Skip to content
https://energystar.gov

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 3 REVIEW 1 FIX
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.

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.energystar.gov/
200https://energystar.gov/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://energystar.gov/ https://www.energystar.gov/

Consistent

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

Certificate validity

244
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
  • 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, 1126 ms lookup
PASS
1 A records, 1126 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 204.47.252.17
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: nccns2.epa.gov, dcns1.epa.gov, dcns2.epa.gov, nccns1.epa.gov
Info::
4 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
Warning::
DNS resolution is slow (1126 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 1126 ms
A204.47.252.17
AAAA
CNAME
NSnccns2.epa.gov, dcns1.epa.gov, dcns2.epa.gov, nccns1.epa.gov
MX
5 grid1f.gseg.att.com
10 grid2f.gseg.att.com
50 grid1f6.gseg.att.com
55 grid2f6.gseg.att.com
TXT
SPF v=spf1 include:_spf.salesforce.com include:_epamail.epa.gov -all
facebook-domain-verification=ikcraqe2dno6r77hs7a6jgvhhrhxxz
CAALookup not available with standard resolver
Resolved in 1126 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.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A
Redirect Chain
1 redirect(s), 990 ms total
PASS
1 redirect(s), 990 ms total
Info::
Single redirect
Got: https://energystar.gov → https://www.energystar.gov/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 990 ms total
Got: 990 ms

https://energystar.gov

473 ms · HTTP/1.1

301

https://www.energystar.gov/

517 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://energystar.gov301473 msHTTP/1.1nginx
2https://www.energystar.gov/200517 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 18324 URLs
PASS
robots.txt present, sitemap with 18324 URLs
Info::
robots.txt is present
Got: 2433 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 18324 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 2433 B Sitemaps referenced 1 User-agents usasearch, *, ClaudeBot 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: usasearch

Allow: /buildings/tools-and-resources

Allow: /products/tools_resources

Allow: /products/ask-the-experts


User-agent: *

Sitemap: https://www.energystar.gov/sitemap.xml

# 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

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

Disallow: /media/oembed

Disallow: /*/media/oembed

Disallow: /buildings/tools-and-resources

Disallow: /products/tools_resources

Disallow: /products/ask-the-experts

# 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


User-agent: ClaudeBot

Disallow: /
A+
Domain Intelligence
energystar.gov — via get.gov, 28 years, 11 months old, hosted on EPA-NET - Environmental Protection Agency, US
PASS
energystar.gov — via get.gov, 28 years, 11 months old, hosted on EPA-NET - Environmental Protection Agency, US
Info::
Domain registered until Sep 5, 2026 (4 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.
Info::
Hosting: EPA-NET - Environmental Protection Agency, US
Got: AS14298
Domain expiry

49 days

September 5, 2026

SSL certificate

244 days

Issued by DigiCert Inc

Domain age

28 years, 11 months

Registered October 2, 1997

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

EPA-NET - Environmental Protection Agency, US

ASN AS14298

204.47.252.17

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 September 5, 2026 (4 months)
Last Updated March 10, 2026
Name Servers dcns1.epa.gov, dcns2.epa.gov, nccns1.epa.gov, nccns2.epa.gov
DNSSEC Enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 204.47.252.17
ASN AS14298 (EPA-NET - Environmental Protection Agency, US)
Provider EPA-NET - Environmental Protection Agency, US
Data source: rdap (0.6s)

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

Connection waterfall

DNS Lookup 117 ms TCP Connect 117 ms TLS Handshake 235 ms Server Processing 117 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