Skip to content
https://taxfoundation.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
99
GRADE
A+
FIX
0
REVIEW
1
PASS
8
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
8 PASS 1 REVIEW
B
TLS Certificate Expiry & Recommendations
56 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

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 Records
1 A records, 34 ms lookup
PASS
1 A records, 34 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 23.185.0.3
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2620:12a:8000::3, 2620:12a:8001::3
Info::
4 nameserver(s) configured
Got: ns-139.awsdns-17.com, ns-1235.awsdns-26.org, ns-1800.awsdns-33.co.uk, ns-1011.awsdns-62.net
Info::
1 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: 34 ms
Got: 34 ms
A23.185.0.3
AAAA2620:12a:8000::3, 2620:12a:8001::3
CNAME—
NSns-139.awsdns-17.com, ns-1235.awsdns-26.org, ns-1800.awsdns-33.co.uk, ns-1011.awsdns-62.net
MX
0 taxfoundation-org.mail.protection.outlook.com
TXT
267C363244
SPF v=spf1 a mx ptr include:spf.protection.outlook.com include:spf.dynect.net includ...
00dj0000001rzlyea2
apple-domain-verification=mPbx7o8ujRHkicTi
google-site-verification=bN-7qDjNP_IqgiV4HXKgX5rNze_vXtger_0tG4y-k3c
MS=ms36814630
include:spf-us.emailsignatures365.com
atlassian-domain-verification=ykDElOfDhkD0ZZ+GGs7eC8ZoaZitugLS9Qzo8MI6hG6UJ/v5KR...
canva-site-verification=8AznUPvo56Es8O6TY8JF2w
CAALookup not available with standard resolver
Resolved in 34 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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://taxfoundation.org

https://taxfoundation.org

9 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://taxfoundation.org2009 msHTTP/1.1nginx
A+
IPv6 Readiness
IPv6 reachable (0 ms)
PASS
IPv6 reachable (0 ms)
Info::
IPv6 is configured and reachable at 2620:12a:8000::3, 2620:12a:8001::3
Got: 0 ms connect
IPv6 Ready
AAAA Records 2620:12a:8000::3, 2620:12a:8001::3 Connection Reachable (0 ms)
A+
Crawlability
robots.txt present, sitemap with 29 URLs
PASS
robots.txt present, sitemap with 29 URLs
Info::
robots.txt is present
Got: 885 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 29 entries
Info::
Sitemap index with 29 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 885 B Sitemaps referenced 1 User-agents GPTBot, CCBot, anthropic-ai, Claude-Web, ChatGPT-User, SemrushBot, BLEXBot, Scrapy, AhrefsBot, MJ12bot, DotBot, YandexBot, PetalBot, * Blocking No — crawling allowed
# LLM Bots - Allow with moderate crawl delay
User-agent: GPTBot
Crawl-delay: 5

User-agent: CCBot
Crawl-delay: 5

User-agent: anthropic-ai
Crawl-delay: 5

User-agent: Claude-Web
Crawl-delay: 5

User-agent: ChatGPT-User
Crawl-delay: 5

# SEO Crawler Bots - Moderate crawl delay
User-agent: AhrefsBot
Crawl-delay: 10

User-agent: SemrushBot
Crawl-delay: 10

User-agent: MJ12bot
Crawl-delay: 10

User-agent: DotBot
Crawl-delay: 10

User-agent: BLEXBot
Crawl-delay: 10

User-agent: YandexBot
Crawl-delay: 10

User-agent: PetalBot
Crawl-delay: 10

# Generic Scrapers - Higher crawl delay
User-agent: Scrapy
Crawl-delay: 30


# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow: /?s=
Disallow: /page/*/?s=
Disallow: /search/
Disallow: /wp-json/
Disallow: /?rest_route=

Sitemap: https://taxfoundation.org/sitemap_index.xml
# ---------------------------
# END YOAST BLOCK
sitemap.xml 200 OK
Type Sitemap Index URLs 29 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.taxfoundation.org/
200https://taxfoundation.org/

Preferred variant: non-www

HTTP → HTTPS

301http://taxfoundation.org/ → https://taxfoundation.org/

Consistent

A+
Domain Intelligence
taxfoundation.org — via Amazon Registrar, Inc., 30 years, 7 months old
PASS
taxfoundation.org — via Amazon Registrar, Inc., 30 years, 7 months old
Info::
Domain registered until Feb 25, 2029 (2 years, 10 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: Amazon Registrar, Inc.
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.
Domain expiry

985 days

February 25, 2029

SSL certificate

56 days

Issued by Let's Encrypt

Domain age

30 years, 7 months

Registered February 24, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2620:12a:8000::3

Registrar

Amazon Registrar, Inc.

Unlocked 4 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 Amazon Registrar, Inc.
Created February 24, 1996 (30 years, 7 months ago)
Expires February 25, 2029 (2 years, 10 months)
Last Updated December 27, 2022
Name Servers ns-1235.awsdns-26.org, ns-1011.awsdns-62.net, ns-139.awsdns-17.com, ns-1800.awsdns-33.co.uk
DNSSEC Not enabled
Hosting
IP Address 2620:12a:8000::3
Data source: rdap (0.4s)

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 46 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
38 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
0 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
2 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
46 ms
Total Time Total request time from DNS lookup through full response.
47 ms

Connection waterfall

DNS Lookup 38 ms TCP Connect 0 ms TLS Handshake 2 ms Server Processing 5 ms Content Transfer 1 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-klot8100088-CHI, cache-toj-leto2350060-TOJ, cache-toj-leto2350074-TOJ, cache-toj-leto2350074-TOJ
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-klot8100088-CHI, cache-toj-leto2350060-TOJ, cache-toj-leto2350074-TOJ, cache-toj-leto2350074-TOJ
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback