Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.BRedirect Chain2 redirect(s), 408 ms totalREVIEW
https://amnesty.org
99 ms · HTTP/1.1
https://www.amnesty.org/
228 ms · HTTP/1.1
https://www.amnesty.org/en/
81 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://amnesty.org | 301 | 99 ms | HTTP/1.1 | cloudflare |
| 2 | https://www.amnesty.org/ | 301 | 228 ms | HTTP/1.1 | cloudflare |
| 3 | https://www.amnesty.org/en/ | 200 | 81 ms | HTTP/1.1 | cloudflare |
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
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
BCrawlabilityrobots.txt present, no sitemapREVIEW
A sitemap helps search engines discover and index your pages more efficiently.
No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.
Learn more ▾ ▴
A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.
Source: sitemaps.org / Google Search Central
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
User-agent: *
Disallow: /ar/search/
Disallow: /fr/search/
Disallow: /es/search/
Disallow: /en/search/
Disallow: /ar/wp-admin/
Disallow: /en/wp-admin/
Disallow: /es/wp-admin/
Disallow: /fr/wp-admin/
Allow: /ar/wp-admin/admin-ajax.php
Allow: /en/wp-admin/admin-ajax.php
Allow: /es/wp-admin/admin-ajax.php
Allow: /fr/wp-admin/admin-ajax.php
User-agent: CCBot
Crawl-Delay: 5
User-agent: bingbot
Crawl-Delay: 5
No sitemap found
Adding a sitemap helps search engines discover your pages.
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Preferred variant: non-www
HTTP → HTTPS
HTTP version does not redirect to HTTPS
BTLS Certificate Expiry & Recommendations60 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Submit your domain to hstspreload.org to be added to the Chrome preload list
- 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 Records2 A records, 29 ms lookupPASS
| A | 141.193.213.20, 141.193.213.21 |
| AAAA | — |
| CNAME | — |
| NS | ns-597.awsdns-10.net, ns-470.awsdns-58.com, ns-1178.awsdns-19.org, ns-1837.awsdns-37.co.uk |
| MX | 0 amnesty-org.mail.protection.outlook.com |
| TXT | ZOOM_verify_jjfeYeiShMfqUek1AEFPTM include:sendgrid.net SPF v=spf1 ip4:94.236.83.186 ip4:217.156.236.250 ip4:195.234.175.0/24 include:server... facebook-domain-verification=2aii639wnjz9r4g26gl2078donjz0z apple-domain-verification=IPplswRGbxVOGG2O |
| 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+Domain Intelligenceamnesty.org — via Network Solutions, LLC, 33 years, 10 months old, hosted on CloudflarePASS
521 days
November 19, 2027
60 days
Issued by Google Trust Services
33 years, 10 months
Registered November 20, 1992
Not enabled
Protects against DNS spoofing
Cloudflare
ASN AS209242
141.193.213.21
Network Solutions, LLC
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