Skip to content
https://chrome.google.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
2
REVIEW
2
PASS
5
INFO
0
Probed from Santa Clara, United States
301 Moved Permanently
Checks
9
5 PASS 2 REVIEW 2 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: 2607:f8b0:4005:803::200e
Info::
IPv6 connection error
Got: dial tcp6 [2607:f8b0:4005:803::200e]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2607:f8b0:4005:803::200e 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)

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.

B
DNS Records
6 A records, 35 ms lookup
REVIEW
6 A records, 35 ms lookup
Info::
Resolves to 6 IPv4 address(es)
Got: 74.125.137.139, 74.125.137.100, 74.125.137.138, 74.125.137.101, 74.125.137.113, 74.125.137.102
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2607:f8b0:4005:803::200e
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: www3.l.google.com
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::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 35 ms
Got: 35 ms
A74.125.137.139, 74.125.137.100, 74.125.137.138, 74.125.137.101, 74.125.137.113, 74.125.137.102
AAAA2607:f8b0:4005:803::200e
CNAMEwww3.l.google.com
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 35 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

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

Certificate validity

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

Recommended actions

  • 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
Redirect Chain
1 redirect(s), 110 ms total
PASS
1 redirect(s), 110 ms total
Info::
Single redirect
Got: https://chrome.google.com → https://www.google.com/chrome/ (301)
Info::
WWW normalization redirect
Info::
Cross-domain redirect detected

https://chrome.google.com

59 ms · HTTP/1.1

301

https://www.google.com/chrome/

51 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://chrome.google.com30159 msHTTP/1.1sffe
2https://www.google.com/chrome/20051 msHTTP/1.1sffe

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 30 URLs
PASS
robots.txt present, sitemap with 30 URLs
Info::
robots.txt is present
Got: 132 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 30 entries
Info::
Sitemap index with 30 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 132 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /webstore/search
Disallow: /webstore/static/*/wall/js/*
Sitemap: https://chrome.google.com/webstore/sitemap
sitemap.xml 200 OK
Type Sitemap Index URLs 30 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::
HTTP correctly 301-redirects to HTTPS

www / non-www

https://www.chrome.google.com/
200https://chrome.google.com/

HTTP → HTTPS

301http://chrome.google.com/ → https://www.google.com/chrome/

Consistent

A+
Domain Intelligence
google.com — via MarkMonitor Inc., 29 years old, hosted on Google Cloud
PASS
google.com — via MarkMonitor Inc., 29 years old, hosted on Google Cloud
Info::
Domain registered until Sep 14, 2028 (2 years, 5 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: MarkMonitor Inc.
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: Google Cloud
Got: AS15169
Domain expiry

759 days

September 14, 2028

SSL certificate

61 days

Issued by Google Trust Services

Domain age

29 years

Registered September 15, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Google Cloud

ASN AS15169

142.251.46.238

Registrar

MarkMonitor Inc.

Unlocked 4 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
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created September 15, 1997 (29 years ago)
Expires September 14, 2028 (2 years, 5 months)
Last Updated September 9, 2019
Name Servers ns1.google.com, ns2.google.com, ns3.google.com, ns4.google.com
DNSSEC Not enabled
Hosting
IP Address 142.251.46.238
ASN AS15169 (GOOGLE - Google LLC, US)
Provider Google Cloud
Data source: rdap (0.1s)

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

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 47 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.
2 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
20 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
47 ms
Total Time Total request time from DNS lookup through full response.
47 ms

Connection waterfall

DNS Lookup 5 ms TCP Connect 2 ms TLS Handshake 20 ms Server Processing 21 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