Skip to main content

Security report for treas.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 federal agency responsible for managing the nation's finances, economic policy, and financial security. It provides a broad range of services and information targeting the general public, businesses, financial institutions, and government entities. The site is well-branded, professionally designed, and offers comprehensive content including policy issues, data centers, services, and news updates. Technically, the website is built on Drupal 10 with integration of modern web technologies such as Google Analytics, Google Tag Manager, and the U.S. Web Design System (USWDS). It is hosted likely behind Akamai's CDN and performance monitoring tools, ensuring fast load times and good mobile responsiveness. Accessibility and SEO best practices are well implemented. From a security perspective, the site enforces HTTPS and uses secure analytics configurations. However, explicit security headers are not clearly visible in the HTML, and there is no publicly available security policy or incident response contact information. The absence of a cookie consent mechanism and vulnerability disclosure page are minor compliance gaps. Overall, the security posture is strong but could be improved with more transparency and user privacy controls. The domain WHOIS data is unavailable, which is typical for U.S. government domains that restrict public WHOIS information for security reasons. The domain is a subdomain of treasury.gov, confirming its legitimacy. No suspicious or malicious indicators were found. The website is safe for general audiences and does not contain any adult or questionable content.

Scanned

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 treas.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. 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
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 as a federal government agency overseeing economic and financial policies. Its business model is service-oriented, providing regulatory oversight, financial data, and public services such as auctions, grants, and fraud reporting. The website targets a diverse audience including citizens, businesses, financial institutions, and government bodies. The Treasury's extensive network of bureaus and inspector general offices are linked, reflecting a broad operational scope. The site’s content and structure support transparency and public engagement, reinforcing its authoritative market position. Partnerships with related government domains and services like IRS.gov and TreasuryDirect.gov enhance its ecosystem.

Security posture

The website demonstrates a mature security posture with mandatory HTTPS, anonymized analytics tracking, and no visible exposure of sensitive data. The use of government-standard web design and hosting behind a reputed CDN adds to its resilience. However, the lack of explicit security headers in the HTML and absence of a published security policy or incident response contacts represent areas for improvement. No vulnerabilities or malware were detected. The site does not provide a vulnerability disclosure program or security.txt file, which could enhance its security culture and transparency. Overall, the site is secure but could benefit from enhanced user privacy controls and clearer security communications.

Recommendations

  1. Publish and enforce comprehensive security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  2. Implement a cookie consent banner to comply with GDPR and enhance user privacy transparency.
  3. Create and publish a dedicated security policy page including incident response contact information.
  4. Establish a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  5. Enhance accessibility documentation and continue monitoring for performance and security improvements.
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 provides policy leadership on financial, economic, tax, and fiscal matters, manages government accounts and the public debt, and oversees national banks and financial institutions.
Key services
Financial sanctions and enforcement, Interest rate statistics and data dissemination, Treasury securities and auctions, Fraud, waste, and abuse reporting, Grant and payment services, Tax policy and IRS services, Shared government services
Content quality
excellent
Branding
consistent

Technology

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

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of secure analytics with IP anonymization
  • No visible vulnerable libraries

Analytics and tracking

Services
Google Analytics, Google Tag Manager, Akamai Boomerang
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Akamai Boomerang
Transparency
basic

Site quality

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

Key observations

  1. Official U.S. Department of the Treasury website with comprehensive content and services
  2. Uses modern web technologies and follows government web standards
  3. Strong branding and consistent design
  4. No signs of phishing, malware, or suspicious activity
  5. WHOIS data is unavailable likely due to government domain privacy policies
  6. No explicit contact emails or phone numbers found on the main page
  7. Privacy and cookie policies are present but cookie consent mechanism is not implemented
  8. No explicit security policy or incident response information publicly visible
  9. Social media presence on Twitter (X), Facebook, and LinkedIn
  10. No vulnerability disclosure or security.txt file detected
Technical notes

Notes

The website is built on Drupal 10 CMS, leveraging the U.S. Web Design System for consistent government branding and accessibility. It integrates Google Analytics and Tag Manager for user behavior tracking with IP anonymization. Hosting appears to be supported by Akamai CDN and performance monitoring tools like Boomerang. The site is mobile-optimized, fast-loading, and SEO-friendly with proper meta tags and structured navigation. No deprecated or vulnerable libraries were detected. The technical infrastructure is modern and robust, supporting a large enterprise government website with extensive content and services.
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/100Medium27 findingsView report
Reviews of this site

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