Skip to content
https://cnrs.fr

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
GRADE
B
FIX
2
REVIEW
3
PASS
4
INFO
0
Probed from Sao Paulo, Brazil
302 Found
Checks
9
4 PASS 3 REVIEW 2 FIX
D
Redirect Chain
Action
2 redirect(s), 2083 ms total
FIX
2 redirect(s), 2083 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://cnrs.fr
Warning::
Redirect overhead: 2083 ms total
Got: 2083 ms

https://cnrs.fr

828 ms · HTTP/1.1

302

https://www.cnrs.fr/

629 ms · HTTP/1.1

301

https://www.cnrs.fr/fr

626 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://cnrs.fr302828 msHTTP/1.1
2https://www.cnrs.fr/301629 msHTTP/1.1
3https://www.cnrs.fr/fr200626 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
HTTP Probe Timing
Total 1034 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
407 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
206 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
213 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.03 s
Total Time Total request time from DNS lookup through full response.
1.03 s

Connection waterfall

DNS Lookup 407 ms TCP Connect 206 ms TLS Handshake 213 ms Server Processing 208 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
187 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

187
days left
0d 30d 60d 90d+

Recommended actions

  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A
DNS Records
1 A records, 207 ms lookup
PASS
1 A records, 207 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 80.94.184.70
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: ns3.cnrs.fr, ns0.cnrs.fr, ns2.cnrs.fr, ns2.renater.fr, ns1.renater.fr, camus.dr15.cnrs.fr
Info::
2 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Warning::
DNS resolution is slow (207 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 207 ms
A80.94.184.70
AAAA
CNAME
NSns3.cnrs.fr, ns0.cnrs.fr, ns2.cnrs.fr, ns2.renater.fr, ns1.renater.fr, camus.dr15.cnrs.fr
MX
10 mx2.cnrs.fr
10 mx1.cnrs.fr
TXT
MS=ms17956212
MS=ms16083841
SPF v=spf1 redirect=spf.cnrs.fr
google-site-verification=qWY8PmYbh-vNEyRqC7s0yQ4996TRtOcxSIwGgW6okyM
mistral-domain-verification=c884e548015a04a5998f1763f7b7982880020409
CAALookup not available with standard resolver
Resolved in 207 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Crawlability
robots.txt present, sitemap with 6 URLs
PASS
robots.txt present, sitemap with 6 URLs
Info::
robots.txt is present
Got: 2054 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 6 entries
Info::
Sitemap index with 6 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 2054 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
#
# robots.txt
#
# This file is to prevent the crawling and indexing of certain parts
# of your site by web crawlers and spiders run by sites like Yahoo!
# and Google. By telling these "robots" where not to go on your site,
# you save bandwidth and server resources.
#
# This file will be ignored unless it is at the root of your host:
# Used:    http://example.com/robots.txt
# Ignored: http://example.com/site/robots.txt
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/robotstxt.html

User-agent: *
# CSS, JS, Images
Allow: /core/*.css$
Allow: /core/*.css?
Allow: /core/*.js$
Allow: /core/*.js?
Allow: /core/*.gif
Allow: /core/*.jpg
Allow: /core/*.jpeg
Allow: /core/*.png
Allow: /core/*.svg
Allow: /profiles/*.css$
Allow: /profiles/*.css?
Allow: /profiles/*.js$
Allow: /profiles/*.js?
Allow: /profiles/*.gif
Allow: /profiles/*.jpg
Allow: /profiles/*.jpeg
Allow: /profiles/*.png
Allow: /profiles/*.svg
# Directories
Disallow: /core/
Disallow: /profiles/
# Files
Disallow: /README.md
Disallow: /composer/Metapackage/README.txt
Disallow: /composer/Plugin/ProjectMessage/README.md
Disallow: /composer/Plugin/Scaffold/README.md
Disallow: /composer/Plugin/VendorHardening/README.txt
Disallow: /composer/Template/README.txt
Disallow: /modules/README.txt
Disallow: /sites/README.txt
Disallow: /themes/README.txt
Disallow: /web.config
# Paths (clean URLs)
Disallow: /admin/
Disallow: /comment/reply/
Disallow: /filter/tips
Disallow: /node/add/
Disallow: /search/
Disallow: /user/register
Disallow: /user/password
Disallow: /user/login
Disallow: /user/logout
Disallow: /media/oembed
Disallow: /*/media/oembed
# Paths (no clean URLs)
Disallow: /index.php/admin/
Disallow: /index.php/comment/reply/
Disallow: /index.php/filter/tips
Disallow: /index.php/node/add/
Disallow: /index.php/search/
Disallow: /index.php/user/password
Disallow: /index.php/user/register
Disallow: /index.php/user/login
Disallow: /index.php/user/logout
Disallow: /index.php/media/oembed
Disallow: /index.php/*/media/oembed

Disallow: /institut_*/fr/

A
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

301https://www.cnrs.fr/
200https://cnrs.fr/

Preferred variant: non-www

HTTP → HTTPS

302http://cnrs.fr/ https://cnrs.fr/

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
cnrs.fr — via GIP RENATER, 31 years, 9 months old, hosted on CEGEDIM, FR
PASS
cnrs.fr — via GIP RENATER, 31 years, 9 months old, hosted on CEGEDIM, FR
Info::
Domain registered until Dec 31, 2026 (8 months remaining)
Info::
Registrar: GIP RENATER
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: CEGEDIM, FR
Got: AS12601
Domain expiry

169 days

December 31, 2026

SSL certificate

187 days

Issued by Hellenic Academic and Research Institutions CA

Domain age

31 years, 9 months

Registered December 31, 1994

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

CEGEDIM, FR

ASN AS12601

80.94.184.70

Registrar

GIP RENATER

Unlocked 6 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar GIP RENATER
Created December 31, 1994 (31 years, 9 months ago)
Expires December 31, 2026 (8 months)
Last Updated January 31, 2026
Name Servers camus.dr15.cnrs.fr, ns0.cnrs.fr, ns1.renater.fr, ns2.cnrs.fr, ns2.renater.fr, ns3.cnrs.fr
Registrant CTRE NAT DE LA RECHERCHE SCIENTIFIQUE
Hosting
IP Address 80.94.184.70
ASN AS12601 (CEGEDIM, FR)
Provider CEGEDIM, FR
Data source: rdap (1.3s)

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback