Skip to main content

Security report for occ.gov

Office of the Comptroller of the Currency · Government · United States

Low risk. 2 critical or high findings in GDPR outside view.

Security score

81/100

Risk levelLow

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

The Office of the Comptroller of the Currency (OCC) is a U.S. federal government agency responsible for ensuring a safe, sound, and fair federal banking system. The website serves as the official digital presence of the OCC, providing regulatory information, news, publications, and tools for bankers, consumers, and other stakeholders. It holds a strong market position as a key regulator within the U.S. banking sector, operating under the Department of the Treasury. The site targets a broad audience including banking professionals, federal institutions, and the general public seeking regulatory guidance and banking information. Technically, the website is built on the Percussion Content Management System and leverages modern web technologies including jQuery, Google Analytics, Crazy Egg, and the U.S. Web Design System (USWDS) to ensure accessibility, responsiveness, and usability. The site demonstrates good performance and SEO practices, with comprehensive metadata and structured navigation. Mobile optimization and accessibility features are well implemented, reflecting a mature digital infrastructure. From a security perspective, the site enforces HTTPS and employs domain transfer protections, indicating a secure baseline. However, DNSSEC is not enabled, representing a minor security gap. The presence of a vulnerability disclosure policy is a positive indicator of security awareness, though explicit incident response contacts and security headers are not evident. Privacy compliance is moderate, with a comprehensive privacy policy but lacking a cookie consent mechanism despite the use of tracking scripts. Overall, the OCC website is a professional, trustworthy, and authoritative government resource with strong content quality and business credibility. Minor improvements in security headers, DNSSEC implementation, and privacy consent mechanisms would enhance its security posture and compliance. The site is safe for general audiences and aligns well with its role as a federal regulatory agency.

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

2 findings rated critical or high. Fix these first.

  1. 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 occ.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. 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
95
Security headers
85
Email security
70
DNS health
85
Network security
100
GDPR outside view
53
Average
81

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention occ.gov, from OffSeq Breach.

Total records
19
Employees
0
Customers
19
Third parties
0
Weak passwords
5%

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for occ.gov.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

The OCC operates as a critical federal regulatory body overseeing national banks and federal savings associations. Its business model is regulatory and supervisory, funded by the federal government. The website reflects this with extensive resources for compliance, licensing, and consumer protection. The OCC maintains a strong partnership ecosystem with related government sites such as BankNet.gov and HelpWithMyBank.gov, enhancing its service offerings. The agency's market position is stable and authoritative, with a large organizational size and a history dating back to 2004 for this domain. The site supports growth and transparency through frequent news updates, publications, and public engagement tools. Strategic observations include a focus on community reinvestment, cybersecurity, and financial literacy, indicating responsiveness to evolving banking challenges.

Security posture

The OCC website demonstrates a mature security posture with mandatory HTTPS, domain transfer prohibitions, and a published vulnerability disclosure policy. The absence of DNSSEC is a notable but not critical weakness. No exposed sensitive data or vulnerable libraries were detected in the HTML content. The site lacks explicit security headers such as Content-Security-Policy and X-Frame-Options, which could mitigate certain attack vectors. Incident response contact information is not publicly visible, which could hinder rapid reporting of security issues. Privacy compliance is partial, with no cookie consent mechanism despite usage of tracking and analytics scripts. Overall, the security maturity is good but could be improved with enhanced header policies, DNSSEC, and clearer incident response channels.

Recommendations

  1. Enable DNSSEC on the domain to strengthen DNS security and prevent spoofing.
  2. Implement and publish comprehensive security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Add a cookie consent banner or mechanism to comply with privacy regulations and inform users about tracking.
  4. Publish explicit incident response contact information such as security@ or abuse@ email addresses.
  5. Consider adding a terms of service page to clarify user rights and responsibilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Office of the Comptroller of the Currency
Description
Ensuring a safe and sound federal banking system for all Americans
Key services
Bank supervision and examination, Chartering and licensing, Consumer protection, Publication of regulatory guidance and reports, Community Reinvestment Act enforcement
Content quality
excellent
Branding
consistent

Technology

Stack
jQuery, Google Custom Search Engine, Google Analytics, Crazy Egg, US Web Design System (USWDS)
Frameworks
Percussion CM System
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Domain status serverTransferProhibited
  • No exposed sensitive data in HTML
  • Use of vulnerability disclosure policy

Analytics and tracking

Services
Google Analytics, DigitalGov Universal Analytics, Crazy Egg
Tracking level
moderate
Privacy practices
basic

Advertising

Ad networks
Google Adsense
Tracking pixels
Crazy Egg, DigitalGov Universal Analytics
Marketing tools
Google Custom Search Engine
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 for the Office of the Comptroller of the Currency
  2. Comprehensive navigation and content structure
  3. Strong branding and trust signals
  4. Use of government-standard web design system (USWDS)
  5. No visible contact emails or phone numbers on homepage, contact via forms
  6. No cookie consent banner detected despite use of tracking scripts
  7. No explicit terms of service page found
  8. Social media presence on Facebook, Twitter, LinkedIn, YouTube
  9. Multiple recent news releases and bulletins indicating active maintenance
Technical notes

Notes

The website is built on a government-standard CMS (Percussion CM System) and uses the US Web Design System for consistent styling and accessibility. It integrates multiple third-party analytics and tracking tools including Google Analytics and Crazy Egg, which provide user behavior insights but require privacy considerations. The site is mobile optimized and accessible, with preloaded fonts and responsive images. Performance is moderate, with asynchronous loading of scripts to improve page speed. The domain is registered with serverTransferProhibited status, indicating control over domain transfers. However, DNSSEC is not enabled, which is a technical risk. The site uses multiple external domains for analytics and social media integration, all reputable and expected for a government site. Overall, the technical infrastructure is solid with room for security enhancements.
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

Reviews of this site

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