Skip to content
https://epa.gov

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
2
REVIEW
1
PASS
6
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
6 PASS 1 REVIEW 2 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
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
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 0 Expected: 301 redirect to HTTPS

www / non-www

200https://www.epa.gov/
200https://epa.gov/

Inconsistent — duplicate content risk

HTTP → HTTPS

http://epa.gov/

HTTP version does not redirect to HTTPS

D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

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

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
1 A records, 112 ms lookup
PASS
1 A records, 112 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 134.67.21.34
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2620:117:506f:15::f022
Info::
4 nameserver(s) configured
Got: dcns2.epa.gov, nccns1.epa.gov, nccns2.epa.gov, dcns1.epa.gov
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: 112 ms
Got: 112 ms
A134.67.21.34
AAAA2620:117:506f:15::f022
CNAME
NSdcns2.epa.gov, nccns1.epa.gov, nccns2.epa.gov, dcns1.epa.gov
MX
0 usepa.mail.protection.outlook.com
TXT
google-site-verification=fUmsNQhzYYZmxo4WqfmBkmwUMlk1H9ns-cGuXfwx9IM
adobe-sign-verification=24513cfcab0903ecf5de3fd467be1d7412df57793960e76577f9b27b...
mongodb-site-verification=BlMuSDOkvL0UWUVteO3W2lcTbjGdtzq7
{adobe-idp-site-verification=6c7001ef-8126-4fbc-8ecb-8fae83ee039b}
SPF v=spf1 include:spf.protection.outlook.com include:%{i}._ip.%{h}._ehlo.%{d}._spf....
MS=ms7622314
iContact1869815
adobe-idp-site-verification=6c7001ef-8126-4fbc-8fae83ee039b
CAALookup not available with standard resolver
Resolved in 112 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
1 redirect(s), 591 ms total
PASS
1 redirect(s), 591 ms total
Info::
Single redirect
Got: https://epa.gov → https://www.epa.gov/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 591 ms total
Got: 591 ms

https://epa.gov

483 ms · HTTP/1.1

301

https://www.epa.gov/

108 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://epa.gov301483 msHTTP/1.1Apache
2https://www.epa.gov/200108 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (111 ms)
PASS
IPv6 reachable (111 ms)
Info::
IPv6 is configured and reachable at 2620:117:506f:15::f022
Got: 111 ms connect
IPv6 Ready
AAAA Records 2620:117:506f:15::f022 Connection Reachable (111 ms)
A+
Crawlability
robots.txt present, sitemap with 38 URLs
PASS
robots.txt present, sitemap with 38 URLs
Info::
robots.txt is present
Got: 2035 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 38 entries
Info::
Sitemap index with 38 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 2035 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: *
# 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.txt
Disallow: /web.config
# 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: /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/
# Search pages per EPAD8-2542
Disallow: /newsreleases/search/
Disallow: /faqs/search/
Disallow: /perspectives/search/
Disallow: /publicnotices/notices-search/
Disallow: /speeches/search/
# Theme artifacts (including pattern lab):
Disallow: /themes/
Allow: /themes/*.css$
Allow: /themes/*.css?
Allow: /themes/*.js$
Allow: /themes/*.js?
Allow: /themes/*.gif
Allow: /themes/*.jpg
Allow: /themes/*.jpeg
Allow: /themes/*.png
Allow: /themes/*.svg

sitemap.xml 200 OK
Type Sitemap Index URLs 38 entries Valid XML Yes
A+
Domain Intelligence
epa.gov — via get.gov, 28 years, 11 months old
PASS
epa.gov — via get.gov, 28 years, 11 months old
Info::
Domain registered until Aug 4, 2026 (3 months remaining)
Info::
DNSSEC is enabled
Info::
Registrar: get.gov
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

21 days

August 4, 2026

SSL certificate

183 days

Issued by DigiCert Inc

Domain age

28 years, 11 months

Registered October 2, 1997

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2620:117:506f:15::f022

Registrar

get.gov

Unlocked 4 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 registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar get.gov
Created October 2, 1997 (28 years, 11 months ago)
Expires August 4, 2026 (3 months)
Last Updated August 9, 2025
Name Servers dcns1.epa.gov, dcns2.epa.gov, nccns1.epa.gov, nccns2.epa.gov
DNSSEC Enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 2620:117:506f:15::f022
Data source: rdap (0.4s)

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

Connection waterfall

DNS Lookup 21 ms TCP Connect 120 ms TLS Handshake 271 ms Server Processing 121 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback