Skip to content
https://kubernetes.io

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Sao Paulo, Brazil
200 OK
Checks
9
6 PASS 3 REVIEW
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
TLS Certificate Expiry & Recommendations
39 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • 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
B
CDN & Delivery
Netlify
REVIEW
Netlify
Info::
Site is served via Netlify CDN
Got: x-nf-request-id: 01KNCVS5SAS7RP9487EFTX7BYA
CDN Detected: Netlify
Provider Netlify Evidence x-nf-request-id: 01KNCVS5SAS7RP9487EFTX7BYA
A
DNS Records
2 A records, 1706 ms lookup
PASS
2 A records, 1706 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 15.197.167.90, 3.33.186.135
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a1.googledomains.com
Info::
5 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 (1706 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 1706 ms
A15.197.167.90, 3.33.186.135
AAAA—
CNAME—
NSns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a1.googledomains.com
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
SPF v=spf1 include:_spf.google.com mail.kubernetes.io ~all
1password-site-verification=SOZCTQ66DFFXVGPOWOHMVDIBVI
google-site-verification=qmfDqvHjWJBL78F9saApyW0VFRyymuSMpqMn8gtGmd0
google-site-verification=oPORCoq9XU6CmaR7G_bV00CLmEz-wLGOL7SXpeEuTt8
CAALookup not available with standard resolver
Resolved in 1706 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.

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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://kubernetes.io

https://kubernetes.io

146 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://kubernetes.io200146 msHTTP/1.1Netlify
A+
Crawlability
robots.txt present, sitemap with 16 URLs
PASS
robots.txt present, sitemap with 16 URLs
Info::
robots.txt is present
Got: 305 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 16 entries
Info::
Sitemap index with 16 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 305 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /legacy/
Disallow: /v1.0/
Disallow: /v1.1/
Disallow: /404/
Disallow: /404.html

Allow: /docs/reference/kubernetes-api/api-index/
Allow: /docs/reference/kubernetes-api/labels-annotations-taints/
Disallow: /docs/reference/kubernetes-api/

SITEMAP: https://kubernetes.io/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 16 entries Valid XML Yes
Child Sitemaps:
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)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.kubernetes.io/
200https://kubernetes.io/

Preferred variant: non-www

HTTP → HTTPS

301http://kubernetes.io/ → https://kubernetes.io/

Consistent

A+
Domain Intelligence
kubernetes.io — via 1API GmbH, 11 years, 10 months old, hosted on AWS
PASS
kubernetes.io — via 1API GmbH, 11 years, 10 months old, hosted on AWS
Info::
Domain registered until Jul 23, 2026 (3 months remaining)
Info::
Registrar: 1API GmbH
Info::
Hosting: AWS
Got: AS16509
Domain expiry

11 days

July 23, 2026

SSL certificate

39 days

Issued by Let's Encrypt

Domain age

11 years, 10 months

Registered July 23, 2014

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

3.33.186.135

Registrar

1API GmbH

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
Registrar 1API GmbH
Created July 23, 2014 (11 years, 10 months ago)
Expires July 23, 2026 (3 months)
Last Updated November 26, 2025
Name Servers ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, ns-cloud-a3.googledomains.com, ns-cloud-a4.googledomains.com
Registrant The Linux Foundation
Hosting
IP Address 3.33.186.135
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: whois (2.4s)
A+
HTTP Probe Timing
Total 222 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
205 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
2 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
8 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
221 ms
Total Time Total request time from DNS lookup through full response.
222 ms

Connection waterfall

DNS Lookup 205 ms TCP Connect 2 ms TLS Handshake 8 ms Server Processing 7 ms Content Transfer 1 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback