Skip to main content

Security report for fincen.gov

Financial Crimes Enforcement Network · Government · United States

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

Security score

73/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 activities such as money laundering and terrorist financing. It provides critical financial intelligence, regulatory guidance, and enforcement actions to financial institutions, law enforcement, and government agencies. The website serves as a comprehensive resource hub for these stakeholders, offering access to advisories, reporting requirements, and enforcement updates. The site’s market position is that of a key federal government entity with authoritative oversight in financial crime prevention. Technically, the website is built on Drupal 10, leveraging modern web technologies including Google Tag Manager, Akamai mPulse for performance monitoring, and Font Awesome for iconography. The site is well-optimized for mobile and accessibility standards, with fast loading times and clear navigation. Security best practices are observed with HTTPS enforcement and no visible vulnerabilities or exposed sensitive data. Analytics usage is moderate and privacy policies are comprehensive, though a cookie consent mechanism is not explicitly present. From a security perspective, the site demonstrates a strong posture with secure configurations and adherence to government standards. The WHOIS data is limited due to privacy protections typical for government domains, but the domain’s .gov TLD and consistent branding strongly support legitimacy. No critical vulnerabilities or suspicious patterns were detected. Overall, the site is trustworthy, professional, and well-maintained. The overall risk assessment is low, with recommendations to enhance transparency by publishing explicit security headers and implementing a visible cookie consent banner to improve privacy compliance. Strategic improvements in incident response disclosures and security policy visibility would further strengthen trust and compliance.

Scanned

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

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 20 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
50
Email security
70
DNS health
65
Network security
100
GDPR outside view
58
Average
73

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 holds a critical role in the U.S. government’s financial crime enforcement ecosystem, providing regulatory oversight and intelligence services that support law enforcement and financial institutions. Its business model is government-funded and focused on compliance enforcement and intelligence dissemination rather than commercial revenue. The target customers include banks, financial institutions, law enforcement agencies, and policymakers. The agency maintains strong partnerships with other government entities such as the IRS, Treasury, and regulatory bodies, as evidenced by linked domains and cross-references. Growth indicators include ongoing updates to reporting requirements and enforcement actions. The website’s professional presentation and comprehensive resources reflect a mature and authoritative market presence.

Security posture

The website exhibits a mature security posture with HTTPS enforced and no visible security misconfigurations or vulnerabilities. Use of modern analytics and performance monitoring tools is balanced with privacy considerations. However, the absence of a visible cookie consent mechanism and explicit security policy disclosures represent minor compliance gaps. Incident response contact information is not publicly detailed, which could be improved for transparency. Overall, the site aligns well with government security standards and demonstrates readiness to protect user data and maintain operational integrity.

Recommendations

  1. Implement a visible cookie consent banner to comply with privacy regulations and enhance user trust.
  2. Publish detailed security headers such as Content-Security-Policy, X-Content-Type-Options, and Referrer-Policy explicitly.
  3. Provide clear incident response and security policy documentation accessible from the website.
  4. Enhance transparency by listing data retention policies related to analytics and user data.
  5. Maintain regular security audits and update WHOIS information where possible to improve domain transparency.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Financial Crimes Enforcement Network
Description
The Financial Crimes Enforcement Network (FinCEN) is a bureau of the U.S. Department of the Treasury that safeguards the financial system from illicit activity, counters money laundering and terrorist financing, and promotes national security through financial intelligence collection, analysis, and dissemination.
Key services
Financial intelligence collection and analysis, Suspicious Activity Reporting (SAR) guidance, Beneficial Ownership Information reporting, Advisories and enforcement actions, Support to law enforcement and financial institutions
Content quality
excellent
Branding
consistent

Technology

Stack
Drupal 10, Google Tag Manager, Font Awesome 6, Universal-Federated-Analytics, Akamai mPulse
Frameworks
Drupal CMS
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 secure analytics scripts
  • No visible vulnerable libraries

Analytics and tracking

Services
Google Analytics, Akamai mPulse, Universal-Federated-Analytics
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Akamai mPulse, Universal-Federated-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 content related to financial crime enforcement
  3. No signs of phishing or malware
  4. No exposed sensitive data or vulnerabilities detected
  5. Good use of modern web technologies and analytics
  6. Privacy and vulnerability disclosure policies present
  7. No cookie consent banner detected
  8. Contact available via official assistance portal
  9. WHOIS data is privacy protected or restricted as typical for government domains
Technical notes

Notes

The website is built on a modern Drupal 10 CMS platform with integration of Google Tag Manager and Akamai mPulse for analytics and performance monitoring. The use of Font Awesome icons and responsive design ensures a consistent user experience across devices. Hosting appears to be managed through government infrastructure with CDN support for performance. The site loads quickly and includes accessibility features such as skip links and ARIA labels. Technical debt appears minimal with no deprecated libraries or scripts detected. Opportunities exist to further modernize by adopting explicit security headers and enhancing privacy compliance mechanisms.
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/100Medium26 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.