Skip to content
https://www.w3.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Santa Clara, United Stated
200 OK
Checks
9
6 PASS 2 REVIEW 1 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2606:4700::6812:1713, 2606:4700::6812:1613
Info::
IPv6 connection error
Got: dial tcp6 [2606:4700::6812:1713]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2606:4700::6812:1713, 2606:4700::6812:1613 Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 3772 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 3772 B Sitemaps referenced 0 User-agents *, W3C-checklink Blocking No — crawling allowed
#
# robots.txt for https://www.w3.org/
#
# $Id: robots.txt,v 1.104 2026/02/16 05:12:36 gerald Exp $
#

# the following settings apply to all bots
User-agent: *
# Blogs - WordPress
# https://wordpress.org/documentation/article/search-engine-optimization/#robots-txt-optimization
Disallow: /*/wp-admin/
Disallow: /*/wp-includes/
Disallow: /*/wp-content/plugins/
Disallow: /*/wp-content/cache/
Disallow: /*/wp-content/themes/
Disallow: /blog/?
Disallow: /blog/*/trackback/
Disallow: /blog/*/feed/
Disallow: /blog/*/comments/
Disallow: /blog/*/category/*/*
Disallow: /blog/*/*/trackback/
Disallow: /blog/*/*/feed/
Disallow: /blog/*/*/comments/
Disallow: /blog/*/*?
Disallow: /community/trackback/
Disallow: /community/feed/
Disallow: /community/comments/
Disallow: /community/category/*/*
Disallow: /community/*/trackback/
Disallow: /community/*/feed/
Disallow: /community/*/comments/
Disallow: /community/*/category/*/*
Disallow: /community/*?
Disallow: /Consortium/Offices/trackback/
Disallow: /Consortium/Offices/feed/
Disallow: /Consortium/Offices/comments/
Disallow: /Consortium/Offices/category/*/*
Disallow: /Consortium/Offices/*/trackback/
Disallow: /Consortium/Offices/*/feed/
Disallow: /Consortium/Offices/*/comments/
Disallow: /Consortium/Offices/*?
# Wikis - Mediawiki
# https://www.mediawiki.org/wiki/Manual:Robots.txt
Disallow: /wiki/index.php?
Disallow: /wiki/index.php/Help
Disallow: /wiki/index.php/MediaWiki
Disallow: /wiki/index.php/Special:
Disallow: /wiki/index.php/Template
Disallow: /wiki/Special:
Disallow: /wiki/Help:
Disallow: /wiki/Talk:
Disallow: /wiki/skins/
Disallow: /wiki/*/info
Disallow: /wiki/*/edit
Disallow: /wiki/*/history
Disallow: /*/wiki/index.php?
Disallow: /*/wiki/index.php/Help
Disallow: /*/wiki/index.php/MediaWiki
Disallow: /*/wiki/index.php/Special:
Disallow: /*/wiki/index.php/Template
Disallow: /*/wiki/Special:
Disallow: /*/wiki/Help:
Disallow: /*/wiki/Talk:
Disallow: /*/wiki/skins/
Disallow: /*/wiki/*/info
Disallow: /*/wiki/*/edit
Disallow: /*/wiki/*/history
# various other access-controlled or expensive areas
Disallow: /2004/ontaria/basic
Disallow: /Member/
Disallow: /Team/
Disallow: /Project/
Disallow: /Web/
Disallow: /Systems/
Disallow: /Out-Of-Date
Disallow: /2005/06/blog/
Disallow: /2004/08/W3CTalks
Disallow: /2007/11/Talks/search
Disallow: /People/all/
Disallow: /people/all/
Disallow: /People/domain/
Disallow: /people/domain/
Disallow: /RDF/Validator/ARPServlet
Disallow: /RDF/Validator/rdfval
Disallow: /2003/03/Translations/byLanguage
Disallow: /2003/03/Translations/byTechnology
Disallow: /2005/11/Translations/Query
Disallow: /2000/06/webdata/xslt
Disallow: /2000/09/webdata/xslt
Disallow: /2005/08/online_xslt/xslt
Disallow: /Search/Mail/Public/
Disallow: /2006/02/chartergen
Disallow: /2004/01/pp-impl
Disallow: /Consortium/supporters
Disallow: /2012/pyRdfa/extract
Disallow: /2012/pyRdfa/?
Disallow: /WAI/PF/comments/
Disallow: /WAI/events/
Disallow: /participate/conferences.xml
Disallow: /scripts/
Disallow: /2005/01/yacker/
Disallow: /2005/01/yacker?
Disallow: /2005/07/pubrules?
Disallow: /ns/hydra/console/?
Disallow: /2007/08/grddl/?
Disallow: /2009/07/webidl-check?
Disallow: /RDF/Validator/ARPServlet?
Disallow: /2000/06/webdata/xsv?
Disallow: /2000/09/webdata/xsv?
Disallow: /2007/10/htmldiff?
Disallow: /Style/CSS/members.be/
Disallow: /services
Disallow: /2021/05/view-gallery/
Disallow: /International/questions/qa-html-language-declarations/icons/
Disallow: /International/questions/qa-html-language-declarations/qa-html-language-declarations-data/icons/
Disallow: /*,*
Disallow: /WAI/beta/
Disallow: /WAI/ut1/
Disallow: /WAI/ut2/
Disallow: /WAI/ut3/
Disallow: /WAI/ut4/
Disallow: /WAI/drafts/

# Allow W3C Link checker to check any paths on this site
User-agent: W3C-checklink
Disallow:


sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • 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
2 A records, 13 ms lookup
PASS
2 A records, 13 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.23.19, 104.18.22.19
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700::6812:1713, 2606:4700::6812:1613
Info::
No NS records found
Info::
No MX records — email not configured via DNS
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: 13 ms
Got: 13 ms
A104.18.23.19, 104.18.22.19
AAAA2606:4700::6812:1713, 2606:4700::6812:1613
CNAME
NS
MX
TXT
SPF v=spf1 -all
CAALookup not available with standard resolver
Resolved in 13 ms

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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.w3.org

https://www.w3.org

31 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.w3.org20031 msHTTP/1.1cloudflare
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: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.w3.org/
301https://w3.org/

Preferred variant: www

HTTP → HTTPS

301http://www.w3.org/ https://www.w3.org/

Consistent

A+
Domain Intelligence
w3.org — via Gandi SAS, 32 years, 2 months old, hosted on Cloudflare
PASS
w3.org — via Gandi SAS, 32 years, 2 months old, hosted on Cloudflare
Info::
Domain registered until Jul 5, 2029 (3 years, 3 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: Gandi SAS
Info::
Hosting: Cloudflare
Got: AS13335
Domain expiry

1053 days

July 5, 2029

SSL certificate

67 days

Issued by Google Trust Services

Domain age

32 years, 2 months

Registered July 6, 1994

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.18.22.19

Registrar

Gandi SAS

Lock status unknown 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
Registrar Gandi SAS
Created July 6, 1994 (32 years, 2 months ago)
Expires July 5, 2029 (3 years, 3 months)
Last Updated May 28, 2025
Name Servers jamie.ns.cloudflare.com, pranab.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 104.18.22.19
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
Data source: rdap (0.2s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

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

Connection waterfall

DNS Lookup 5 ms TCP Connect 4 ms TLS Handshake 9 ms Server Processing 14 ms Content Transfer 1 ms
A+
CDN & Delivery
Cloudflare (HIT)
PASS
Cloudflare (HIT)
Info::
Site is served via Cloudflare CDN (edge: SJC)
Got: cf-ray: 9e71f8426f36cf2e-SJC
Info::
CDN cache status: HIT
CDN Detected: Cloudflare
Provider Cloudflare Cache Status HIT Evidence cf-ray: 9e71f8426f36cf2e-SJC
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback