Skip to content
https://iarc.fr

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
303 HTTP 303
Checks
9
5 PASS 3 REVIEW 1 FIX
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
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 67 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

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 67 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
TLS Certificate Expiry & Recommendations
74 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • 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, 47 ms lookup
PASS
1 A records, 47 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 193.51.164.6
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns1.iarc.fr, ccpntc3.in2p3.fr, dnsext.iarc.fr, ccpnvx.in2p3.fr
Info::
1 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
Info::
DNS resolution time: 47 ms
Got: 47 ms
A193.51.164.6
AAAA
CNAME
NSns1.iarc.fr, ccpntc3.in2p3.fr, dnsext.iarc.fr, ccpnvx.in2p3.fr
MX
10 iarc-fr.mail.protection.outlook.com
TXT
qlvvlj02b0g2ldhhwkpcg4ts6789dq97
BFPcEyFY1bHN1ZkdR2A/RQtPazGeZnsTl295lVgWmBoOOUiJayww1LQmATkaWtBk+OOw4qx0T6H/0Be9...
SPF v=spf1 mx ip4:193.51.164.149/32 ip4:193.51.164.154/32 ip4:193.51.164.147/32 ip4:...
facebook-domain-verification=69pen5tf9edowze7jvbomj3783t342
have-i-been-pwned-verification=d5fa6db2a13c5c810da70c3df090162e
CAALookup not available with standard resolver
Resolved in 47 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.

A
Redirect Chain
1 redirect(s), 562 ms total
PASS
1 redirect(s), 562 ms total
Info::
Single redirect
Got: https://iarc.fr → https://www.iarc.who.int/ (303)
Info::
WWW normalization redirect
Info::
Redirect overhead: 562 ms total
Got: 562 ms
Info::
Cross-domain redirect detected

https://iarc.fr

120 ms · HTTP/1.1

303

https://www.iarc.who.int/

442 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://iarc.fr303120 msHTTP/1.1Microsoft-IIS/7.5
2https://www.iarc.who.int/200442 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

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.iarc.fr/
200https://iarc.fr/

Preferred variant: non-www

HTTP → HTTPS

303http://iarc.fr/ https://www.iarc.who.int/

Use 301 (permanent) instead of 302 (temporary)

A+
Domain Intelligence
iarc.fr — via GIP RENATER, 31 years, 9 months old, hosted on FR-RENATER Reseau National de telecommunications pour la Technologie, FR
PASS
iarc.fr — via GIP RENATER, 31 years, 9 months old, hosted on FR-RENATER Reseau National de telecommunications pour la Technologie, 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: FR-RENATER Reseau National de telecommunications pour la Technologie, FR
Got: AS2200
Domain expiry

201 days

December 31, 2026

SSL certificate

74 days

Issued by Let's Encrypt

Domain age

31 years, 9 months

Registered December 31, 1994

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

FR-RENATER Reseau National de telecommunications pour la Technologie, FR

ASN AS2200

193.51.164.6

Registrar

GIP RENATER

Unlocked 4 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 ccpntc3.in2p3.fr, ccpnvx.in2p3.fr, dnsext.iarc.fr, ns1.iarc.fr
Registrant International Agency for Research on Cancer
Hosting
IP Address 193.51.164.6
ASN AS2200 (FR-RENATER Reseau National de telecommunications pour la Technologie, FR)
Provider FR-RENATER Reseau National de telecommunications pour la Technologie, FR
Data source: rdap (0.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

A+
HTTP Probe Timing
Total 166 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
47 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
22 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
75 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
166 ms
Total Time Total request time from DNS lookup through full response.
166 ms

Connection waterfall

DNS Lookup 47 ms TCP Connect 22 ms TLS Handshake 75 ms Server Processing 22 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback