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.
BTLS Certificate Expiry & Recommendations61 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 Records1 A records, 16 ms lookupPASS
| A | 217.114.94.2 |
| AAAA | — |
| CNAME | — |
| NS | ns1.netnames.net, ns2.netnames.net, ns5.netnames.net, ns6.netnames.net |
| MX | 5 ofcom-org-uk.mail.protection.outlook.com |
| TXT | MS=ms32592140 MS=ms41786388 1zv458c7jd50720hknljks12mqk560br hnv9y7786y8zwqwkpx664n5jw8xgjg07 jrrnr5bt5hg6gtk97s0mqjw0tdhyjqly vj2j3gnyqmm0shs2jc7r7llvq31gn1rm ZOOM_verify_Wn0l37o_Tlq9akV8QNP6yA apple-domain-verification=H4s09S6X2K4FKHGd miro-verification=40904871ffd1929e8357920dcb9b041c9aaf7784 facebook-domain-verification=5ueypeo4znf6rqrbqm2neaxfup1x2i LD6RiTIZlhIpjsDDNyqy4w0GcjZffsmPyY4+BrlAgBYXnZ5LkCaghoiwMSmHZ52sDsvGrBKwQAY8pOhb... adobe-idp-site-verification=1ef9d93781c176548922738115ed11e6895119b4be29f8c9e498... figma-domain-verification=5bea28a359035532809d92d6ee70a6f35bb6d3820a0a6097e31340... SPF v=spf1 ip4:185.84.1.120 ip4:185.84.1.121 ip4:185.84.1.202 ip4:146.101.78.115 ip4... |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.
Learn more ▾ ▴
Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.
Source: SRE practice / DNS architecture
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), 288 ms totalPASS
https://ofcom.org.uk
31 ms · HTTP/1.1
https://www.ofcom.org.uk/
257 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://ofcom.org.uk | 301 | 31 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.ofcom.org.uk/ | 403 | 257 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
HTTP → HTTPS
Consistent
ADomain Intelligenceofcom.org.uk — via CSC Corporate Domains, Inc, 26 years, 3 months old, hosted on EPISERVER_AS, SEPASS
EXPIRED
May 31, 2026
61 days
Issued by Google Trust Services
26 years, 3 months
Registered May 31, 2000
Not enabled
Protects against DNS spoofing
EPISERVER_AS, SE
ASN AS30811
217.114.94.2
CSC Corporate Domains, Inc
Expiry timeline
Recommended actions
- Domain has EXPIRED — renew immediately to avoid total site outage
- Enable DNSSEC to protect visitors from DNS spoofing
- Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Consider enabling auto-renewal to prevent accidental expiration.
Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.
Source: ICANN renewal policy
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