Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BCrawlabilityno robots.txt, no sitemapREVIEW
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
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.
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
No robots.txt found
This is fine for most sites — a missing robots.txt allows all crawling by default.
No sitemap found
Adding a sitemap helps search engines discover your pages.
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
HTTP → HTTPS
HTTP version does not redirect to HTTPS
BTLS Certificate Expiry & Recommendations49 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 & DeliveryCloudflareREVIEW
ADNS Records2 A records, 348 ms lookupPASS
| A | 104.18.11.31, 104.18.10.31 |
| AAAA | — |
| CNAME | — |
| NS | ns61.constellix.net, ns11.constellix.com, ns21.constellix.com, ns31.constellix.com, ns41.constellix.net, ns51.constellix.net |
| MX | 1 aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com |
| TXT | SPF v=spf1 include:servers.mcsv.net include:_spf.google.com include:sparkpostmail.co... google-site-verification=V5ZanAy0CqVq2zLLMhNEq01dqyMHRWjJx6xh0UNRhLo google-site-verification=mNkDujnPx_Ked3s-e07xeFUd7wCtib1BNkNFlok-Nsc google-site-verification=0YvDxZW-X0Hrap2-HvOasaW6dJS2VSOUXgvKylJxUEQ MS=ms23597098 bw=I8rX/v8khEjS/avbErWKCdPX5uo94GMU5H/0KfyfoQ4+ tollbit-domain-verification=28a0f41200da030331b575c81b582ac6feca635d1a428a5c231b... |
| CAA | Lookup not available with standard resolver |
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
Slow DNS adds latency to every page load. Consider a faster DNS provider.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
A+Redirect Chain0 redirect(s), 168 ms totalPASS
https://sourceforge.io
168 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://sourceforge.io | 403 | 168 ms | HTTP/1.1 | cloudflare |
A+Domain Intelligencesourceforge.io — via GoDaddy.com, LLC, 13 years, 2 months old, hosted on CloudflarePASS
269 days
April 12, 2027
49 days
Issued by Let's Encrypt
13 years, 2 months
Registered April 12, 2013
Status unknown
Protects against DNS spoofing
Cloudflare
ASN AS13335
104.18.11.31
GoDaddy.com, LLC
Expiry timeline
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