Infrastructure
· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FIPv6 ReadinessActionIPv6 records exist but unreachableFIX
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.
Learn more ▾ ▴
Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.
Source: RFC 8305 (Happy Eyeballs)
BDNSSECUnsigned (DNSSEC not deployed)REVIEW
BCAA RecordsNo CAA records (any CA may issue certificates)REVIEW
CReverse DNSAction0/4 IPs match cert SANREVIEW
BTLS Certificate Expiry & Recommendations73 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- 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
BOperational Status PageNo status page link detectedREVIEW
A+DNS Records2 A records, 33 ms lookupPASS
| A | 104.21.7.91, 172.67.135.238 |
| AAAA | 2606:4700:3036::6815:75b, 2606:4700:3031::ac43:87ee |
| CNAME | — |
| NS | perla.ns.cloudflare.com, pete.ns.cloudflare.com |
| MX | 8 route2.mx.cloudflare.net 20 route3.mx.cloudflare.net 27 route1.mx.cloudflare.net |
| TXT | google-site-verification=ap0yK4nSz-FvqTa3vai2nindMxiRYftuJVKsfEZfKwk SPF v=spf1 include:_spf.mx.cloudflare.net ~all |
| CAA | Lookup not available with standard resolver |
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
A+Multi-Resolver DNS SpeedMean 19ms across 3 resolvers (spread 20ms)PASS
A+Redirect ChainNo redirects — direct accessPASS
https://froga.io
352 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://froga.io | 200 | 352 ms | HTTP/1.1 | cloudflare |
A+Crawlabilityrobots.txt present, sitemap with 135 URLsPASS
User-Agent: *
Allow: /
Disallow: /dashboard
Disallow: /mod/
Disallow: /profile
Disallow: /settings/
Disallow: /my-tests
Disallow: /bookmarks
Disallow: /onboarding
Disallow: /auth/
Disallow: /protected
Disallow: /suspended
Disallow: /room/new
Disallow: /path/new
Sitemap: https://froga.io/sitemap.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencefroga.io — via Cloudflare, Inc, 2 months old, hosted on CloudflarePASS
286 days
July 31, 2027
73 days
Issued by Google Trust Services
2 months
Registered July 31, 2026
Status unknown
Protects against DNS spoofing
Cloudflare
ASN AS13335
104.21.7.91
Cloudflare, Inc
Expiry timeline
Recommended actions
- Newly registered domain — build backlinks and content to establish SEO trust
Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.
Informational: domain age. Newer domains may have lower trust signals in spam/security filters.
Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
Registrar lock (clientTransferProhibited et al.) prevents unauthorized domain transfers — strongest defense against domain hijacking.
Source: ICANN / domain-security best practice