Skip to content
https://pagespeed.web.dev/analysis/https-aistudio-google-com-apps-8a1aa443-e343-43b1-9244-fca856afe044/qqof0k4os8?form_factor=desktop

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
11
PASS
5
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
5 PASS 11 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
DNS Records
6 A records, 24 ms lookup
REVIEW
6 A records, 24 ms lookup
Info::
Resolves to 6 IPv4 address(es)
Got: 142.251.110.113, 142.251.110.139, 142.251.110.138, 142.251.110.100, 142.251.110.102, 142.251.110.101
Info::
Has 4 IPv6 (AAAA) record(s)
Got: 2a00:1450:4001:c1f::8a, 2a00:1450:4001:c1f::64, 2a00:1450:4001:c1f::65, 2a00:1450:4001:c1f::66
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::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 24 ms
Got: 24 ms
A142.251.110.113, 142.251.110.139, 142.251.110.138, 142.251.110.100, 142.251.110.102, 142.251.110.101
AAAA2a00:1450:4001:c1f::8a, 2a00:1450:4001:c1f::64, 2a00:1450:4001:c1f::65, 2a00:1450:4001:c1f::66
CNAMEwww3.l.google.com
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 24 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

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
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
B
Reverse DNS
0/10 IPs match cert SAN
REVIEW
0/10 IPs match cert SAN
Info::
PTR for 142.251.110.113 does not match any cert SAN: bz-in-f113.1e100.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 142.251.110.139 does not match any cert SAN: bz-in-f139.1e100.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 142.251.110.138 does not match any cert SAN: bz-in-f138.1e100.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 142.251.110.100 does not match any cert SAN: bz-in-f100.1e100.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 142.251.110.102 does not match any cert SAN: bz-in-f102.1e100.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 142.251.110.101 does not match any cert SAN: bz-in-f101.1e100.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 2a00:1450:4001:c1f::8a does not match any cert SAN: bz-in-f138.1e100.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 2a00:1450:4001:c1f::64 does not match any cert SAN: bz-in-f100.1e100.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 2a00:1450:4001:c1f::65 does not match any cert SAN: bz-in-f101.1e100.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 2a00:1450:4001:c1f::66 does not match any cert SAN: bz-in-f102.1e100.net
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
B
Multi-Resolver DNS Speed
Mean 60ms across 3 resolvers (spread 125ms)
REVIEW
Mean 60ms across 3 resolvers (spread 125ms)
Info::
Cloudflare: 17ms
Got: 17ms via 1.1.1.1:53
Info::
Google: 23ms
Got: 23ms via 8.8.8.8:53
Info::
Quad9: 142ms
Got: 142ms via 9.9.9.9:53
B
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more ▾

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more ▾

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
HTTP Probe Timing
Total 1376 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
29 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
25 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
38 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
190 ms
Total Time Total request time from DNS lookup through full response.
1.38 s

Connection waterfall

DNS Lookup 29 ms TCP Connect 25 ms TLS Handshake 38 ms Server Processing 97 ms Content Transfer 1.19 s
B
TLS Certificate Expiry & Recommendations
69 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

69
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
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
CNAME does not point at a known takeover-able service
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://pagespeed.web.dev/analysis/https-aistudio-google-com-apps-8a1aa443-e343-43b1-9244-fca856afe044/qqof0k4os8?form_factor=desktop

https://pagespeed.web.dev/analysis/https...

227 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://pagespeed.web.dev/analysis/https...200227 msHTTP/1.1ESF
A+
IPv6 Readiness
IPv6 reachable (25 ms)
PASS
IPv6 reachable (25 ms)
Info::
IPv6 is configured and reachable at 2a00:1450:4001:c1f::8a, 2a00:1450:4001:c1f::64, 2a00:1450:4001:c1f::65, 2a00:1450:4001:c1f::66
Got: 25 ms connect
IPv6 Ready
AAAA Records 2a00:1450:4001:c1f::8a, 2a00:1450:4001:c1f::64, 2a00:1450:4001:c1f::65, 2a00:1450:4001:c1f::66 Connection Reachable (25 ms)
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

https://www.pagespeed.web.dev/analysis/https-aistudio-google-com-apps-8a1aa443-e343-43b1-9244-fca856afe044/qqof0k4os8
200https://pagespeed.web.dev/analysis/https-aistudio-google-com-apps-8a1aa443-e343-43b1-9244-fca856afe044/qqof0k4os8

Trailing Slash

404https://pagespeed.web.dev/analysis/https-aistudio-google-com-apps-8a1aa443-e343-43b1-9244-fca856afe044/qqof0k4os8/
200https://pagespeed.web.dev/analysis/https-aistudio-google-com-apps-8a1aa443-e343-43b1-9244-fca856afe044/qqof0k4os8?form_factor=desktop

HTTP → HTTPS

301http://pagespeed.web.dev/analysis/https-aistudio-google-com-apps-8a1aa443-e343-43b1-9244-fca856afe044/qqof0k4os8 → https://pagespeed.web.dev/analysis/https-aistudio-google-com-apps-8a1aa443-e343-43b1-9244-fca856afe044/qqof0k4os8

Consistent

A
Domain Intelligence
web.dev — via MarkMonitor Inc., 7 years, 11 months old
PASS
web.dev — via MarkMonitor Inc., 7 years, 11 months old
Warning::
Domain expires in 70 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Oct 29, 2026
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.
Domain expiry

59 days

October 29, 2026

SSL certificate

69 days

Issued by Google Trust Services

Domain age

7 years, 11 months

Registered October 29, 2018

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2001:4860:4802:32::1b

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 DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created October 29, 2018 (7 years, 11 months ago)
Expires October 29, 2026 (2 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.3s)

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

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback