Skip to content
https://www.irs.gov

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
96
GRADE
A
FIX
1
REVIEW
2
PASS
6
INFO
0
Probed from Singapore, Singapore
200 OK
Checks
9
6 PASS 2 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.

B
DNS Records
2 A records, 12 ms lookup
REVIEW
2 A records, 12 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 23.72.88.209, 23.72.88.224
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2600:141a:8000::1748:58e0, 2600:141a:8000::1748:58d1
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: www.irs.gov.edgekey.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: 12 ms
Got: 12 ms
A23.72.88.209, 23.72.88.224
AAAA2600:141a:8000::1748:58e0, 2600:141a:8000::1748:58d1
CNAMEwww.irs.gov.edgekey.net
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 12 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
68 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

68
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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.irs.gov

https://www.irs.gov

583 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.irs.gov200583 msHTTP/1.1
A+
IPv6 Readiness
IPv6 reachable (220 ms)
PASS
IPv6 reachable (220 ms)
Info::
IPv6 is configured and reachable at 2600:141a:8000::1748:58e0, 2600:141a:8000::1748:58d1
Got: 220 ms connect
IPv6 Ready
AAAA Records 2600:141a:8000::1748:58e0, 2600:141a:8000::1748:58d1 Connection Reachable (220 ms)
A+
Crawlability
robots.txt present, sitemap with 12 URLs
PASS
robots.txt present, sitemap with 12 URLs
Info::
robots.txt is present
Got: 2257 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 12 entries
Info::
Sitemap index with 12 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 2257 B Sitemaps referenced 1 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

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


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: /*search=*

Disallow: /user/register/

Disallow: /user/password/

Disallow: /user/login/

Disallow: /user/logout/

Disallow: /zh-hans/node/

Disallow: /zh-hant/node/

Disallow: /es/node/

Disallow: /vi/node/

Disallow: /ht/node/

Disallow: /ru/node/

Disallow: /ko/node/

# Paths (no clean URLs)

Disallow: /index.php/zh-hans/node/

Disallow: /index.php/zh-hant/node/

Disallow: /index.php/es/node/

Disallow: /index.php/vi/node/

Disallow: /index.php/ht/node/

Disallow: /index.php/ru/node/

Disallow: /index.php/ko/node/

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: /filing/free-file-fillable-forms/free-file-fillable-forms-support

Disallow: /filing/free-file-fillable-forms/free-file-fillable-forms-support-2
sitemap.xml 200 OK
Type Sitemap Index URLs 12 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: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.irs.gov/
301https://irs.gov/

Preferred variant: www

HTTP → HTTPS

301http://www.irs.gov/ → https://www.irs.gov/

Consistent

A+
Domain Intelligence
irs.gov — via get.gov, 28 years, 11 months old
PASS
irs.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
Domain expiry

50 days

August 4, 2026

SSL certificate

68 days

Issued by Let's Encrypt

Domain age

28 years, 11 months

Registered October 2, 1997

DNSSEC

Enabled

Protects against DNS spoofing

Hosting

Unknown

2610:30:2000:402::110

Registrar

get.gov

Lock status unknown 2 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
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 ns0022.secondary.cloudflare.com, ns0227.secondary.cloudflare.com
DNSSEC Enabled
Registrant REDACTED FOR PRIVACY
Hosting
IP Address 2610:30:2000:402::110
Data source: rdap (0.4s)
A
HTTP Probe Timing
Total 581 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
7 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
176 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
181 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
561 ms
Total Time Total request time from DNS lookup through full response.
582 ms

Connection waterfall

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

Send Feedback