Infrastructure - https://thinkwithgoogle.com BeaverCheck Audit

D

CDN & Delivery

Action

No CDN detected

FIX

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

Redirect Chain

2 redirect(s), 319 ms total

REVIEW

2 redirect(s), 319 ms total

2 redirects before reaching final URL

Each redirect adds latency. Try to minimize the chain to 1 hop.

WWW normalization redirect

Cross-domain redirect detected

https://thinkwithgoogle.com

39 ms · HTTP/1.1

301

https://www.thinkwithgoogle.com/

111 ms · HTTP/1.1

301

https://business.google.com/us/think/

168 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://thinkwithgoogle.com	301	39 ms	HTTP/1.1	sffe
2	https://www.thinkwithgoogle.com/	301	111 ms	HTTP/1.1	Google Frontend
3	https://business.google.com/us/think/	200	168 ms	HTTP/1.1	ESF

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

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+

DNS Records

1 A records, 27 ms lookup

PASS

1 A records, 27 ms lookup

Resolves to 1 IPv4 address(es)

Got: 142.250.65.78

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

Has 1 IPv6 (AAAA) record(s)

Got: 2607:f8b0:4006:810::200e

4 nameserver(s) configured

Got: ns3.google.com, ns2.google.com, ns4.google.com, ns1.google.com

No MX records — email not configured via DNS

CAA records not checked

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

SPF record present in TXT

DNS resolution time: 27 ms

Got: 27 ms

A	142.250.65.78
AAAA	2607:f8b0:4006:810::200e
CNAME	—
NS	ns3.google.com, ns2.google.com, ns4.google.com, ns1.google.com
MX	—
TXT	SPF v=spf1 -all facebook-domain-verification=sbvz693hyqny6ag4fjqyse15bm6uz0
CAA	Lookup not available with standard resolver

Resolved in 27 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.

A+

IPv6 Readiness

IPv6 reachable (1 ms)

PASS

IPv6 reachable (1 ms)

IPv6 is configured and reachable at 2607:f8b0:4006:810::200e

Got: 1 ms connect

IPv6 Ready

AAAA Records 2607:f8b0:4006:810::200e Connection Reachable (1 ms)

A+

Crawlability

robots.txt present, sitemap with 84 URLs

PASS

robots.txt present, sitemap with 84 URLs

robots.txt is present

Got: 88 bytes

sitemap.xml is present

sitemap.xml is valid XML

sitemap.xml contains 84 entries

Sitemap index with 84 child sitemaps

robots.txt references sitemap

robots.txt 200 OK

Size 88 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed

User-agent: *

Disallow: /*?query=

Sitemap: https://www.thinkwithgoogle.com/sitemap.xml

sitemap.xml 200 OK

Type Sitemap Index URLs 84 entries Valid XML Yes

Child Sitemaps:

A+

URL Variants

www/non-www, trailing slash, HTTP→HTTPS

PASS

www/non-www, trailing slash, HTTP→HTTPS

www/non-www redirect configured correctly (preferred: non-www)

HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.thinkwithgoogle.com/

200https://thinkwithgoogle.com/

Preferred variant: non-www

HTTP → HTTPS

301http://thinkwithgoogle.com/ → https://www.thinkwithgoogle.com/

Consistent

A

Domain Intelligence

thinkwithgoogle.com — via MarkMonitor Inc., 16 years, 1 months old

PASS

thinkwithgoogle.com — via MarkMonitor Inc., 16 years, 1 months old

Domain expires in 41 days

Consider enabling auto-renewal to prevent accidental expiration.

Got: Expires Jun 2, 2026

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.

Registrar: MarkMonitor Inc.

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

EXPIRED

June 2, 2026

SSL certificate

61 days

Issued by Google Trust Services

Domain age

16 years, 1 months

Registered June 2, 2010

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2607:f8b0:4006:805::200e

Registrar

MarkMonitor Inc.

Unlocked 4 NS records

Expiry timeline

Today

+1 year

Domain expiry SSL expiry Danger zone (≤30 days)

Recommended actions

Domain has EXPIRED — renew immediately to avoid total site outage
Enable DNSSEC to protect visitors from DNS spoofing
Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers

Registrar MarkMonitor Inc.

Created June 2, 2010 (16 years, 1 months ago)

Expires June 2, 2026 (1 months)

Last Updated May 1, 2025

Name Servers ns1.google.com, ns2.google.com, ns3.google.com, ns4.google.com

DNSSEC Not enabled

Hosting

IP Address 2607:f8b0:4006:805::200e

Data source: rdap (0.1s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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 35 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

PASS

DNS Lookup

20 ms

TCP Connect

1 ms

TLS Handshake

11 ms

Time to First Byte

35 ms

Total Time

36 ms

Connection waterfall

DNS Lookup 20 ms TCP Connect 1 ms TLS Handshake 11 ms Server Processing 3 ms Content Transfer 0 ms