Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DRedirect ChainAction2 redirect(s), 1372 ms totalFIX
https://humanesociety.org
7 ms · HTTP/1.1
https://www.humaneworld.org/
50 ms · HTTP/1.1
https://www.humaneworld.org/en
1316 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://humanesociety.org | 301 | 7 ms | HTTP/1.1 | Pantheon |
| 2 | https://www.humaneworld.org/ | 301 | 50 ms | HTTP/1.1 | nginx |
| 3 | https://www.humaneworld.org/en | 200 | 1316 ms | HTTP/1.1 | nginx |
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
BTLS Certificate Expiry & Recommendations87 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
ADNS Records1 A records, 391 ms lookupPASS
| A | 23.185.0.4 |
| AAAA | 2620:12a:8000::4, 2620:12a:8001::4 |
| CNAME | — |
| NS | ns2-05.azure-dns.net, ns1-05.azure-dns.com, ns3-05.azure-dns.org, ns4-05.azure-dns.info |
| MX | 0 humanesociety-org.mail.protection.outlook.com |
| TXT | atlassian-domain-verification=PGaihFR5P29oiU0b72DgoPQ8Pp6UvE5-+EfVcDp/oWUdBAIzy3... google-site-verification=W4WZ_HYh604P6-CFFVLAWPXXr5_5-X6ppqK4LYblPTY google-site-verification=URsPbJktc9XGgRNBKwfAfMuDiX0nr5axTtvADPOBauU google-site-verification=KbRsODSMl7YSpM9YzR_cNlyUOk7jLStmjgwALt2RlG0 SPF v=spf1 include:spf.protection.outlook.com include:_spf.psm.knowbe4.com include:_... dropbox-domain-verification=3eflsbq1xbel openai-domain-verification=dv-ekM3Ve0shSx36XWfzKK84tuG K3KKruTn/evRRClZtmREi3Q0FDZTgTxSMwEWY/omr978ElVy+Qz+bukf2JDKo1S9JxFLP6YOMw2x9RoO... docusign=8cb80911-5977-4747-9e78-d9e25515ac99 smartsheet-site-validation=JgalNZUcCzazAwCz0r9QaLx8OYdITofp amazonses:1vDgGITwjnTd+hJDKB92GTed7jnwju93s62iILdbNVs= google-site-verification=545RzPeGVPYnBMCnzTbbQ0JpqS9MrZaoIbhZpCUUK4A intacct-esk=603F28FE0D2014B7E0538C06A8C0F42F adobe-idp-site-verification=a6d28ba5aa89be374213896bde9e62fc1b99ca590ad9db9a3826... docusign=69712210-5cdd-47a1-a39c-7ca5842a6639 google-site-verification=FHmYhM__-SDOWKTykQ3FTT-k4LrAF624S4kpRSKsfTE google-site-verification=v9ZAi83rvWjwKscF6Jqw3EEU1B-Ro21Jr552jFLof1c _b7b23lw1entwgaq3l02hku7xl299pmn |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.
Learn more ▾ ▴
Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.
Source: SRE practice / DNS architecture
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.
Slow DNS adds latency to every page load. Consider a faster DNS provider.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
A+IPv6 ReadinessIPv6 reachable (1 ms)PASS
A+Crawlabilityrobots.txt present, sitemap with 4563 URLsPASS
#
# robots.txt
#
# This file is to prevent the crawling and indexing of certain parts
# of your site by web crawlers and spiders run by sites like Yahoo!
# and Google. By telling these "robots" where not to go on your site,
# you save bandwidth and server resources.
#
# This file will be ignored unless it is at the root of your host:
# Used: http://example.com/robots.txt
# Ignored: http://example.com/site/robots.txt
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/robotstxt.html
User-agent: *
# CSS, JS, Images
Allow: /core/*.css$
Allow: /core/*.css?
Allow: /core/*.js$
Allow: /core/*.js?
Allow: /core/*.gif
Allow: /core/*.jpg
Allow: /core/*.jpeg
Allow: /core/*.png
Allow: /core/*.svg
Allow: /profiles/*.css$
Allow: /profiles/*.css?
Allow: /profiles/*.js$
Allow: /profiles/*.js?
Allow: /profiles/*.gif
Allow: /profiles/*.jpg
Allow: /profiles/*.jpeg
Allow: /profiles/*.png
Allow: /profiles/*.svg
# Directories
Disallow: /core/
Disallow: /profiles/
# Files
Disallow: /README.md
Disallow: /composer/Metapackage/README.txt
Disallow: /composer/Plugin/ProjectMessage/README.md
Disallow: /composer/Plugin/Scaffold/README.md
Disallow: /composer/Plugin/VendorHardening/README.txt
Disallow: /composer/Template/README.txt
Disallow: /modules/README.txt
Disallow: /sites/README.txt
Disallow: /themes/README.txt
# Paths (clean URLs)
Disallow: /admin/
Disallow: /comment/reply/
Disallow: /filter/tips
Disallow: /node/add/
Disallow: /search/
Disallow: /user/register
Disallow: /user/password
Disallow: /user/login
Disallow: /user/logout
Disallow: /media/oembed
Disallow: /*/media/oembed
# Paths (no clean URLs)
Disallow: /index.php/admin/
Disallow: /index.php/comment/reply/
Disallow: /index.php/filter/tips
Disallow: /index.php/node/add/
Disallow: /index.php/search/
Disallow: /index.php/user/password
Disallow: /index.php/user/register
Disallow: /index.php/user/login
Disallow: /index.php/user/logout
Disallow: /index.php/media/oembed
Disallow: /index.php/*/media/oembed
#
# Customizations applied to robots.txt through the hsus-robots.txt
# file via composer.
#
Sitemap: https://www.humaneworld.org/sitemap.xml
Disallow: /en/search?
Disallow: /search?
Disallow: /en/sitewide_alert/load
- https://www.humaneworld.org/en
- https://www.humaneworld.org/en/news/safari-club-internationals-annual
- https://www.humaneworld.org/en/news/undercover-investigation-illegal-wildlife-safari-club
- https://www.humaneworld.org/en/news/tiger-found-caged-abandoned
- https://www.humaneworld.org/en/news/new-sanctuary-added-wildlands
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligencehumanesociety.org — via CSC Corporate Domains, Inc., 29 years, 3 months oldPASS
1452 days
June 5, 2030
87 days
Issued by Let's Encrypt
29 years, 3 months
Registered June 6, 1997
Not enabled
Protects against DNS spoofing
Unknown
2620:12a:8001::4
CSC Corporate Domains, Inc.
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