Skip to content
https://web.dev

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
98
GRADE
A+
FIX
1
REVIEW
1
PASS
7
INFO
0
Probed from New York, United Stated
200 OK
Checks
9
7 PASS 1 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.

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

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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, 70 ms lookup
PASS
1 A records, 70 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 216.239.32.27
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2001:4860:4802:32::1b
Info::
4 nameserver(s) configured
Got: ns3.zdns.google, ns1.zdns.google, ns2.zdns.google, ns4.zdns.google
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: 70 ms
Got: 70 ms
A216.239.32.27
AAAA2001:4860:4802:32::1b
CNAME
NSns3.zdns.google, ns1.zdns.google, ns2.zdns.google, ns4.zdns.google
MX
TXT
google-site-verification=1KUpoM0U9uMGLkzIL1CaCnZDapQByrD74Wr92wrYZdA
CAALookup not available with standard resolver
Resolved in 70 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.

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)

A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://web.dev

https://web.dev

229 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://web.dev200229 msHTTP/1.1Google Frontend
A+
IPv6 Readiness
IPv6 reachable (2 ms)
PASS
IPv6 reachable (2 ms)
Info::
IPv6 is configured and reachable at 2001:4860:4802:32::1b
Got: 2 ms connect
IPv6 Ready
AAAA Records 2001:4860:4802:32::1b Connection Reachable (2 ms)
A+
Crawlability
robots.txt present, sitemap with 2 URLs
PASS
robots.txt present, sitemap with 2 URLs
Info::
robots.txt is present
Got: 61 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2 entries
Info::
Sitemap index with 2 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 61 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow:
Sitemap: https://web.dev/sitemap.xml

sitemap.xml 200 OK
Type Sitemap Index URLs 2 entries Valid XML Yes
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

404https://www.web.dev/
200https://web.dev/

HTTP → HTTPS

301http://web.dev/ https://web.dev/

Consistent

A+
Domain Intelligence
web.dev — via MarkMonitor Inc., 7 years, 6 months old
PASS
web.dev — via MarkMonitor Inc., 7 years, 6 months old
Info::
Domain registered until Oct 29, 2026 (6 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.
Domain expiry

73 days

October 29, 2026

SSL certificate

64 days

Issued by Google Trust Services

Domain age

7 years, 6 months

Registered October 29, 2018

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2001:4860:4802:32::1b

Registrar

MarkMonitor Inc.

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
  • Enable DNSSEC to protect visitors from DNS spoofing
Registrar MarkMonitor Inc.
Created October 29, 2018 (7 years, 6 months ago)
Expires October 29, 2026 (6 months)
Last Updated October 23, 2025
Name Servers ns1.zdns.google, ns2.zdns.google, ns3.zdns.google, ns4.zdns.google
DNSSEC Not enabled
Hosting
IP Address 2001:4860:4802:32::1b
Data source: rdap (0.4s)

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 404 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
202 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
10 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
404 ms
Total Time Total request time from DNS lookup through full response.
405 ms

Connection waterfall

DNS Lookup 202 ms TCP Connect 1 ms TLS Handshake 10 ms Server Processing 191 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