Skip to main content

Security report for fdic.gov

Federal Deposit Insurance Corporation · Finance · United States

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

Security score

72/100

Risk levelMedium

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

The Federal Deposit Insurance Corporation (FDIC) is a U.S. government independent agency focused on maintaining stability and public confidence in the nation's financial system. The website serves multiple audiences including consumers, bankers, and analysts by providing deposit insurance information, regulatory guidance, financial research, and news updates. The FDIC operates as a trusted authority in the banking sector with a long-established domain and official .gov branding. Technically, the website is built on Drupal 10 CMS, leveraging modern analytics and performance monitoring tools such as Google Tag Manager and Boomerang. It is hosted via Akamai CDN infrastructure, ensuring fast and reliable delivery. The site is well-optimized for mobile and accessibility standards, with clear navigation and professional design. From a security perspective, the site enforces HTTPS and shows no signs of exposed sensitive data or vulnerabilities. However, it lacks explicit security headers, vulnerability disclosure mechanisms, and publicly available privacy or cookie policies, which are areas for improvement. The domain WHOIS data is privacy protected but consistent with government domain practices, supporting legitimacy. Overall, the FDIC website presents a strong security posture and high business credibility but should enhance privacy compliance and transparency to align with best practices and regulatory expectations.

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. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching fdic.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
75
Security headers
50
Email security
70
DNS health
80
Network security
100
GDPR outside view
58
Average
72

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

The FDIC holds a critical role in the U.S. financial regulatory ecosystem, providing deposit insurance and supervising financial institutions. Its business model is government-funded and focused on financial system stability rather than profit. The website reflects this by offering extensive resources for different stakeholders, including educational tools, regulatory information, and detailed banking industry data. The FDIC's market position as a federal agency is unique and authoritative, with no direct commercial competitors. The site’s content and structure support its mission to inform and protect consumers and financial institutions. Partnerships with other government entities and use of federal analytics platforms indicate a mature operational ecosystem.

Security posture

The FDIC website demonstrates a mature security posture with mandatory HTTPS, no visible sensitive data leaks, and use of secure forms. The absence of DNSSEC is a minor gap in DNS security. Lack of explicit security headers and vulnerability disclosure policies reduces transparency and could be improved. No signs of malware or phishing were detected. The site uses reputable third-party analytics and performance tools, which appear properly integrated. Incident response contact information is not publicly visible, which is a potential compliance gap. Overall, the site is secure but could benefit from enhanced security policy disclosures and technical header implementations.

Recommendations

  1. Enable DNSSEC on the fdic.gov domain to strengthen DNS security.
  2. Publish comprehensive privacy and cookie policies with clear consent mechanisms to improve privacy compliance.
  3. Implement and publicly disclose a vulnerability disclosure policy and security.txt file to enhance transparency and security culture.
  4. Add standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to improve defense-in-depth.
  5. Provide clear incident response contact channels on the website for security reporting and abuse handling.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Federal Deposit Insurance Corporation
Description
The Federal Deposit Insurance Corporation (FDIC) is an independent agency created by the Congress to maintain stability and public confidence in the nation’s financial system. The FDIC insures deposits; examines and supervises financial institutions for safety, soundness, and consumer protection; makes large and complex financial institutions resolvable; and manages receiverships.
Key services
Deposit insurance, Bank supervision and examinations, Financial institution resolution, Consumer education and resources, Banking industry research and analysis
Content quality
excellent
Branding
consistent

Technology

Stack
Drupal 10, Google Tag Manager, Plotly.js, Boomerang (performance monitoring), Universal-Federated-Analytics
Frameworks
Drupal CMS
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Use of .gov domain indicating government authenticity
  • No exposed sensitive data in HTML
  • Secure forms with proper labels and ARIA attributes

Analytics and tracking

Services
Google Analytics (via GTM), Universal-Federated-Analytics
Tracking level
moderate
Privacy practices
poor

Advertising

Tracking pixels
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 for consumers, bankers, and analysts
  3. Modern, accessible, and mobile-optimized design
  4. Use of Drupal 10 CMS and advanced analytics tools
  5. No explicit privacy or cookie policies found on homepage
  6. No visible security.txt or vulnerability disclosure
  7. No contact emails or phone numbers explicitly found in provided content
  8. Strong trust indicators from branding and domain
  9. No adult or questionable content detected
Technical notes

Notes

The FDIC website is built on Drupal 10, a modern and secure CMS platform, indicating a current technology stack. It uses Akamai CDN for hosting and content delivery, ensuring fast performance and global reach. The site integrates Google Tag Manager and Universal-Federated-Analytics for data collection and user behavior analysis. Plotly.js is used for interactive data visualizations, enhancing user engagement. The site is mobile-optimized and accessible, with proper ARIA labels and responsive design. Performance monitoring is implemented via Boomerang scripts. No deprecated or vulnerable libraries were detected in the provided content. Overall, the technical infrastructure is robust, modern, and well-maintained.
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. 69/100Medium26 findingsView report
Reviews of this site

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