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 government agency responsible for managing national finances, economic policy, and financial security. It provides comprehensive information and services including financial sanctions, interest rate data, savings bonds, grant programs, and tax policy. The site targets a broad audience including the general public, businesses, financial institutions, and government entities. The website is well-branded, consistent, and authoritative, reflecting its government status. Technically, the site is built on Drupal 10 and leverages modern web technologies such as Google Analytics, Google Tag Manager, FontAwesome, and the U.S. Web Design System (USWDS). It is hosted likely behind Akamai CDN, ensuring fast performance and global availability. The site is mobile-optimized and accessible, with good SEO practices and structured navigation. From a security perspective, the site enforces HTTPS, uses security headers, and avoids exposing sensitive data. However, explicit security policies and incident response contacts are not prominently published, and no visible cookie consent mechanism is present, which could be improved for compliance. The domain is a .gov domain, inherently trustworthy and managed by the U.S. government, with WHOIS data restricted accordingly. Overall, the site demonstrates a strong security posture, excellent content quality, and high business credibility. Minor improvements in privacy compliance and transparency are recommended to enhance user trust and regulatory adherence.

Scanned

This is an earlier scan of treas.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 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 Department of the Treasury holds a dominant position as the U.S. government's financial authority, providing essential services such as managing federal finances, enforcing tax laws, and administering economic sanctions. Its business model is non-commercial, focused on public service and regulatory functions. The website reflects this with extensive links to bureaus and inspector general offices, indicating a broad operational scope. The presence of multiple bureaus and inspector general sites as partners highlights a complex organizational ecosystem. The site supports transparency and public engagement through data centers, news, and service portals. Strategic partnerships with other government entities and data platforms reinforce its authoritative role in finance and governance.

Security posture

The website exhibits a mature security posture with enforced HTTPS, use of security headers, and no visible vulnerabilities or outdated libraries. The absence of exposed sensitive data and the use of official .gov domain enhance trust. However, the lack of explicit security policy documentation and incident response contact information is a gap. No vulnerability disclosure or security.txt file was found, which could limit external reporting of security issues. Cookie consent mechanisms are not visible, potentially impacting privacy compliance. Overall, the site aligns well with government security standards but could improve transparency and user privacy controls.

Recommendations

  1. Publish a dedicated security policy page including incident response contacts to improve transparency.
  2. Implement a visible cookie consent banner to comply with privacy regulations and enhance user trust.
  3. Add a vulnerability disclosure policy or security.txt file to facilitate responsible reporting of security issues.
  4. Provide clear contact information for the Data Protection Officer or privacy team to support GDPR and related compliance.
  5. Regularly review and audit third-party scripts and tracking tools to ensure ongoing privacy compliance and minimize user tracking.
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 national treasury of the federal government of the United States, responsible for promoting economic prosperity and ensuring the financial security of the United States. It provides policy leadership, manages federal finances, enforces finance and tax laws, and administers economic sanctions.
Key services
Financial sanctions and enforcement, Interest rate statistics and data, Savings bonds and securities management, Grant programs and financial assistance, Treasury payments and auctions, Tax policy and IRS related services, Government shared services
Content quality
excellent
Branding
consistent

Technology

Stack
Drupal 10, Google Analytics, Google Tag Manager, FontAwesome, USWDS (U.S. Web Design System), Akamai (implied by akamaihd.net references), Boomerang (performance monitoring)
Frameworks
Drupal CMS, USWDS
Platforms
Web (Desktop and Mobile)
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 or outdated libraries detected
  • Secure forms with no password or sensitive input fields visible

Analytics and tracking

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

Advertising

Tracking pixels
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 financial and policy information.
  2. Uses secure HTTPS protocol with modern web technologies and accessibility standards.
  3. No signs of malicious or suspicious content.
  4. Extensive use of official government branding and links to related bureaus and inspector general offices.
  5. No visible contact emails or phone numbers on the homepage; contact likely managed via dedicated pages.
  6. No explicit cookie consent banner detected despite cookie policy presence.
  7. WHOIS data is not publicly available, consistent with .gov domain privacy and security policies.
Technical notes

Notes

The website is built on a modern Drupal 10 CMS platform, utilizing the U.S. Web Design System for consistent government branding and accessibility. It integrates Google Analytics and Tag Manager for analytics and performance monitoring, along with Boomerang for real user monitoring. Hosting appears to leverage Akamai CDN for performance and security. The site is mobile-optimized, accessible, and SEO-friendly with proper meta tags and structured navigation. No technical debt or outdated technologies were detected. Performance is fast, and the site uses modern JavaScript libraries and fonts. Opportunities exist to enhance privacy compliance mechanisms and security transparency.
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.