Skip to main content

Security report for irs.gov

Internal Revenue Service · Government · United States

Low risk. 3 critical or high findings in Security headers and GDPR outside view.

Security score

76/100

Risk levelLow

0–100, higher is better. How it is calculated

The Internal Revenue Service (IRS) website serves as the official digital presence of the U.S. federal tax authority, providing comprehensive tax-related information, services, and tools to individuals, businesses, tax professionals, and international filers. The site is well-branded with consistent government identity markers and offers multi-language support to cater to diverse audiences. It is positioned as the authoritative source for federal tax filing, payments, refunds, and compliance guidance. Technically, the website is built on Drupal 10 CMS, leveraging modern web technologies including Google Tag Manager and Analytics for tracking and performance monitoring. The site demonstrates good mobile optimization, accessibility, and SEO practices, ensuring a positive user experience across devices. Hosting appears to be government-managed or via Akamai CDN, supporting reliable performance. From a security perspective, the site enforces HTTPS and follows best practices in form security and data handling. While explicit security headers are not visible in the HTML, the overall posture is strong with no detected vulnerabilities or exposed sensitive data. Privacy compliance is robust with a comprehensive privacy policy, though cookie consent mechanisms and terms of service pages could be enhanced. The WHOIS data is limited due to .gov domain privacy but aligns with expected government ownership, supporting legitimacy. Overall, the IRS website is a highly credible, secure, and user-friendly platform essential for federal tax administration. Strategic recommendations include enhancing visible security policies, adding cookie consent for compliance, and improving contact information accessibility to further strengthen trust and compliance.

Scanned

This is an earlier scan of irs.gov. View the latest report

NIS2 and GDPR posture

GDPR outside view
58/ 100 · Medium
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

3 findings rated critical or high. Fix these first.

  1. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

Need hands-on remediation? Email guard@offseq.com

Keep watching irs.gov

This scan found 18 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. See sample alerts.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
95
Security headers
55
Email security
70
DNS health
80
Network security
100
GDPR outside view
58
Average
76

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

The IRS operates as a critical government agency responsible for tax collection and enforcement in the United States. Its market position is unique as the sole federal tax authority, serving a broad customer base including individuals, businesses, nonprofits, and international taxpayers. The business model is non-commercial, focused on public service and regulatory compliance. Revenue streams are government-funded, with no commercial transactions on the site itself. The IRS maintains partnerships with related government entities such as the U.S. Treasury and oversight bodies. Growth indicators are tied to legislative changes and tax policy updates, reflected in the site's content and tools. The agency's digital presence supports operational efficiency and taxpayer engagement, with a strong ecosystem of related government portals and services.

Security posture

The IRS website exhibits a mature security posture appropriate for a high-profile government entity. HTTPS is enforced site-wide, ensuring encrypted communications. The absence of exposed sensitive data and secure handling of forms indicate good operational security. However, explicit security headers like Content-Security-Policy and X-Frame-Options are not visible in the HTML and should be verified server-side. No incident response or vulnerability disclosure information is publicly available, which could be improved to enhance transparency and readiness. Privacy compliance is strong with a detailed privacy policy, though cookie consent mechanisms are lacking. Overall, the site balances accessibility with security effectively, but could benefit from enhanced visible security documentation and user-facing controls.

Recommendations

  1. Publish and verify explicit security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to strengthen browser security.
  2. Implement a cookie consent banner or mechanism to comply with privacy regulations and enhance user transparency.
  3. Create and prominently link a terms of service page to clarify user rights and responsibilities.
  4. Provide clear and accessible contact information including security incident response contacts to improve trust and facilitate communication.
  5. Regularly audit third-party scripts and tracking tools to minimize privacy risks and ensure compliance with data protection standards.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Internal Revenue Service
Description
Pay your taxes. Get your refund status. Find IRS forms and answers to tax questions. We help you understand and meet your federal tax responsibilities.
Key services
Tax filing information and assistance, Refund status tracking, Tax payment processing, Forms and instructions, Identity protection PIN issuance, Taxpayer assistance centers locator
Content quality
excellent
Branding
consistent

Technology

Stack
Drupal 10, Google Tag Manager, Google Analytics, AddToAny sharing, jQuery
Frameworks
Drupal CMS
Performance
moderate
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Secure forms with autocomplete off
  • Use of official .gov domain

Analytics and tracking

Services
Google Analytics, Google Tag Manager, DigitalGov Analytics
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
DigitalGov Analytics
Marketing tools
AddToAny sharing
Transparency
basic

Site quality

Design
excellent
User experience
excellent
Content relevance
excellent
Navigation
excellent
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Official U.S. government website with .gov domain
  2. Comprehensive tax-related content and services
  3. Multi-language support with hreflang tags
  4. Use of Drupal 10 CMS and modern web technologies
  5. Strong branding and trust indicators
  6. No signs of phishing or malware
  7. No visible contact emails or phone numbers on homepage
  8. Privacy policy present and detailed
  9. No cookie consent banner detected
  10. No terms of service page explicitly found
Technical notes

Notes

The IRS website is built on a modern Drupal 10 CMS platform, utilizing JavaScript libraries such as jQuery and integrating Google Tag Manager and Analytics for data collection and performance monitoring. The site employs responsive design techniques ensuring excellent mobile optimization and accessibility. Hosting appears to leverage government infrastructure and Akamai CDN for content delivery. Performance is moderate with room for optimization in script loading and caching. The site includes multi-language support with hreflang tags, enhancing international usability. Technical debt appears low, with a clean and structured HTML markup. Opportunities exist to enhance security headers and implement cookie consent mechanisms to align with evolving compliance requirements.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Earlier scans of this domain

  1. 76/100Low26 findingsView report
  2. 76/100Low26 findingsView report
Reviews of this site

Share your experience with irs.gov. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review irs.gov.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.