Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BCrawlabilityrobots.txt present, sitemap with 0 URLsREVIEW
Search engines may not be able to parse the sitemap. Fix XML validation errors.
An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.
Learn more ▾ ▴
Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.
Source: sitemaps.org / Google Search Central
An empty sitemap provides no value. Add <url> entries for your pages.
An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.
Learn more ▾ ▴
Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.
Source: Google Search Central / sitemaps.org
# Stop anything going into these locations
User-agent: *
Disallow: /login/
Disallow: */diff/
Disallow: */source/
Disallow: */source
Disallow: */raw/
Disallow: /account/
Disallow: /search
# Do not allow changing the default per page as is not useful
Disallow: /*?*size=*
Sitemap: https://metacpan.org/sitemap-authors.xml.gz
Sitemap: https://metacpan.org/sitemap-releases.xml.gz
# Stop the bots - using signalsciences to block
BTLS Certificate Expiry & Recommendations233 days until leaf cert expires — 5 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- 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, 42 ms lookupPASS
| A | 151.101.2.217, 151.101.66.217, 151.101.130.217, 151.101.194.217 |
| AAAA | 2a04:4e42:200::729, 2a04:4e42::729, 2a04:4e42:400::729, 2a04:4e42:600::729 |
| CNAME | — |
| NS | rosa.ns.cloudflare.com, noel.ns.cloudflare.com |
| MX | 10 in1-smtp.messagingengine.com 20 in2-smtp.messagingengine.com |
| TXT | _globalsign-domain-verification=mVYWxIl-2ab_B1yPPFxEmDCLrBcl6ucouXJOU_P0_C google-site-verification=RaOtYXpRIzBroICq4P2_prM13j4MJUFITHAv7JAFouU SPF v=spf1 include:spf.messagingengine.com ?all |
| 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://metacpan.org
5 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://metacpan.org | 200 | 5 ms | HTTP/1.1 |
A+IPv6 ReadinessIPv6 reachable (0 ms)PASS
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencemetacpan.org — via pair Networks, Inc. d/b/a pair Domains, 15 years, 8 months oldPASS
2670 days
November 3, 2033
233 days
Issued by GlobalSign nv-sa
15 years, 8 months
Registered November 3, 2010
Not enabled
Protects against DNS spoofing
Unknown
2a04:4e42::729
pair Networks, Inc. d/b/a pair Domains
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