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 & Recommendations36 days until leaf cert expires — 3 issues to addressREVIEW
Certificate validity
Recommended actions
- Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
- 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, 33 ms lookupPASS
| A | 151.101.129.91, 151.101.65.91, 151.101.193.91, 151.101.1.91 |
| AAAA | — |
| CNAME | — |
| NS | ns4.dnsmadeeasy.com, ns1.dnsmadeeasy.com, ns0.dnsmadeeasy.com, ns3.dnsmadeeasy.com, ns2.dnsmadeeasy.com |
| MX | 1 aspmx.l.google.com 5 alt1.aspmx.l.google.com 5 alt2.aspmx.l.google.com 10 aspmx3.googlemail.com 10 aspmx2.googlemail.com |
| TXT | tara3dnftbf2517etlfre4gvno fastly-domain-delegation-yjybcvkpvj3ahecqnztw--2024-05-06 detectify-verification=0c65d0953e7caae3977a0867fd03a843 SPF v=spf1 mx include:_spf.google.com include:spf.mandrillapp.com include:servers.mc... google-site-verification=D79z4UjzetwTnOyrlP850AizZGiQfCqJh5RCyPBDKHs MS=ms46339034 facebook-domain-verification=genf5szw1n6q0a38345igs03yvgunw 10bb9itgte1f398c4ke3888sqe j8sgjr11slij3o8el23370ckpb |
| 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.
ARedirect Chain1 redirect(s), 83 ms totalPASS
https://charitynavigator.org
6 ms · HTTP/1.1
https://www.charitynavigator.org/
77 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://charitynavigator.org | 302 | 6 ms | HTTP/1.1 | Varnish |
| 2 | https://www.charitynavigator.org/ | 200 | 77 ms | HTTP/1.1 |
See the visual redirect chain in the HTTP Probe tab →
If permanent, use 301 instead.
302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.
Learn more ▾ ▴
Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).
Source: Google Search Central
A+Crawlabilityrobots.txt present, sitemap with 614 URLsPASS
# Start Group: all
User-agent: *
Disallow:
Disallow: /cgi-bin/
Disallow: /search*
Disallow: /search/
Disallow: /confirmation/*
Disallow: /basket*
Disallow: /profile*
Disallow: https://www.charitynavigator.org/ein/86-3371262
Disallow: https://www.charitynavigator.org/ein/863371262
# End Group: all
Sitemap: https://www.charitynavigator.org/sitemap.xml
Sitemap: https://www.charitynavigator.org/extra-index.xml
- https://www.charitynavigator.org/
- https://www.charitynavigator.org/discover-charities/
- https://www.charitynavigator.org/discover-charities/cause-based-giving/
- https://www.charitynavigator.org/discover-charities/cause-based-giving/end-homelessness-fund/
- https://www.charitynavigator.org/discover-charities/cause-based-giving/end-hunger-fund/
A+Domain Intelligencecharitynavigator.org — via Network Solutions, LLC, 25 years, 2 months old, hosted on FastlyPASS
1461 days
June 15, 2030
36 days
Issued by Let's Encrypt
25 years, 2 months
Registered June 15, 2001
Not enabled
Protects against DNS spoofing
Fastly
ASN AS54113
151.101.193.91
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