Skip to main content

Security report for centralbankonline.com

Central Bank · Finance · United States

Medium risk. 5 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

62/100

Risk levelMedium

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

Central Bank is a well-established, family-owned community bank serving Iowa and South Dakota with a broad range of financial services including personal and business banking, mortgages, and insurance. The website reflects a strong regional focus with clear navigation and comprehensive service offerings tailored to local customers. The bank emphasizes local decision-making and customer service, positioning itself as a trusted community financial institution. Technically, the website employs modern web technologies such as jQuery, Slick Slider, and Google Analytics, with good mobile optimization and SEO practices. Security posture is adequate with HTTPS usage and external link warnings, but lacks visible advanced security headers and explicit incident response policies. Privacy compliance is partial with a privacy policy present but no cookie consent mechanism. Overall, the site is professional, trustworthy, and credible, with room for improvement in security and privacy transparency.

Scanned

NIS2 and GDPR posture

GDPR outside view
33/ 100 · High
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

5 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.

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

    • 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

  2. 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.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  3. 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';…

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

Keep watching centralbankonline.com

This scan found 14 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
0
Security headers
70
Email security
85
DNS health
85
Network security
100
GDPR outside view
33
Average
62

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

Central Bank operates in the finance sector as a medium-sized community bank with a history dating back to 1877. Its business model focuses on providing diversified financial products including checking and savings accounts, loans, credit cards, treasury management, mortgages, and insurance through partnerships. The bank targets individuals and businesses in its regional markets, leveraging local branch presence and personalized service as competitive advantages. The website's integration with partner domains for online banking and rewards programs indicates a mature partnership ecosystem. The bank's market position is that of a trusted local institution with strong community ties and a comprehensive digital presence.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enforced and a speed bump mechanism for external links to warn users. However, no explicit security headers (such as CSP, HSTS) were detected in the provided data, and there is no published security policy or incident response contact information. The use of third-party scripts like Google Analytics and Tag Manager is standard but requires ongoing monitoring for vulnerabilities. No exposed sensitive data or vulnerabilities were identified in the HTML content. Privacy compliance is partial, lacking cookie consent mechanisms and GDPR indicators. Overall, the security posture is adequate for a financial institution's public website but could be enhanced with stronger headers, transparency, and incident response readiness.

Recommendations

  1. Implement and enforce security headers such as Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options to enhance protection against common web attacks.
  2. Add a cookie consent banner and detailed cookie policy to comply with privacy regulations and improve user transparency.
  3. Publish a dedicated security policy and provide clear incident response contact channels (e.g., security@ or abuse@ email addresses).
  4. Regularly audit and update third-party scripts and libraries to mitigate risks from vulnerable dependencies.
  5. Enhance accessibility features to meet WCAG standards and improve user experience for all visitors.

Contact details published on the site

Addresses
Legal name
Central Bank
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Central Bank
Description
Central Bank is a family-owned community bank serving Iowa and South Dakota, offering personal and business banking, mortgage, and insurance services with a focus on local decision making and customer service.
Key services
Personal Checking, Personal Savings, Loans & Lines of Credit, Credit Cards, Online & Mobile Banking, Business Checking, Commercial Loans, Treasury Management, Mortgage Loans, Insurance
Content quality
good
Branding
consistent

Technology

Stack
jQuery 3.7.1, Slick Slider, Google Analytics, Google Tag Manager, LazySizes (lazy loading images), Async script loader ($script.js), Modernizr (conditional for IE9 and below)
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS usage implied
  • External link speed bump warning implemented
  • No inline sensitive data exposure detected

Analytics and tracking

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

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is professionally designed with clear navigation and consistent branding.
  2. Strong presence of banking and financial services content tailored to local communities.
  3. Use of modern web technologies and analytics tools.
  4. No signs of blocking or WAF interference.
  5. Privacy and cookie policies exist but cookie consent mechanism is missing.
  6. Security headers and explicit security policies are not visible in the provided data.
  7. External links to trusted partner domains and social media are present.
  8. Contact information is prominently displayed and consistent.
Technical notes

Notes

The website is built on a modern technology stack including jQuery 3.7.1, Slick Slider for UI components, and Google Analytics/Tag Manager for tracking. It uses lazy loading for images to optimize performance and a custom async script loader for dependency management. The CMS appears to be Blue Compass, inferred from copyright and script paths. The site is mobile optimized with responsive design and good SEO metadata including Open Graph and JSON-LD structured data. Performance is moderate with room for improvement in loading speed and accessibility. No major technical debt or outdated technologies were detected, indicating a well-maintained infrastructure.
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 centralbankonline.com. 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 centralbankonline.com.

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.