Skip to main content

Security report for treasury.gov

U.S. Department of the Treasury · Government · United States

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

Security score

75/100

Risk levelMedium

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

The U.S. Department of the Treasury website serves as the official digital presence of the U.S. federal agency responsible for managing national finances, economic policy, and regulatory enforcement. The site provides comprehensive information on Treasury leadership, policy issues, data resources, services, and news updates. It targets a broad audience including the general public, businesses, financial institutions, and government entities. The website is built on a modern Drupal 10 CMS platform with integration of U.S. Web Design System (USWDS) standards, ensuring accessibility, mobile responsiveness, and a professional user experience. From a technical perspective, the site employs secure HTTPS connections, uses reputable third-party analytics and tracking tools such as Google Analytics and Akamai mPulse, and leverages content delivery networks for performance optimization. The site demonstrates strong branding consistency and trust indicators typical of official government domains, including the use of a .gov domain and official seals. Security posture is robust with no visible vulnerabilities or exposed sensitive data, although explicit security headers and vulnerability disclosure mechanisms could be more clearly documented. Overall, the website reflects a mature digital infrastructure aligned with government standards, providing reliable and authoritative content. Privacy compliance is generally good with a comprehensive privacy policy, but the absence of a cookie consent mechanism and explicit incident response contacts are areas for improvement. The domain's WHOIS data is unavailable due to .gov domain restrictions, which is standard and does not detract from legitimacy. The site is safe for general audiences and free from any adult or questionable content.

Scanned

This is an earlier scan of treasury.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 treasury.gov

This scan found 19 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. The full timeline opens with your unlock code.

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
85
Security headers
55
Email security
70
DNS health
80
Network security
100
GDPR outside view
58
Average
75

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 U.S. Department of the Treasury holds a critical position in the U.S. government as the primary agency overseeing fiscal policy, tax collection, currency issuance, and financial regulation. Its business model is non-commercial, focused on public service and regulatory enforcement. The website supports this mission by providing extensive data, policy documentation, and service portals for various stakeholders. The Treasury's ecosystem includes multiple bureaus and inspector general offices, each with dedicated web presences linked from the main site. The agency's market position is authoritative and central to U.S. economic governance. The website's content and structure support transparency, public engagement, and operational efficiency, reflecting a high level of digital maturity and strategic communication.

Security posture

The Treasury website exhibits a strong security posture with enforced HTTPS, use of official .gov domain, and no visible exposure of sensitive information. The site uses modern web technologies and reputable analytics services, minimizing risk from vulnerable third-party libraries. However, explicit security headers such as Content-Security-Policy and X-Frame-Options are not clearly identified in the HTML content, which could enhance protection against common web attacks. The absence of a published vulnerability disclosure policy or security.txt file limits transparency for security researchers. Incident response contact information is not readily found, which could hinder timely reporting of security issues. Overall, the site aligns well with government security standards but could improve in formalizing vulnerability management and incident response communications.

Recommendations

  1. Implement and clearly document security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  2. Add a cookie consent banner or mechanism to comply with GDPR and other privacy regulations.
  3. Publish a vulnerability disclosure policy or security.txt file to facilitate responsible reporting of security issues.
  4. Provide explicit incident response contact information on the website for security concerns.
  5. Regularly audit and update third-party scripts and analytics tools to mitigate potential vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
U.S. Department of the Treasury
Description
The U.S. Department of the Treasury is the executive agency responsible for promoting economic prosperity and ensuring the financial security of the United States. It manages federal finances, collects taxes, produces currency, manages government accounts and the public debt, and enforces finance and tax laws.
Key services
Financial sanctions enforcement, Interest rate statistics publication, Savings bonds and securities management, Grant programs administration, Treasury payments and auctions, Tax policy and IRS services, Data and economic policy dissemination
Content quality
excellent
Branding
consistent

Technology

Stack
Drupal 10, Google Analytics, Google Tag Manager, FontAwesome, Slick Carousel, USWDS (U.S. Web Design System)
Frameworks
Drupal CMS, USWDS
Platforms
Web
Performance
fast
Mobile
excellent
Accessibility
excellent
SEO
good

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of official .gov domain
  • No vulnerable libraries detected
  • Secure forms with no password fields

Analytics and tracking

Services
Google Analytics, Google Tag Manager, Akamai mPulse, DigitalGov Web Vitals
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Akamai mPulse
Transparency
good

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 content covering Treasury functions, policies, data, and services
  3. Modern, accessible, and mobile-optimized design using Drupal 10 and USWDS
  4. Secure HTTPS with no visible security issues
  5. No signs of adult or questionable content
  6. Strong social media presence on official platforms
  7. No WHOIS data available due to .gov domain restrictions
  8. No cookie consent mechanism detected
  9. No explicit security.txt or vulnerability disclosure found
Technical notes

Notes

The website is built on Drupal 10 CMS with integration of the U.S. Web Design System, ensuring compliance with federal accessibility and design standards. It uses modern JavaScript libraries such as FontAwesome for icons and Slick Carousel for interactive elements. Analytics and performance monitoring are handled via Google Analytics, Google Tag Manager, and Akamai mPulse, indicating a mature approach to user behavior tracking and site optimization. The site is mobile-optimized and accessible, with responsive design and skip links for screen readers. Hosting appears to be supported by government infrastructure and Akamai CDN, contributing to fast load times and reliability. The technical implementation is robust with room for improvement in security header deployment and privacy consent mechanisms.
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. 75/100 −2Medium27 findingsView report
  2. 77/100Low21 findingsView report
Reviews of this site

Share your experience with treasury.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 treasury.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.