Skip to content
https://www.eff.org

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
95
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
7 PASS 2 REVIEW
B
DNS Records
4 A records, 24 ms lookup
REVIEW
4 A records, 24 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 151.101.128.201, 151.101.64.201, 151.101.0.201, 151.101.192.201
Info::
Has 4 IPv6 (AAAA) record(s)
Got: 2a04:4e42:400::201, 2a04:4e42::201, 2a04:4e42:600::201, 2a04:4e42:200::201
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: eff.map.fastly.net
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 24 ms
Got: 24 ms
A151.101.128.201, 151.101.64.201, 151.101.0.201, 151.101.192.201
AAAA2a04:4e42:400::201, 2a04:4e42::201, 2a04:4e42:600::201, 2a04:4e42:200::201
CNAMEeff.map.fastly.net
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 24 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

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

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.eff.org

https://www.eff.org

5 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.eff.org2005 msHTTP/1.1nginx
A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2a04:4e42:400::201, 2a04:4e42::201, 2a04:4e42:600::201, 2a04:4e42:200::201
Got: 1 ms connect
IPv6 Ready
AAAA Records 2a04:4e42:400::201, 2a04:4e42::201, 2a04:4e42:600::201, 2a04:4e42:200::201 Connection Reachable (1 ms)
A+
Crawlability
robots.txt present, sitemap with 1 URLs
PASS
robots.txt present, sitemap with 1 URLs
Info::
robots.txt is present
Got: 3445 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1 entries
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 3445 B Sitemaps referenced 0 User-agents AhrefsBot, MJ12bot, Google-Extended, CCBot, ClaudeBot, facebookexternalhit, SemrushBot, GPTBot, anthropic-ai, * 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

# Slow down aggressive SEO crawlers
User-agent: SemrushBot
Crawl-delay: 30

User-agent: AhrefsBot
Crawl-delay: 30

User-agent: MJ12bot
Crawl-delay: 30

# AI training crawlers — higher delay (or Disallow: / if preferred)
User-agent: GPTBot
Crawl-delay: 30

User-agent: Google-Extended
Crawl-delay: 30

User-agent: CCBot
Crawl-delay: 60

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

User-agent: ClaudeBot
Crawl-delay: 30

# Meta's social preview crawler ignores Crawl-delay, but document intent
User-agent: facebookexternalhit
Crawl-delay: 10

User-agent: *
Crawl-delay: 30
# 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
# 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/

# EFF Stuff

# Don't crawl pages endlessly.
Disallow: /*?*page=
Allow: /updates?page=
Disallow: /documents?language=
Allow: /documents?page=

# Disallow language prefixes, these should be passed via the `language` param.
Disallow: /am/*
Disallow: /ar/*
Disallow: /de/*
Disallow: /el/*
Disallow: /en/*
Disallow: /es/*
Disallow: /fa/*
Disallow: /fr/*
Disallow: /hi/*
Disallow: /it/*
Disallow: /ja/*
Disallow: /ko/*
Disallow: /my/*
Disallow: /nb/*
Disallow: /nl/*
Disallow: /pl/*
Disallow: /pt/*
Disallow: /pt-br/*
Disallow: /ro/*
Disallow: /ru/*
Disallow: /sh/*
Disallow: /sv/*
Disallow: /th/*
Disallow: /tr/*
Disallow: /uk/*
Disallow: /vi/*
Disallow: /wp/*
Disallow: /zh/*
Disallow: /zh-hans/*
Disallow: /zh-hant/*

sitemap.xml 200 OK
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: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

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

Preferred variant: www

HTTP → HTTPS

301http://www.eff.org/ https://www.eff.org/

Consistent

A+
Domain Intelligence
eff.org — via Gandi SAS, 36 years old, hosted on UNWIRED - Unwired, US
PASS
eff.org — via Gandi SAS, 36 years old, hosted on UNWIRED - Unwired, US
Info::
Domain registered until Oct 9, 2026 (6 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: Gandi SAS
Info::
Hosting: UNWIRED - Unwired, US
Got: AS32354
Domain expiry

89 days

October 9, 2026

SSL certificate

45 days

Issued by Let's Encrypt

Domain age

36 years

Registered October 10, 1990

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

UNWIRED - Unwired, US

ASN AS32354

173.239.79.200

Registrar

Gandi SAS

Lock status unknown 3 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
Registrar Gandi SAS
Created October 10, 1990 (36 years ago)
Expires October 9, 2026 (6 months)
Last Updated August 15, 2025
Name Servers ns1.eff.org, ns2.eff.org, ns4.eff.org
DNSSEC Not enabled
Hosting
IP Address 173.239.79.200
ASN AS32354 (UNWIRED - Unwired, US)
Provider UNWIRED - Unwired, US
Data source: rdap (0.9s)

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

A+
HTTP Probe Timing
Total 118 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
24 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.
3 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
118 ms
Total Time Total request time from DNS lookup through full response.
118 ms

Connection waterfall

DNS Lookup 24 ms TCP Connect 0 ms TLS Handshake 3 ms Server Processing 91 ms Content Transfer 1 ms
A+
CDN & Delivery
Fastly (HIT, MISS)
PASS
Fastly (HIT, MISS)
Info::
Site is served via Fastly CDN
Got: x-served-by: cache-lga21983-LGA, cache-toj-leto2350073-TOJ
Info::
CDN cache status: HIT, MISS
CDN Detected: Fastly
Provider Fastly Cache Status HIT, MISS Evidence x-served-by: cache-lga21983-LGA, cache-toj-leto2350073-TOJ
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback