Skip to main content

Security report for fincen.gov

United States Department of the Treasury Financial Crimes Enforcement Network · Finance · United States

Medium risk. 4 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

75/100

Risk levelMedium

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

The Financial Crimes Enforcement Network (FinCEN) operates as a bureau within the United States Department of the Treasury, focusing on safeguarding the financial system from illicit use, combating money laundering, and promoting national security through financial intelligence. The website serves as an authoritative portal providing regulatory information, filing systems, advisories, and resources for financial institutions, law enforcement, and the public. It holds a strong market position as a key U.S. government agency in financial crime enforcement. Technically, the site is built on Drupal 10 with integration of modern web technologies including Bootstrap, jQuery, and Google Analytics. The infrastructure supports good mobile optimization, accessibility, and SEO practices, reflecting a mature digital presence. The site uses HTTPS exclusively, ensuring secure communications, and integrates official government branding and trusted external resources. From a security perspective, the site demonstrates a solid posture with HTTPS, no visible vulnerabilities, and adherence to best practices. However, explicit security headers are not detected in the provided data, and there is no visible cookie consent mechanism, which could be improved for enhanced compliance. The WHOIS data is not publicly available, typical for .gov domains, but the domain's legitimacy is strongly supported by the official branding and content. Overall, the website is highly professional, trustworthy, and serves its government regulatory function effectively. Strategic recommendations include adding explicit security headers, implementing a cookie consent banner, publishing incident response contacts, and enhancing transparency on security frameworks to further strengthen trust and compliance.

Scanned

This is an earlier scan of fincen.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

4 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

  3. DNS health

    DNS sends visitors and email to the right servers. Misconfigured records can cause outages or let someone redirect your traffic.

    • High

      Unregistered MX Record

      MX record points to unregistered domain: ms25064148.msv1.invalid

      What to do: Remove or fix MX record pointing to unregistered domain

      • RFC 5321 §5.1
      • NIS2 21(2)(i)
      • IR 2024/2690 12.4: Implementing Regulation (EU) 2024/2690, Annex point 12.4: Asset inventory
      • NIST CM-8: NIST SP 800-53 Rev. 5 CM-8: System Component Inventory

Need hands-on remediation? Email guard@offseq.com

Keep watching fincen.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. 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
100
Security headers
60
Email security
70
DNS health
65
Network security
100
GDPR outside view
53
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

FinCEN is positioned as an essential government entity within the finance sector, providing regulatory oversight and enforcement related to anti-money laundering and financial crimes. Its business model revolves around regulatory compliance, intelligence sharing, and enforcement support. The target audience includes financial institutions, law enforcement agencies, and regulated entities. The agency benefits from strong government backing and a clear mandate, which supports its authoritative market position. The website reflects a well-maintained digital ecosystem with partnerships linked to other government domains, enhancing its operational ecosystem. Growth indicators include recent news on regulatory updates and expanded reporting requirements. The absence of commercial advertising or affiliate programs aligns with its government mission.

Security posture

The website exhibits a mature security posture with enforced HTTPS and no detected vulnerabilities or exposed sensitive data. The lack of explicit security headers such as Content-Security-Policy or X-Frame-Options suggests room for improvement. No incident response or abuse contact information is visible, which is a gap in transparency. The site complies with privacy regulations, including GDPR, as indicated by the presence of a privacy policy. Tracking technologies are limited to government-standard analytics tools, minimizing privacy risks. Overall, the security culture appears strong but could benefit from enhanced header policies and clearer incident response channels.

Recommendations

  1. Implement comprehensive security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  2. Add a visible cookie consent banner to comply with privacy regulations and enhance user transparency.
  3. Publish clear incident response and abuse contact information to improve security communication.
  4. Enhance documentation and public disclosure of security frameworks and certifications to build trust.
  5. Regularly audit third-party scripts and tracking tools to minimize privacy risks and ensure compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
United States Department of the Treasury Financial Crimes Enforcement Network
Description
FinCEN is a bureau of the U.S. Department of the Treasury focused on safeguarding the financial system from illicit use, combating money laundering, and promoting national security through the collection, analysis, and dissemination of financial intelligence.
Key services
Beneficial Ownership Information Reporting, Bank Secrecy Act Filing Information, Financial Trend Analyses, Suspicious Activity Report (SAR) Statistics, FinCEN Exchange for information sharing, Alerts and Advisories on financial crimes
Content quality
excellent
Branding
consistent

Technology

Stack
Drupal 10, jQuery, Bootstrap, Google Analytics, Google Tag Manager, USA.gov search integration
Frameworks
Drupal CMS, Bootstrap CSS/JS
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Secure cookie usage implied
  • No exposed sensitive data in HTML
  • Use of official .gov domain

Analytics and tracking

Services
Google Analytics, Google Tag Manager, DigitalGov Web Vitals
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
DigitalGov Web Vitals
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 content on financial crime enforcement and regulatory information
  3. Use of modern CMS (Drupal 10) and standard government web technologies
  4. No signs of malicious or suspicious content
  5. Strong branding and trust indicators
  6. No visible contact emails or phone numbers on homepage content
  7. Privacy policy and vulnerability disclosure policies are present
  8. No cookie consent banner detected
  9. No WHOIS registrar or registrant info publicly available, typical for .gov
Technical notes

Notes

The website is built on a modern Drupal 10 CMS platform, leveraging Bootstrap for responsive design and jQuery for interactivity. It integrates Google Analytics and Google Tag Manager for analytics and tracking. The site demonstrates good mobile optimization and accessibility features, with a clear navigation structure and professional design. Performance is moderate, likely due to the complexity of content and government-standard compliance requirements. There is no indication of outdated or vulnerable libraries. Hosting details are not explicit but the site uses a .gov domain, implying government-managed infrastructure. Opportunities exist to improve security headers and cookie consent mechanisms to align with best practices.
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. 73/100Medium27 findingsView report
Reviews of this site

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