Skip to main content

Security report for treasurydirect.gov

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

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

Security score

80/100

Risk levelLow

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

TreasuryDirect.gov is the official U.S. Department of the Treasury website providing electronic services for purchasing, managing, and redeeming U.S. Savings Bonds and other Treasury securities. It serves a broad audience including the general public, financial professionals, and government entities. The platform is the sole official channel for these financial instruments, positioning it as a critical government financial service with a strong market presence. The website offers comprehensive information, tools, and auction data to support users in managing their investments securely and efficiently. Technically, the site employs a modern technology stack including jQuery, Bootstrap, Google reCAPTCHA, and Google Tag Manager, ensuring a responsive and accessible user experience. The site is well-optimized for mobile devices and includes accessibility features. Hosting appears to be managed by or for the U.S. government, ensuring reliability and compliance with government standards. From a security perspective, TreasuryDirect.gov demonstrates a strong posture with enforced HTTPS, use of security headers, and bot protection mechanisms. No vulnerabilities or exposed sensitive data were detected. However, there is room for improvement in publishing explicit security policies, vulnerability disclosure programs, and cookie consent mechanisms to enhance compliance and transparency. Overall, TreasuryDirect.gov is a highly trustworthy, professional, and secure government website that effectively serves its mission. Strategic enhancements in privacy compliance and security transparency would further strengthen its position and user trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 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 treasurydirect.gov

This scan found 15 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
100
Security headers
70
Email security
70
DNS health
85
Network security
100
GDPR outside view
53
Average
80

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

TreasuryDirect operates as a government essential entity within the finance sector, providing direct access to U.S. Treasury securities. Its competitive advantage lies in its exclusive status as the official platform for U.S. Savings Bonds and marketable securities auctions. Revenue streams are government-funded, with no commercial advertising or affiliate programs. The target customers include individual investors, financial professionals, and government agencies. The site’s partnership ecosystem includes related Treasury and fiscal service domains, enhancing service integration. The platform’s longevity since 1998 and consistent branding reinforce its authoritative market presence.

Security posture

The website exhibits a mature security posture with mandatory HTTPS, serverTransferProhibited domain status, and integration of Google reCAPTCHA to mitigate automated threats. Security headers and best practices are partially implemented, though explicit security policies and incident response contacts are absent. No vulnerabilities or insecure libraries were identified. The absence of a vulnerability disclosure program and security.txt file represents a compliance gap. Incident response readiness and data protection officer contacts are not publicly disclosed, which could be improved to align with best practices and regulatory expectations.

Recommendations

  1. Enable DNSSEC to enhance DNS security and prevent spoofing.
  2. Implement a cookie consent banner to comply with privacy regulations and improve user transparency.
  3. Publish a dedicated security policy and incident response information to increase trust and preparedness.
  4. Establish and publicize a vulnerability disclosure program and security.txt file to encourage responsible reporting.
  5. Provide Data Protection Officer contact details to align with data protection best practices and regulatory requirements.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
U.S. Department of the Treasury
Description
TreasuryDirect.gov is the official U.S. government website to electronically buy and redeem U.S. Savings Bonds and other U.S.-backed investments for the general public, financial professionals, and state and local governments.
Key services
Electronic purchase and redemption of U.S. Savings Bonds, Electronic sales and auctions of Treasury Marketable Securities, Information and management tools for bonds and securities, Auction results and schedules, Government user services
Content quality
excellent
Branding
consistent

Technology

Stack
jQuery, Bootstrap, Google reCAPTCHA, Google Tag Manager, Google Translate, Verint (FSR) feedback system
Frameworks
Bootstrap
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • Use of Google reCAPTCHA for bot protection
  • No exposed sensitive data in HTML
  • Secure login mechanisms
  • No vulnerable libraries detected

Analytics and tracking

Services
DAP Universal Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
DAP Universal Analytics
Marketing tools
Verint Feedback System
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 TLD
  2. Comprehensive financial services for U.S. Treasury securities
  3. Modern and accessible website design
  4. Strong security posture with HTTPS and reCAPTCHA
  5. No signs of malicious or suspicious activity
  6. Limited explicit privacy and security policy disclosures
  7. No cookie consent mechanism detected
  8. No vulnerability disclosure or security.txt found
Technical notes

Notes

The website uses a stable and modern technology stack including jQuery and Bootstrap for UI components, Google reCAPTCHA for bot protection, and Google Tag Manager for analytics. The site is mobile-optimized and accessible, with good SEO practices evident in meta tags and structured navigation. Hosting is likely government-managed, ensuring compliance and reliability. Performance is moderate, with asynchronous loading of scripts and external resources. There is no evidence of a commercial CMS, indicating a custom-built platform tailored for government use. Opportunities exist to modernize further by adopting newer JavaScript frameworks and enhancing performance metrics.
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. 78/100Low26 findingsView report
Reviews of this site

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