Skip to content
https://global-shayari-ai.ai.studio

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
10
PASS
5
INFO
1
Probed from Singapore, Singapore
200 OK
Checks
17
5 PASS 10 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.
C
Reverse DNS
Action
0/16 IPs match cert SAN
REVIEW
0/16 IPs match cert SAN
Info::
PTR lookup failed for 34.143.72.2: lookup 34.143.72.2: Temporary failure in name resolution
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 34.143.79.2: lookup 34.143.79.2: Temporary failure in name resolution
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 34.143.77.2: lookup 34.143.77.2: Temporary failure in name resolution
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 34.143.73.2: lookup 34.143.73.2: Temporary failure in name resolution
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 34.143.78.2: lookup 34.143.78.2: Temporary failure in name resolution
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 34.143.75.2: lookup 34.143.75.2: Temporary failure in name resolution
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 34.143.76.2: lookup 34.143.76.2: Temporary failure in name resolution
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 34.143.74.2: lookup 34.143.74.2: Temporary failure in name resolution
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2600:1900:4240:200::: lookup 2600:1900:4240:200::: Temporary failure in name resolution
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2600:1900:4245:200::: lookup 2600:1900:4245:200::: Temporary failure in name resolution
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2600:1900:4242:200::: lookup 2600:1900:4242:200::: Temporary failure in name resolution
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2600:1900:4243:200::: lookup 2600:1900:4243:200::: Temporary failure in name resolution
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2600:1900:4241:200::: lookup 2600:1900:4241:200::: Temporary failure in name resolution
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2600:1901:81d4:200::: lookup 2600:1901:81d4:200::: Temporary failure in name resolution
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2600:1901:81d5:200::: lookup 2600:1901:81d5:200::: Temporary failure in name resolution
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2600:1900:4244:200::: lookup 2600:1900:4244:200::: Temporary failure in name resolution
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
B
Crawlability
robots.txt present, sitemap with 0 URLs
REVIEW
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 115 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt references sitemap

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more ▾

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more ▾

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

robots.txt 200 OK
Size 115 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
Sitemap: https://ais-pre-psgakquiwaol5aevbdjv6g-759203062707.asia-east1.run.app/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML No
B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 0 Expected: 301 redirect to HTTPS

www / non-www

https://www.global-shayari-ai.ai.studio/
200https://global-shayari-ai.ai.studio/

HTTP → HTTPS

http://global-shayari-ai.ai.studio/

HTTP version does not redirect to HTTPS

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

Connection waterfall

DNS Lookup 7 ms TCP Connect 2 ms TLS Handshake 5 ms Server Processing 1.22 s Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
67 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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: connection error, /health: connection error, /healthz: connection error, /ping: connection error, /status: connection error.
A
DNS Records
8 A records, 20 ms lookup
PASS
8 A records, 20 ms lookup
Info::
Resolves to 8 IPv4 address(es)
Got: 34.143.72.2, 34.143.79.2, 34.143.77.2, 34.143.73.2, 34.143.78.2, 34.143.75.2, 34.143.76.2, 34.143.74.2
Info::
Has 8 IPv6 (AAAA) record(s)
Got: 2600:1900:4240:200::, 2600:1900:4245:200::, 2600:1900:4242:200::, 2600:1900:4243:200::, 2600:1900:4241:200::, 2600:1901:81d4:200::, 2600:1901:81d5:200::, 2600:1900:4244:200::
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: 20 ms
Got: 20 ms
A34.143.72.2, 34.143.79.2, 34.143.77.2, 34.143.73.2, 34.143.78.2, 34.143.75.2, 34.143.76.2, 34.143.74.2
AAAA2600:1900:4240:200::, 2600:1900:4245:200::, 2600:1900:4242:200::, 2600:1900:4243:200::, 2600:1900:4241:200::, 2600:1901:81d4:200::, 2600:1901:81d5:200::, 2600:1900:4244:200::
CNAME—
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 20 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 4ms across 3 resolvers (spread 1ms)
PASS
Mean 4ms across 3 resolvers (spread 1ms)
Info::
Google: 4ms
Got: 4ms via 8.8.8.8:53
Info::
Cloudflare: 4ms
Got: 4ms via 1.1.1.1:53
Info::
Quad9: 5ms
Got: 5ms via 9.9.9.9:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://global-shayari-ai.ai.studio

https://global-shayari-ai.ai.studio

1240 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://global-shayari-ai.ai.studio2001240 msHTTP/1.1Google Frontend
A+
IPv6 Readiness
IPv6 reachable (2 ms)
PASS
IPv6 reachable (2 ms)
Info::
IPv6 is configured and reachable at 2600:1900:4240:200::, 2600:1900:4245:200::, 2600:1900:4242:200::, 2600:1900:4243:200::, 2600:1900:4241:200::, 2600:1901:81d4:200::, 2600:1901:81d5:200::, 2600:1900:4244:200::
Got: 2 ms connect
IPv6 Ready
AAAA Records 2600:1900:4240:200::, 2600:1900:4245:200::, 2600:1900:4242:200::, 2600:1900:4243:200::, 2600:1900:4241:200::, 2600:1901:81d4:200::, 2600:1901:81d5:200::, 2600:1900:4244:200:: Connection Reachable (2 ms)
Domain Intelligence
Domain intelligence data not available
INFO
Domain intelligence data not available

RDAP and WHOIS lookup both failed

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

Send Feedback