Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BCrawlabilityrobots.txt present, no sitemapREVIEW
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
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
User-agent: *
Disallow: /images/
Disallow: /libraries/
Disallow: /preview/
Disallow: /templates/
Disallow: /cgi-bin/download.plx?dli=*
Allow: /cgi-bin/download.plx$
Disallow: /forum/index.php?action=login*
Disallow: /forum/index.php?action=register*
Disallow: /forum/index.php?action=search*
Disallow: /forum/index.php?action=reminder*
Disallow: /forum/index.php?action=profile*
Disallow: /forum/index.php?action=unread*
Disallow: /forum/index.php?action=verificationcode*
Disallow: /forum/index.php?action=printpage*
Disallow: /forum/index.php?*;wap
Disallow: /forum/index.php?*;wap2
Disallow: /forum/index.php?*;imode
No sitemap found
Adding a sitemap helps search engines discover your pages.
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations48 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Add includeSubDomains to the HSTS directive
- Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+DNS Records2 A records, 195 ms lookupPASS
| A | 104.21.54.133, 172.67.138.207 |
| AAAA | 2606:4700:3033::ac43:8acf, 2606:4700:3035::6815:3685 |
| CNAME | — |
| NS | kirk.ns.cloudflare.com, jessica.ns.cloudflare.com |
| MX | 10 mail.finetworks.fi |
| TXT | SPF v=spf1 +include:_spf.finetworks.fi ?all google-site-verification=56p73o8-6Kw0DvwtYs_e8Eo9VBNgvVAAZid7Fph5Jxo |
| 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.
ARedirect Chain1 redirect(s), 783 ms totalPASS
https://apachehaus.com
750 ms · HTTP/1.1
http://www.apachehaus.com/
33 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://apachehaus.com | 301 | 750 ms | HTTP/1.1 | cloudflare |
| 2 | http://www.apachehaus.com/ | 301 | 33 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+IPv6 ReadinessIPv6 reachable (2 ms)PASS
A+Domain Intelligenceapachehaus.com — via DomainSite, Inc., 17 years, 8 months oldPASS
1242 days
November 6, 2029
48 days
Issued by Google Trust Services
17 years, 8 months
Registered November 6, 2008
Enabled
Protects against DNS spoofing
Unknown
2606:4700:3033::ac43:8acf
DomainSite, Inc.
Expiry timeline
Recommended actions
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
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