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
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
Consistent
BTLS Certificate Expiry & Recommendations85 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- 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
BCDN & DeliveryNetlifyREVIEW
A+DNS Records1 A records, 47 ms lookupPASS
| A | 75.2.60.5 |
| AAAA | — |
| CNAME | — |
| NS | ns-cloud-c4.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com, ns-cloud-c1.googledomains.com |
| MX | 10 eu-smtp-inbound-1.mimecast.com 10 eu-smtp-inbound-2.mimecast.com |
| TXT | google-site-verification=akxKU-zrWmRZSmmxugc9kusVfEEdeYJV3PbStkoiY-Y canva-site-verification=Oj4N5oGpYSbYgODtUbBBDg google-site-verification=vC49jK7n1XxyANkEiyYJd55kZHwDKB3e30LFKTjccI4 SPF v=spf1 include:theaccessgroupSPF.smtp.com include:_spf.google.com include:server... google-site-verification=oOYyOd37U0rXlQri1c6ZZ0G0otUD160UEzhpWrBQptE google-site-verification=Pjdis7iP8ZRWDqIUuQ323V03wOsAL2vWKPWD9eqCdIM |
| 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), 251 ms totalPASS
https://ellenmacarthurfoundation.org
98 ms · HTTP/1.1
https://www.ellenmacarthurfoundation.org...
153 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://ellenmacarthurfoundation.org | 301 | 98 ms | HTTP/1.1 | Netlify |
| 2 | https://www.ellenmacarthurfoundation.org... | 200 | 153 ms | HTTP/1.1 | Netlify |
See the visual redirect chain in the HTTP Probe tab →
A+Crawlabilityrobots.txt present, sitemap with 6 URLsPASS
User-agent: *
Allow: /
Sitemap: https://www.ellenmacarthurfoundation.org/sitemap-index.xml
A+Domain Intelligenceellenmacarthurfoundation.org — via IONOS SE, 17 years, 7 months old, hosted on AWSPASS
897 days
November 28, 2028
85 days
Issued by Let's Encrypt
17 years, 7 months
Registered November 28, 2008
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
75.2.60.5
IONOS SE
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