Skip to content
https://blog.google

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
100
GRADE
A+
FIX
1
REVIEW
1
PASS
7
INFO
0
Probed from Singapore, Singapore
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
41 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
4 A records, 44 ms lookup
PASS
4 A records, 44 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 216.239.32.21, 216.239.34.21, 216.239.38.21, 216.239.36.21
Info::
Has 4 IPv6 (AAAA) record(s)
Got: 2001:4860:4802:36::15, 2001:4860:4802:38::15, 2001:4860:4802:32::15, 2001:4860:4802:34::15
Info::
4 nameserver(s) configured
Got: ns1.zdns.google, ns2.zdns.google, ns3.zdns.google, ns4.zdns.google
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: 44 ms
Got: 44 ms
A216.239.32.21, 216.239.34.21, 216.239.38.21, 216.239.36.21
AAAA2001:4860:4802:36::15, 2001:4860:4802:38::15, 2001:4860:4802:32::15, 2001:4860:4802:34::15
CNAME—
NSns1.zdns.google, ns2.zdns.google, ns3.zdns.google, ns4.zdns.google
MX
0 smtp.google.com
TXT
SPF v=spf1 include:_spf.google.com ?all
facebook-domain-verification=1dpptdn7bpg26p5d1mkvttadjncmm8
CAALookup not available with standard resolver
Resolved in 44 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://blog.google

https://blog.google

327 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://blog.google200327 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:36::15, 2001:4860:4802:38::15, 2001:4860:4802:32::15, 2001:4860:4802:34::15
Got: 2 ms connect
IPv6 Ready
AAAA Records 2001:4860:4802:36::15, 2001:4860:4802:38::15, 2001:4860:4802:32::15, 2001:4860:4802:34::15 Connection Reachable (2 ms)
A+
Crawlability
robots.txt present, sitemap with 28 URLs
PASS
robots.txt present, sitemap with 28 URLs
Info::
robots.txt is present
Got: 153 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 28 entries
Info::
Sitemap index with 28 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 153 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed




User-agent: *
Disallow: /search/?
Disallow: /intl/*/search/?
Disallow: /search?
Disallow: /intl/*/search?

Sitemap: https://blog.google/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 28 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.blog.google/
200https://blog.google/

Preferred variant: non-www

HTTP → HTTPS

301http://blog.google/ → https://blog.google/

Consistent

A+
Domain Intelligence
blog.google — via MarkMonitor Inc., 9 years, 9 months old
PASS
blog.google — via MarkMonitor Inc., 9 years, 9 months old
Info::
Domain registered until Aug 12, 2026 (3 months remaining)
Info::
DNSSEC is enabled
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.
Domain expiry

29 days

August 12, 2026

SSL certificate

41 days

Issued by Google Trust Services

Domain age

9 years, 9 months

Registered August 12, 2016

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2001:4860:4802:32::15

Registrar

MarkMonitor Inc.

Unlocked 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 registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created August 12, 2016 (9 years, 9 months ago)
Expires August 12, 2026 (3 months)
Last Updated October 10, 2025
Name Servers ns1.zdns.google, ns2.zdns.google, ns3.zdns.google, ns4.zdns.google
DNSSEC Enabled
Hosting
IP Address 2001:4860:4802:32::15
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 316 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
4 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.
8 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
276 ms
Total Time Total request time from DNS lookup through full response.
317 ms

Connection waterfall

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

Send Feedback