Skip to content
https://aistudio.google.com/apps/8a1aa443-e343-43b1-9244-fca856afe044?_gl=1*18jxoze*_up*MQ..&gclid=CjwKCAjwhZDUBhBGEiwAbi5bjoetsyty1ASr_fSL6o5Qwbl5zSSDrk6KwJb7P73Qb4noxx2tCs_HZhoCF-EQAvD_BwE&project=gen-lang-client-0544329167&showPreview=true

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
1
REVIEW
7
PASS
9
INFO
0
Probed from Madrid, Spain
302 Found
Checks
17
9 PASS 7 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
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.20.138 does not match any cert SAN: bx-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.20.139 does not match any cert SAN: bx-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.20.102 does not match any cert SAN: bx-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.20.113 does not match any cert SAN: bx-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.20.100 does not match any cert SAN: bx-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.20.101 does not match any cert SAN: bx-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:c17::65 does not match any cert SAN: bx-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:c17::71 does not match any cert SAN: bx-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 2a00:1450:4001:c17::8b does not match any cert SAN: bx-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 2a00:1450:4001:c17::66 does not match any cert SAN: bx-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
Redirect Chain
2 redirect(s), 352 ms total
REVIEW
2 redirect(s), 352 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://aistudio.google.com/apps/8a1aa443-e343-43b1-9244-fca856afe044?_gl=1*18jxoze*_up*MQ..&gclid=CjwKCAjwhZDUBhBGEiwAbi5bjoetsyty1ASr_fSL6o5Qwbl5zSSDrk6KwJb7P73Qb4noxx2tCs_HZhoCF-EQAvD_BwE&project=gen-lang-client-0544329167&showPreview=true
Info::
Cross-domain redirect detected

https://aistudio.google.com/apps/8a1aa44...

152 ms · HTTP/1.1

302

https://accounts.google.com/ServiceLogin...

110 ms · HTTP/1.1

302

https://accounts.google.com/v3/signin/id...

90 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://aistudio.google.com/apps/8a1aa44...302152 msHTTP/1.1ESF
2https://accounts.google.com/ServiceLogin...302110 msHTTP/1.1ESF
3https://accounts.google.com/v3/signin/id...20090 msHTTP/1.1ESF

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

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

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.
A
DNS Records
6 A records, 23 ms lookup
PASS
6 A records, 23 ms lookup
Info::
Resolves to 6 IPv4 address(es)
Got: 142.251.20.138, 142.251.20.139, 142.251.20.102, 142.251.20.113, 142.251.20.100, 142.251.20.101
Info::
Has 4 IPv6 (AAAA) record(s)
Got: 2a00:1450:4001:c17::65, 2a00:1450:4001:c17::71, 2a00:1450:4001:c17::8b, 2a00:1450:4001:c17::66
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: 23 ms
Got: 23 ms
A142.251.20.138, 142.251.20.139, 142.251.20.102, 142.251.20.113, 142.251.20.100, 142.251.20.101
AAAA2a00:1450:4001:c17::65, 2a00:1450:4001:c17::71, 2a00:1450:4001:c17::8b, 2a00:1450:4001:c17::66
CNAME—
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 23 ms

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+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 13ms across 3 resolvers (spread 20ms)
PASS
Mean 13ms across 3 resolvers (spread 20ms)
Info::
Quad9: 1ms
Got: 1ms via 9.9.9.9:53
Info::
Cloudflare: 18ms
Got: 18ms via 1.1.1.1:53
Info::
Google: 21ms
Got: 21ms via 8.8.8.8:53
A+
IPv6 Readiness
IPv6 reachable (25 ms)
PASS
IPv6 reachable (25 ms)
Info::
IPv6 is configured and reachable at 2a00:1450:4001:c17::65, 2a00:1450:4001:c17::71, 2a00:1450:4001:c17::8b, 2a00:1450:4001:c17::66
Got: 25 ms connect
IPv6 Ready
AAAA Records 2a00:1450:4001:c17::65, 2a00:1450:4001:c17::71, 2a00:1450:4001:c17::8b, 2a00:1450:4001:c17::66 Connection Reachable (25 ms)
A+
Crawlability
robots.txt present, sitemap with 1 URLs
PASS
robots.txt present, sitemap with 1 URLs
Info::
robots.txt is present
Got: 473 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1 entries
Info::
Sitemap index with 1 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 473 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *

Allow: /app/apikey
Allow: /apikey
Allow: /prompts/new_chat

Disallow: /404
Disallow: /500
Disallow: /520

Disallow: /api-keys
Disallow: /app
Disallow: /app/
Disallow: /apps
Disallow: /apps/
Disallow: /billing
Disallow: /library
Disallow: /logs
Disallow: /projects
Disallow: /prompt-access-restricted
Disallow: /prompts/
Disallow: /rate-limit
Disallow: /spend
Disallow: /usage
Disallow: /docs

Allow: *

Sitemap: https://aistudio.google.com/sitemap/index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 1 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 redirects to HTTPS permanently
Got: HTTP 301

www / non-www

301https://www.aistudio.google.com/apps/8a1aa443-e343-43b1-9244-fca856afe044
200https://aistudio.google.com/apps/8a1aa443-e343-43b1-9244-fca856afe044

Preferred variant: non-www

Trailing Slash

302https://aistudio.google.com/apps/8a1aa443-e343-43b1-9244-fca856afe044/
200https://aistudio.google.com/apps/8a1aa443-e343-43b1-9244-fca856afe044?_gl=1*18jxoze*_up*MQ..&gclid=CjwKCAjwhZDUBhBGEiwAbi5bjoetsyty1ASr_fSL6o5Qwbl5zSSDrk6KwJb7P73Qb4noxx2tCs_HZhoCF-EQAvD_BwE&project=gen-lang-client-0544329167&showPreview=true

HTTP → HTTPS

301http://aistudio.google.com/apps/8a1aa443-e343-43b1-9244-fca856afe044 → https://aistudio.google.com/apps/8a1aa443-e343-43b1-9244-fca856afe044

Consistent

A+
Domain Intelligence
google.com — via MarkMonitor Inc., 29 years, 4 months old
PASS
google.com — via MarkMonitor Inc., 29 years, 4 months old
Info::
Domain registered until Sep 14, 2028 (2 years, 1 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.
Domain expiry

749 days

September 14, 2028

SSL certificate

69 days

Issued by Google Trust Services

Domain age

29 years, 4 months

Registered September 15, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a00:1450:4001:c17::8a

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, 4 months ago)
Expires September 14, 2028 (2 years, 1 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 2a00:1450:4001:c17::8a
Data source: rdap (0.2s)

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 183 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
23 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.
36 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
184 ms
Total Time Total request time from DNS lookup through full response.
184 ms

Connection waterfall

DNS Lookup 23 ms TCP Connect 25 ms TLS Handshake 36 ms Server Processing 100 ms Content Transfer 0 ms
A+
Health Check Endpoint
Health endpoint at https://aistudio.google.com/health (HTTP 200)
PASS
Health endpoint at https://aistudio.google.com/health (HTTP 200)
Info::
Public health endpoint at https://aistudio.google.com/health
Got: https://aistudio.google.com/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback