Skip to content
https://aspca.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
0
REVIEW
4
PASS
5
INFO
0
Probed from Amsterdam, Netherlands
301 Moved Permanently
Checks
9
5 PASS 4 REVIEW
B
Redirect Chain
2 redirect(s), 556 ms total
REVIEW
2 redirect(s), 556 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
HTTP to HTTPS redirect present
Info::
WWW normalization redirect
Warning::
2-hop chain could be reduced to 1 hop
Redirect directly from https://aspca.org to https://www.aspca.org/
Info::
Redirect overhead: 556 ms total
Got: 556 ms

https://aspca.org

17 ms · HTTP/1.1

301

http://www.aspca.org/

19 ms · HTTP/1.1

301

https://www.aspca.org/

520 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://aspca.org30117 msHTTP/1.1nginx
2http://www.aspca.org/30119 msHTTP/1.1cloudflare
3https://www.aspca.org/200520 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

Redirect directly from https://aspca.org to https://www.aspca.org/

Why this matters

Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.

Source: web.dev

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.aspca.org/
200https://aspca.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://aspca.org/ https://aspca.org/

Consistent

B
TLS Certificate Expiry & Recommendations
39 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

39
days left
0d 30d 60d 90d+

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • 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 Records
1 A records, 9 ms lookup
PASS
1 A records, 9 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 23.185.0.2
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: auth2.dns.cogentco.com, auth1.dns.cogentco.com
Info::
2 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 9 ms
Got: 9 ms
A23.185.0.2
AAAA
CNAME
NSauth2.dns.cogentco.com, auth1.dns.cogentco.com
MX
5 mxa-00643b01.gslb.pphosted.com
5 mxb-00643b01.gslb.pphosted.com
TXT
docusign=7bad53e4-4dc5-4886-a129-3078f2b1e40a
onetrust-domain-verification=7039d9d64d3e4e3bb7e86b9764e2db28
ZOOM_verify_V7nZAztPSH290wJxRNK_Gw
SPF v=spf1 include:44788773.spf06.hubspotemail.net include:spf.protection.outlook.co...
atlassian-domain-verification=WqLnXzAP5LY4XAjxMh6El9UVvkmuHHMF7ncvXWyx/1huT7v8Ml...
sE+XeCGRj3TDfNoxA7oDUwkQ1paLnOWABOurZepKTJbDGQPxuhPetY9L22VpIcom6Xs1FfARiaQLd+R1...
anthropic-domain-verification-c045n0=TCIigeAc3O9vNnATh5WuPhlkG
canva-site-verification=w4bZXtlDs-aYHyO0Ups-KQ
apple-domain-verification=K6D1JwllwvMtlBb1
docusign=e4d7fe35-fe2e-4203-985a-c8862362b3d4
CAALookup not available with standard resolver
Resolved in 9 ms

Multiple A records provide failover if one server goes down.

Why this matters

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.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A+
Crawlability
robots.txt present, sitemap with 2 URLs
PASS
robots.txt present, sitemap with 2 URLs
Info::
robots.txt is present
Got: 2480 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2 entries
Info::
Sitemap index with 2 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 2480 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
#
# 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: *
Crawl-delay: 10
# CSS, JS, Images
Allow: /misc/*.css$
Allow: /misc/*.css?
Allow: /misc/*.js$
Allow: /misc/*.js?
Allow: /misc/*.gif
Allow: /misc/*.jpg
Allow: /misc/*.jpeg
Allow: /misc/*.png
Allow: /modules/*.css$
Allow: /modules/*.css?
Allow: /modules/*.js$
Allow: /modules/*.js?
Allow: /modules/*.gif
Allow: /modules/*.jpg
Allow: /modules/*.jpeg
Allow: /modules/*.png
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: /themes/*.css$
Allow: /themes/*.css?
Allow: /themes/*.js$
Allow: /themes/*.js?
Allow: /themes/*.gif
Allow: /themes/*.jpg
Allow: /themes/*.jpeg
Allow: /themes/*.png
# Directories
Disallow: /includes/
Disallow: /misc/
Disallow: /modules/
Disallow: /profiles/
Disallow: /scripts/
Disallow: /themes/
# Files
Disallow: /CHANGELOG.txt
Disallow: /cron.php
Disallow: /INSTALL.mysql.txt
Disallow: /INSTALL.pgsql.txt
Disallow: /INSTALL.sqlite.txt
Disallow: /install.php
Disallow: /INSTALL.txt
Disallow: /LICENSE.txt
Disallow: /MAINTAINERS.txt
Disallow: /update.php
Disallow: /UPGRADE.txt
Disallow: /xmlrpc.php
Disallow: /apple-touch-icon-precomposed.png
Disallow: /apple-touch-icon-120x120.png
Disallow: /apple-touch-icon-120x120-precomposed.png
Disallow: /apple-touch-icon-152x152-precomposed.png
Disallow: /apple-touch-icon-152x152.png
Disallow: /humane-alliance/robots.txt
Disallow: /site/FrameSet
# 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/
# Paths (no clean URLs)
Disallow: /?q=admin/
Disallow: /?q=comment/reply/
Disallow: /?q=filter/tips/
Disallow: /?q=node/add/
Disallow: /?q=search/
Disallow: /?q=user/password/
Disallow: /?q=user/register/
Disallow: /?q=user/login/
Disallow: /?q=user/logout/

sitemap.xml 200 OK
Type Sitemap Index URLs 2 entries Valid XML Yes
A+
Domain Intelligence
aspca.org — via DomainSpot LLC, 30 years, 8 months old, hosted on Fastly
PASS
aspca.org — via DomainSpot LLC, 30 years, 8 months old, hosted on Fastly
Info::
Domain registered until Jan 5, 2027 (8 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: DomainSpot LLC
Warning::
Registrar lock is NOT enabled
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.
Info::
Hosting: Fastly
Got: AS54113
Domain expiry

170 days

January 5, 2027

SSL certificate

39 days

Issued by Let's Encrypt

Domain age

30 years, 8 months

Registered January 6, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Fastly

ASN AS54113

23.185.0.2

Registrar

DomainSpot LLC

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar DomainSpot LLC
Created January 6, 1996 (30 years, 8 months ago)
Expires January 5, 2027 (8 months)
Last Updated December 28, 2025
Name Servers auth1.dns.cogentco.com, auth2.dns.cogentco.com
DNSSEC Not enabled
Hosting
IP Address 23.185.0.2
ASN AS54113 (FASTLY - Fastly, Inc., US)
Provider Fastly
Data source: rdap (0.5s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

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.

Why this matters

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

A+
HTTP Probe Timing
Total 21 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
5 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
5 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
21 ms
Total Time Total request time from DNS lookup through full response.
22 ms

Connection waterfall

DNS Lookup 5 ms TCP Connect 1 ms TLS Handshake 5 ms Server Processing 10 ms Content Transfer 0 ms
A+
CDN & Delivery
Fastly (HIT, HIT, MISS, MISS)
PASS
Fastly (HIT, HIT, MISS, MISS)
Info::
Site is served via Fastly CDN
Got: x-served-by: cache-chi-kigq8000089-CHI, cache-rtm-ehrd2290054-RTM, cache-rtm-ehrd2290034-RTM, cache-rtm-ehrd2290034-RTM
Info::
CDN cache status: HIT, HIT, MISS, MISS
CDN Detected: Fastly
Provider Fastly Cache Status HIT, HIT, MISS, MISS Evidence x-served-by: cache-chi-kigq8000089-CHI, cache-rtm-ehrd2290054-RTM, cache-rtm-ehrd2290034-RTM, cache-rtm-ehrd2290034-RTM
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback