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

78/100

Risk levelLow

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

TreasuryDirect.gov is the official U.S. government website operated by the U.S. Department of the Treasury, providing a secure platform for the electronic purchase, redemption, and management of U.S. Savings Bonds and Treasury Marketable Securities. It serves a broad audience including the general public, financial professionals, and government entities. The site holds a strong market position as the sole official channel for these services, offering comprehensive information and tools related to U.S. Treasury securities. Technically, the website employs a modern and robust technology stack including jQuery, Bootstrap, Google reCAPTCHA, and Google Tag Manager, ensuring good performance, mobile optimization, and accessibility. The site is hosted on government infrastructure with a secure HTTPS configuration and uses standard analytics and feedback tools. However, DNSSEC is not enabled, and some security headers are not explicitly detected. From a security perspective, the site demonstrates strong practices such as HTTPS enforcement, bot protection, and secure login mechanisms. No vulnerabilities or exposed sensitive data were found. Privacy compliance is adequate with a comprehensive privacy policy and terms of service, though a cookie consent mechanism is absent. Incident response and security policy details are not publicly disclosed, which could be improved. Overall, TreasuryDirect.gov is a highly trustworthy and professional government website with excellent content quality and user experience. The risk level is low, but enhancements in DNS security, cookie consent, and transparency around security policies would further strengthen its posture.

Scanned

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

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 17 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
70
Email security
70
DNS health
80
Network security
100
GDPR outside view
53
Average
78

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 an essential government service under the U.S. Department of the Treasury, providing direct-to-consumer and institutional access to U.S. Treasury securities. Its competitive advantage lies in its exclusive status as the official platform for electronic savings bonds and marketable securities. Revenue streams are government-funded, with no commercial advertising or affiliate programs detected. The target customers include individual investors, financial professionals, and government bodies. The site integrates with a network of related government domains, enhancing its ecosystem and data transparency. Growth indicators include regular updates on rates, auctions, and disaster relief announcements. Strategic partnerships with other government data and spending transparency sites reinforce its authoritative position.

Security posture

The website exhibits a mature security posture with enforced HTTPS, use of reCAPTCHA to mitigate automated abuse, and secure login workflows. No critical vulnerabilities or exposed sensitive information were detected in the HTML content. However, the absence of DNSSEC and some common security headers suggests room for improvement. The lack of publicly available incident response contacts or security policies may limit transparency and user trust in security matters. Privacy compliance is generally good, but the missing cookie consent mechanism is a minor gap. Overall, the site aligns well with government security standards but could enhance user trust by publishing more explicit security and incident response information.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Implement and display a cookie consent banner to comply with privacy best practices and regulations.
  3. Publish a dedicated security policy and incident response contact information to increase transparency and user trust.
  4. Add standard security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options to harden the site against common attacks.
  5. Regularly review and update third-party scripts and analytics tools to ensure no vulnerabilities are introduced.
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, Account management for TreasuryDirect users, Information and educational resources about Treasury securities
Content quality
excellent
Branding
consistent

Technology

Stack
jQuery, Bootstrap, Google reCAPTCHA, Google Tag Manager, Google Translate, Verint FSR (feedback system), DAP Digital Analytics Program
Frameworks
Bootstrap
Performance
fast
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Use of Google reCAPTCHA for bot protection
  • No exposed sensitive data in HTML
  • Secure login form
  • Use of serverTransferProhibited domain status

Analytics and tracking

Services
DAP Digitalgov Analytics, Google Tag Manager
Tracking level
minimal
Privacy practices
basic

Advertising

Tracking pixels
DAP Digitalgov Analytics
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 and well-structured content about Treasury securities
  3. Secure HTTPS connection with modern security practices
  4. No signs of malicious or suspicious activity
  5. Good integration of analytics and user feedback tools
  6. No cookie consent mechanism detected, which may be improved
  7. No explicit security policy or incident response contact information published
Technical notes

Notes

The website uses a modern front-end technology stack with jQuery and Bootstrap for responsive design and UI components. Google reCAPTCHA is integrated for bot protection, and Google Tag Manager is used for analytics management. The site is mobile optimized and accessible, with good SEO practices including meta tags and structured navigation. Hosting appears to be on government infrastructure, ensuring compliance with federal hosting standards. Performance is fast with no broken elements detected. The site lacks DNSSEC and some security headers, which are recommended for enhanced security. Overall, the technical implementation is solid with minor areas for improvement.
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. 80/100Low24 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.