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
BReverse DNS0/2 IPs match cert SANREVIEW
BMulti-Resolver DNS SpeedMean 114ms across 3 resolvers (spread 176ms)REVIEW
BTLS Certificate Expiry & Recommendations57 days until leaf cert expires — 5 issues to addressREVIEW
Certificate validity
Recommended actions
- Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
- Add includeSubDomains to the HSTS directive
- 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
ADNS Records1 A records, 324 ms lookupPASS
| A | 23.227.38.66 |
| AAAA | 2620:127:f00f:6:: |
| CNAME | — |
| NS | ns-cloud-b4.googledomains.com, ns-cloud-b1.googledomains.com, ns-cloud-b2.googledomains.com, ns-cloud-b3.googledomains.com |
| MX | 1 aspmx.l.google.com 5 alt2.aspmx.l.google.com 5 alt1.aspmx.l.google.com 10 alt4.aspmx.l.google.com 10 alt3.aspmx.l.google.com |
| TXT | google-site-verification=GapWkpCefAvtXOEhwuy2osp62D40UG0QPJ2d3oItk-Q SPF v=spf1 include:mailgun.org include:_spf.google.com ~all google-site-verification=OtRlV80old6OqAAEEq19FBueeenI6biNLIsE8c50KPw |
| 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
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+Subdomain TakeoverNo subdomain takeover risk detectedPASS
A+Redirect ChainNo redirects — direct accessPASS
https://peakhealthandfitness.co.uk
308 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://peakhealthandfitness.co.uk | 200 | 308 ms | HTTP/1.1 | cloudflare |
A+Crawlabilityrobots.txt present, sitemap with 5 URLsPASS
User-agent: *
Disallow: /admin
Disallow: /cart
Disallow: /checkout
Disallow: /orders
Disallow: /account
Disallow: /search
Disallow: /apple-app-site-association
# =========================
# BLOCK DUPLICATE & LOW VALUE URL PARAMETERS
# =========================
Disallow: /*?*sort_by=
Disallow: /*?*filter=
Disallow: /*?*variant=
Disallow: /*?*view=
Disallow: /*?*grid_list=
Disallow: /*?*page=
Disallow: /*?*section_id=
Disallow: /*?*utm_
Disallow: /*?*ref=
Disallow: /*?*fbclid=
Disallow: /*?*gclid=
Disallow: /*?*price=
Disallow: /*?*rating=
Disallow: /*?*color=
Disallow: /*?*size=
# =========================
# ALLOW CORE SEO PAGES
# =========================
Allow: /collections/
Allow: /collections/*/products/
Allow: /products/
Allow: /blogs/
Allow: /pages/
# =========================
# IMPORTANT: ALLOW PAGINATION CLEANLY
# =========================
Allow: /*?page=
# =========================
# BLOCK INTERNAL DUPLICATE PATHS
# =========================
Disallow: /collections/*+*
Disallow: /collections/*%2B*
Disallow: /collections/*%20*
# =========================
# CRAWL DELAY (OPTIONAL - SOME BOTS IGNORE)
# =========================
User-agent: bingbot
Crawl-delay: 5
# =========================
# BLOCK AGGRESSIVE / LOW VALUE BOTS (OPTIONAL)
# =========================
User-agent: AhrefsBot
Disallow: /
User-agent: SemrushBot
Disallow: /
User-agent: MJ12bot
Disallow: /
User-agent: DotBot
Disallow: /
# =========================
# ALLOW GOOGLE FULL ACCESS
# =========================
User-agent: Googlebot
Disallow:
# =========================
# SITEMAP
# =========================
Sitemap: https://peakhealthandfitness.co.uk/sitemap.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencepeakhealthandfitness.co.uk — via Tucows Inc t/a Tucows, 2 years, 6 months oldPASS
181 days
November 24, 2026
57 days
Issued by Let's Encrypt
2 years, 6 months
Registered November 24, 2023
Not enabled
Protects against DNS spoofing
Unknown
2620:127:f00f:6::
Tucows Inc t/a Tucows
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