Skip to main content

Security report for minneapolisfed.org

Federal Reserve Bank of Minneapolis · Finance · 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

The Federal Reserve Bank of Minneapolis website serves as an authoritative platform for economic research, policy dissemination, and banking community engagement within its regional jurisdiction. The site targets policymakers, researchers, banking professionals, and the general public with comprehensive content on monetary policy, banking supervision, and community development. Technically, the site employs modern frameworks such as Bootstrap and jQuery, integrates Google Analytics and Tag Manager for analytics, and uses reCAPTCHA for form security. The security posture is solid with HTTPS enforced and standard security practices, though it lacks explicit security headers and a published security.txt file. Privacy compliance is basic, with no explicit privacy or cookie policies detected in the provided content. The WHOIS data is unavailable due to a malformed query response, which limits domain registration trust analysis but does not detract from the site's evident legitimacy based on content and branding. Overall, the website is professional, trustworthy, and well-optimized for its audience.

Scanned

NIS2 and GDPR posture

GDPR outside view
65/ 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 minneapolisfed.org

This scan found 18 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
85
Security headers
45
Email security
85
DNS health
85
Network security
100
GDPR outside view
65
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

The Minneapolis Fed operates as a key regional entity within the Federal Reserve System, providing monetary policy guidance, banking supervision, and community economic development services. Its business model is governmental and non-commercial, focusing on public service and economic stability. The website reflects a strong market position as a trusted source of economic data and policy analysis. The presence of specialized institutes and research groups indicates a commitment to thought leadership and regional economic insight. The site’s integration with social media and outreach programs suggests active engagement with diverse stakeholders. The lack of explicit contact information on the main page may be intentional for security and operational reasons.

Security posture

The website demonstrates a mature security posture with HTTPS enforced and use of reCAPTCHA to protect forms from automated abuse. However, the absence of visible security headers such as Content-Security-Policy and X-Frame-Options is a gap that could be addressed to enhance protection against common web attacks. No vulnerabilities or exposed sensitive data were detected in the analyzed content. The lack of a published security.txt or incident response contact information limits transparency for vulnerability reporting. Privacy compliance is minimal, with no clear cookie consent mechanism or detailed privacy policy found, which could be improved to meet GDPR and other regulatory standards.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie consent mechanism to improve privacy compliance.
  2. Add security headers like Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options to strengthen security posture.
  3. Publish a security.txt file to facilitate responsible vulnerability disclosure and incident response.
  4. Provide explicit contact information for security incidents and data protection officer to enhance transparency.
  5. Regularly audit WHOIS data and domain registration details to ensure consistency and trustworthiness.

Contact details published on the site

Registration number
Chamber of Commerce
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Federal Reserve Bank of Minneapolis
Description
The Federal Reserve Bank of Minneapolis is pursuing an economy that works for all of us. Serving Montana, North and South Dakota, Minnesota, Wisconsin and the Upper Peninsula of Michigan.
Key services
Monetary Policy, Banking Supervision, Financial Services, Community Development & Outreach, Economic Research
Content quality
excellent
Branding
consistent

Technology

Stack
jQuery, Bootstrap, Slick Carousel, Constant Contact, Google Analytics, Google Tag Manager, reCAPTCHA
Frameworks
Bootstrap 4.3.1
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Use of reCAPTCHA for forms
  • Google Tag Manager for controlled script loading

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Marketing tools
Constant Contact
Transparency
good

Site quality

Design
excellent
User experience
excellent
Content relevance
excellent
Navigation
excellent
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Website is professionally designed and well-structured
  2. Content is rich with economic research, policy information, and community engagement
  3. No visible contact emails or phone numbers explicitly labeled as company contacts in the provided HTML snippet
  4. Social media links are official and consistent with the Federal Reserve Bank branding
  5. No privacy or cookie policy pages explicitly found in the provided content
  6. No security.txt or vulnerability disclosure information found
  7. Use of modern JavaScript libraries and frameworks
  8. No signs of adult or questionable content
  9. WHOIS data retrieval failed, limiting domain registration analysis
Technical notes

Notes

The website uses a modern and stable technology stack including Bootstrap 4.3.1 for responsive design, jQuery for DOM manipulation, and Slick Carousel for interactive content display. It integrates third-party services such as Google Analytics and Tag Manager for analytics and tracking, and Constant Contact for email marketing. The site is mobile optimized with good accessibility features and clear navigation. Performance is moderate, with potential improvements in loading speed by optimizing external scripts and images. No CMS was explicitly detected, suggesting a custom or proprietary platform. The hosting provider is not identified from the provided data.
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 minneapolisfed.org. 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 minneapolisfed.org.

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.