Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.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.
BTLS Certificate Expiry & Recommendations87 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
A+DNS Records2 A records, 5 ms lookupPASS
| A | 104.20.22.43, 172.66.165.111 |
| AAAA | 2606:4700:10::6814:162b, 2606:4700:10::ac42:a56f |
| CNAME | — |
| NS | cloe.ns.cloudflare.com, luke.ns.cloudflare.com |
| MX | 10 eu-smtp-inbound-psc-2.mimecast.com 10 eu-smtp-inbound-psc-1.mimecast.com |
| TXT | F6B8A410-133C-45E1-AC33-90341EF3478E MS=ms84736787 _9te8qtj4rmlwuxua043ciduvlp6m4rw access-domain-verification=dfb5c7237842564d6b1eeff1921fbef24859798f09ab16c1b1bc2... apple-domain-verification=UFzNQgPiE5z0IlC2 dpMhvKkjMkVGThsY0jSQglN4dJPF2UVd754AahXvlhCLa7C2yq88qP6xqpeKevj9LPas/BJSLX/IOGFN... f0g3n4teefc8goa6ii3mrp9h57 google-site-verification=H7CuUAcA3-Uokm17thulBfaoqZtoq3djMQzT81JcigQ google-site-verification=IKa9FbP1fhEuiqj-muIY4OoZnx27RmUf5tQWv6L2D9I google-site-verification=_pK00ji8Vtf1uZQKgf-5wZCdpxNpGtm6poi_kgSKZM8 google-site-verification=a5b0gBtpFopwLICn2EVh7slf6LHZMndVvi6r5LPYHIo SPF v=spf1 mx include:eu._netblocks.mimecast.com include:servers.mcsv.net include:sp... |
| 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.
A+Redirect Chain0 redirect(s), 22 ms totalPASS
https://iwm.org.uk
22 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://iwm.org.uk | 403 | 22 ms | HTTP/1.1 | cloudflare |
A+IPv6 ReadinessIPv6 reachable (1 ms)PASS
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Consistent
A+Domain Intelligenceiwm.org.uk — via Team Blue Internet Services UK Limited t/a Team Blue Internet Services Limited t/a names.co.uk, 29 years, 2 months oldPASS
3268 days
June 25, 2035
87 days
Issued by Let's Encrypt
29 years, 2 months
Registered June 25, 1997
Not enabled
Protects against DNS spoofing
Unknown
2606:4700:10::6814:162b
Team Blue Internet Services UK Limited t/a Team Blue Internet Services Limited t/a names.co.uk
Expiry timeline
Recommended actions
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.
Learn more ▾ ▴
DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.
Source: ICANN / RFC 4033
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