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)
BTLS Certificate Expiry & Recommendations314 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
A+DNS Records4 A records, 10 ms lookupPASS
| A | 18.173.121.11, 18.173.121.53, 18.173.121.4, 18.173.121.59 |
| AAAA | 2600:9000:25f2:400:1e:6cc8:7300:93a1, 2600:9000:25f2:6c00:1e:6cc8:7300:93a1, 2600:9000:25f2:1000:1e:6cc8:7300:93a1, 2600:9000:25f2:de00:1e:6cc8:7300:93a1, 2600:9000:25f2:8200:1e:6cc8:7300:93a1, 2600:9000:25f2:ba00:1e:6cc8:7300:93a1, 2600:9000:25f2:7000:1e:6cc8:7300:93a1, 2600:9000:25f2:ee00:1e:6cc8:7300:93a1 |
| CNAME | — |
| NS | ns-1081.awsdns-07.org, ns-1635.awsdns-12.co.uk, ns-516.awsdns-00.net, ns-85.awsdns-10.com |
| MX | 5 matomo.alwaysdata.net 10 mx1.alwaysdata.com 15 mx2.alwaysdata.com |
| TXT | SPF v=spf1 include:_spf.alwaysdata.com include:helpscoutemail.com include:spf.em.sec... |
| 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+Redirect ChainNo redirects — direct accessPASS
https://matomo.org
29 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://matomo.org | 200 | 29 ms | HTTP/1.1 | Apache |
A+Crawlabilityrobots.txt present, sitemap with 12 URLsPASS
User-agent: *
Disallow: /wp-admin/
Disallow: /recommends/
Disallow: /e-landing-page-sitemap.xml
Disallow: /post_tag-sitemap.xml
Disallow: /author-sitemap.xml
Disallow: /category-sitemap.xml
Allow: /wp-admin/admin-ajax.php
Crawl-delay: 20
Sitemap: https://matomo.org/sitemap_index.xml
- https://matomo.org/post-sitemap.xml
- https://matomo.org/page-sitemap.xml
- https://matomo.org/landing_pages-sitemap...
- https://matomo.org/topic-sitemap.xml
- https://matomo.org/subcategory-sitemap.x...
- https://matomo.org/subcategory_link-site...
- https://matomo.org/guide-sitemap.xml
- https://matomo.org/faq-sitemap.xml
- https://matomo.org/faq-sitemap2.xml
- https://matomo.org/changelog-sitemap.xml
- https://matomo.org/category-sitemap.xml
- https://matomo.org/post_tag-sitemap.xml
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencematomo.org — via OVH sas, 8 years, 8 months old, hosted on AWSPASS
2276 days
September 8, 2032
314 days
Issued by Amazon
8 years, 8 months
Registered September 8, 2017
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
18.173.121.11
OVH sas
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