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 & Recommendations79 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- 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
BHealth Check EndpointNo conventional health endpoint foundREVIEW
A+DNS Records2 A records, 31 ms lookupPASS
| A | 172.67.130.242, 104.21.3.165 |
| AAAA | 2606:4700:3030::6815:3a5, 2606:4700:3033::ac43:82f2 |
| CNAME | — |
| NS | cass.ns.cloudflare.com, dave.ns.cloudflare.com |
| MX | 10 mx84.dns.com.cn 20 hkmx20.dns.com.cn |
| TXT | SPF v=spf1 include:spf.dns.com.cn -all |
| CAA | Lookup not available with standard resolver |
A+Subdomain TakeoverNo subdomain takeover risk detectedPASS
A+Multi-Resolver DNS SpeedMean 20ms across 3 resolvers (spread 39ms)PASS
A+Redirect ChainNo redirects — direct accessPASS
https://balford.net
79 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://balford.net | 200 | 79 ms | HTTP/1.1 | cloudflare |
A+Crawlabilityrobots.txt present, sitemap with 1801 URLsPASS
User-Agent: *
Allow: /
Disallow: /admin/
Disallow: /api/
Disallow: /assets/
Disallow: /feed/
Disallow: */feed/
Disallow: */feed
Disallow: /author/
Disallow: /trackback/
Disallow: */trackback
Disallow: /comments/
Disallow: */comments
Disallow: /?s=
Disallow: /?post_type=
User-Agent: OAI-SearchBot
User-Agent: ChatGPT-User
User-Agent: Claude-User
User-Agent: Claude-SearchBot
User-Agent: PerplexityBot
User-Agent: Perplexity-User
User-Agent: DuckAssistBot
User-Agent: cohere-ai
User-Agent: Youbot
User-Agent: MistralAI-User
User-Agent: Meta-ExternalFetcher
User-Agent: GoogleOther
Allow: /
User-Agent: GPTBot
User-Agent: ClaudeBot
User-Agent: Google-Extended
User-Agent: CCBot
User-Agent: Bytespider
User-Agent: cohere-training-data-crawler
User-Agent: Meta-ExternalAgent
User-Agent: Applebot-Extended
User-Agent: AI2Bot
User-Agent: AI2Bot-Dolma
User-Agent: img2dataset
User-Agent: ImagesiftBot
User-Agent: PanguBot
Disallow: /
Host: https://balford.net
Sitemap: https://balford.net/sitemap.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencebalford.net — via 22net, Inc., 7 years, 9 months old, hosted on CloudflarePASS
93 days
December 23, 2026
79 days
Issued by Google Trust Services
7 years, 9 months
Registered December 23, 2018
Not enabled
Protects against DNS spoofing
Cloudflare
ASN AS13335
104.21.3.165
22net, Inc.
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