Skip to content
https://snai.it

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
71
GRADE
C
FIX
1
REVIEW
11
PASS
4
INFO
1
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
4 PASS 11 REVIEW 1 FIX
F
Multi-Resolver DNS Speed
Action
All public resolvers failed to resolve the domain
FIX
All public resolvers failed to resolve the domain
Critical::
DNS resolution failed against all public resolvers
1.1.1.1, 8.8.8.8, and 9.9.9.9 all failed to resolve this domain. Almost always means the domain is delegated incorrectly, the authoritative servers are unreachable, or the resolution returned NXDOMAIN/SERVFAIL across the board.
C
DNSSEC
Action
DNSSEC posture not checked
REVIEW
DNSSEC posture not checked
Info::
DNSSEC posture not checked
Could not query the validating resolver for DNSSEC status. Network or resolver outage.
C
CAA Records
Action
CAA posture not checked
REVIEW
CAA posture not checked
Info::
CAA records not checked
Could not query the resolver for CAA records. Network or resolver outage.
B
Reverse DNS
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR for 95.101.38.130 does not match any cert SAN: a95-101-38-130.deploy.static.akamaitechnologies.com
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 95.101.38.179 does not match any cert SAN: a95-101-38-179.deploy.static.akamaitechnologies.com
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.
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

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
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.snai.it/
200https://snai.it/

HTTP → HTTPS

http://snai.it/

HTTP version does not redirect to HTTPS

B
TLS Certificate Expiry & Recommendations
124 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

124
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
B
CDN & Delivery
Akamai
REVIEW
Akamai
Info::
Site is served via Akamai CDN
Got: server header
CDN Detected: Akamai
Provider Akamai Evidence server header
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
2 A records, 54 ms lookup
PASS
2 A records, 54 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 95.101.38.130, 95.101.38.179
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: a10-67.akam.net, a16-65.akam.net, a8-67.akam.net, a5-66.akam.net, a1-4.akam.net, a13-64.akam.net
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 54 ms
Got: 54 ms
A95.101.38.130, 95.101.38.179
AAAA—
CNAME—
NSa10-67.akam.net, a16-65.akam.net, a8-67.akam.net, a5-66.akam.net, a1-4.akam.net, a13-64.akam.net
MX
10 mxa-0050fd01.gslb.pphosted.com
10 mxb-0050fd01.gslb.pphosted.com
TXT
_y0fb25jvbilrwc36buwdvd90ik3h47e
_w0ebgkytmv3oclxhulwi98b6qaez2u9
_globalsign-domain-verification=IN1MunHGDXLhVEB9MtIHiJUaL3vn1xBDkkf1tI4SEa
MS=ms36389182
SPF v=spf1 include:%{ir}.%{v}.%{d}.spf.has.pphosted.com ~all
CpKDT7Pdd7GIThaYgL2MC/xhm1fpNI26lDW3A4wFgtuPY0WpPtap0pgyQMKpXwjJgT29O2yt1iqoi5nm...
google-site-verification=Oj0jPULddOsEuPyZMAS9X8ZWiX878b1ntvB2arHYp7E
CAALookup not available with standard resolver
Resolved in 54 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Redirect Chain
0 redirect(s), 11 ms total
PASS
0 redirect(s), 11 ms total

https://snai.it

11 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://snai.it30111 msHTTP/1.1AkamaiGHost
A+
HTTP Probe Timing
Total 87 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
47 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 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.
87 ms
Total Time Total request time from DNS lookup through full response.
87 ms

Connection waterfall

DNS Lookup 47 ms TCP Connect 1 ms TLS Handshake 5 ms Server Processing 34 ms Content Transfer 0 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