Infrastructure
· 9 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)
DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BRedirect Chain2 redirect(s), 490 ms totalREVIEW
https://cleverreach.com
114 ms · HTTP/1.1
http://www.cleverreach.com/
105 ms · HTTP/1.1
https://www.cleverreach.com/
271 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://cleverreach.com | 301 | 114 ms | HTTP/1.1 | |
| 2 | http://www.cleverreach.com/ | 301 | 105 ms | HTTP/1.1 | LiteSpeed |
| 3 | https://www.cleverreach.com/ | 200 | 271 ms | HTTP/1.1 | LiteSpeed |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
Redirect directly from https://cleverreach.com to https://www.cleverreach.com/
Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.
Source: web.dev
CURL VariantsActionwww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Use 301 (permanent) instead of 302 (temporary)
BTLS Certificate Expiry & Recommendations84 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
A+DNS Records3 A records, 38 ms lookupPASS
| A | 54.171.139.81, 52.30.247.193, 52.48.120.210 |
| AAAA | 2a01:578:3::341e:f7c1, 2a01:578:3::36ab:8b51, 2a01:578:3::3430:78d2 |
| CNAME | — |
| NS | ns-465.awsdns-58.com, ns-1432.awsdns-51.org, ns-722.awsdns-26.net, ns-2034.awsdns-62.co.uk |
| MX | 1 mercury.cleverreach.com 115 rxiwfcu5mvlabgu7wgth6l2fbq6xwiftlwglrnpuzhp64d3nlp2a.mx-verification.google.com |
| TXT | SPF v=spf1 include:spf.crsend.com include:mail.zendesk.com include:_spf.google.com a... mailru-verification: 358bb31855cb450e google-site-verification=FreAKHgAa83z6kfqMSpOwTiRe3St5SGw07VBJe_ekEU |
| 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+Crawlabilityrobots.txt present, sitemap with 8 URLsPASS
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Sitemap: https://www.cleverreach.com/de-de/sitemap_index.xml
- https://www.cleverreach.com/de-de/post-s...
- https://www.cleverreach.com/de-de/page-s...
- https://www.cleverreach.com/de-de/case-s...
- https://www.cleverreach.com/de-de/presse...
- https://www.cleverreach.com/de-de/partne...
- https://www.cleverreach.com/de-de/integr...
- https://www.cleverreach.com/de-de/newsle...
- https://www.cleverreach.com/de-de/catego...
A+Domain Intelligencecleverreach.com — via Mesh Digital Limited, 19 years, 6 months oldPASS
200 days
February 1, 2027
84 days
Issued by Let's Encrypt
19 years, 6 months
Registered February 1, 2007
Not enabled
Protects against DNS spoofing
Unknown
2a01:578:3::3430:78d2
Mesh Digital Limited
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