Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DRedirect ChainAction3 redirect(s), 428 ms totalFIX
https://ai.studio/apps/8a1aa443-e343-43b...
69 ms · HTTP/1.1
https://aistudio.google.com/apps/8a1aa44...
175 ms · HTTP/1.1
https://accounts.google.com/ServiceLogin...
132 ms · HTTP/1.1
https://accounts.google.com/v3/signin/id...
52 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://ai.studio/apps/8a1aa443-e343-43b... | 301 | 69 ms | HTTP/1.1 | sffe |
| 2 | https://aistudio.google.com/apps/8a1aa44... | 302 | 175 ms | HTTP/1.1 | ESF |
| 3 | https://accounts.google.com/ServiceLogin... | 302 | 132 ms | HTTP/1.1 | ESF |
| 4 | https://accounts.google.com/v3/signin/id... | 200 | 52 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.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
If permanent, use 301 instead.
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
DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BReverse DNS0/2 IPs match cert SANREVIEW
BTLS Certificate Expiry & Recommendations69 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
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
BCDN Cache ObservabilityNo CDN cache-status headers in the responseREVIEW
BOperational Status PageNo status page link detectedREVIEW
A+DNS Records1 A records, 24 ms lookupPASS
| A | 216.239.32.29 |
| AAAA | 2001:4860:4802:32::1d |
| CNAME | — |
| NS | ns2.googledomains.com, ns3.googledomains.com, ns1.googledomains.com, ns4.googledomains.com |
| MX | — |
| TXT | SPF v=spf1 ?all |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
ACAA Recordsissue: pki.googPASS
A+Multi-Resolver DNS SpeedMean 22ms across 3 resolvers (spread 3ms)PASS
A+IPv6 ReadinessIPv6 reachable (22 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 1 URLsPASS
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
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
Trailing Slash
HTTP → HTTPS
Consistent
A+Domain Intelligenceai.studio — via MarkMonitor Inc., 2 years, 11 months oldPASS
1122 days
September 21, 2029
69 days
Issued by Google Trust Services
2 years, 11 months
Registered September 21, 2023
Not enabled
Protects against DNS spoofing
Unknown
2001:4860:4802:32::1d
MarkMonitor Inc.
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
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.
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