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
CCrawlabilityActionrobots.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
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
# See http://www.robotstxt.org/wc/norobots.html for documentation on how to use the robots.txt file
#
# To ban all spiders from the entire site uncomment the next two lines:
User-Agent: *
Disallow: /COP/analyzing_progress/
Disallow: /Cops/
Disallow: /docs/
Disallow: /news/
Disallow: /participant/
Disallow: /participants/
Disallow: /participants/search
Disallow: /search
Crawl-delay: 3
User-Agent: SEOkicks-Robot
Disallow: /
User-Agent: CFNetwork
Disallow: /
BTLS Certificate Expiry & Recommendations315 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 Records4 A records, 41 ms lookupPASS
| A | 18.155.129.117, 18.155.129.24, 18.155.129.105, 18.155.129.56 |
| AAAA | — |
| CNAME | — |
| NS | ns3.dnsimple.com, ns4.dnsimple-edge.org, ns2.dnsimple-edge.net, ns1.dnsimple.com |
| MX | 1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 alt3.aspmx.l.google.com 10 alt4.aspmx.l.google.com |
| TXT | google-site-verification=xzLDijG654044Rg3SixuwXOIhw4y6HkdRZ9Dnkb2FY4 google-site-verification=i49PVlc2Reww_dQWiSZaNqDkp296xzT1dS4C31bVVyM ALIAS for d1k9xa2yjbg796.cloudfront.net pardot989942=6e5edad10caa93c67b3bca58fd79e9db77692aeb6b0955e898f2db9069576bb8 asv=861cd0a0289743645ac3472bff4e5d4f MS=ms57208218 google-site-verification=CiO85Q8O6mixA6qr7eNyTWqS2ibikQdLRJeea7oHwNE asv=f2513d80ea968537ed0a87df3598715d sending_domain946683=e8936361ffc90b5e9ee70aba6cad3bbe23581382afd2a258d05e3606e2f... mandrill_verify.zQkZYMvMhCOoN8Z8il4vqw google-site-verification=1kkXq4q-gx7MA0mRhWZStelIXGGsc0wfvHl6gQfKuI0 pardot591891=f5717f17042203079a023f92ff8d677462e3ba2087abc24b112dafdb9ef739bb SPF v=spf1 include:_spf.unglobalcompact_org._d.easydmarc.pro ~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://unglobalcompact.org
494 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://unglobalcompact.org | 200 | 494 ms | HTTP/1.1 |
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligenceunglobalcompact.org — via 1API GmbH, 26 years, 9 months old, hosted on AWSPASS
2000 days
December 6, 2031
315 days
Issued by Amazon
26 years, 9 months
Registered December 6, 1999
Not enabled
Protects against DNS spoofing
AWS
ASN AS16509
18.155.129.105
1API GmbH
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