Skip to main content

Security report for bankunderground.co.uk

Bank of England · Finance · United Kingdom

Medium risk. 5 critical or high findings in Email security, Security headers and 1 other check.

Security score

63/100

Risk levelMedium

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

Bank Underground is an official research blog operated by the Bank of England, providing a platform for staff to share research and views on financial stability, monetary policy, and related economic topics. The website serves as a knowledge-sharing hub targeting Bank of England staff, economists, policymakers, and interested members of the public. It maintains a strong market position as an authoritative source of financial research and policy discussion. The technical infrastructure is based on WordPress CMS hosted on WordPress.com, leveraging modern technologies such as Jetpack, CookieYes for cookie consent management, and Google Analytics for traffic analysis. The site demonstrates excellent performance, mobile optimization, and accessibility, with a professional and consistent design. Security posture is solid with HTTPS enforced, standard security headers likely in place, and no visible vulnerabilities or exposed sensitive data. Privacy compliance is well addressed with a comprehensive privacy policy and cookie consent mechanism, including GDPR compliance indicators. However, explicit security policies, incident response contacts, and vulnerability disclosure mechanisms are absent. Overall, the website is trustworthy, professionally maintained, and aligned with the Bank of England's standards. Strategic recommendations include adding explicit security and incident response policies, publishing vulnerability disclosure information, and providing direct contact details for data protection and security inquiries.

Scanned

NIS2 and GDPR posture

GDPR outside view
88/ 100 · Low
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. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  2. 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 X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • 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';…

  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 Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1
    • 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 bankunderground.co.uk

This scan found 26 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
39
Security headers
30
Email security
60
DNS health
60
Network security
100
GDPR outside view
88
Average
63

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 Bank Underground blog functions as an internal and public-facing research dissemination platform for the Bank of England. It leverages the Bank's research agenda (BEAR) to focus on key themes such as prudential regulation, financial markets, climate risk, and macroeconomics. The business model is knowledge sharing and policy influence rather than direct commercial activity. The site benefits from the Bank's strong institutional reputation, providing competitive advantage in credibility and content quality. The partnership ecosystem includes WordPress.com hosting and third-party plugins for analytics and consent management. Growth indicators include regular publication of research articles and active engagement through comments and social media channels.

Security posture

The website exhibits a mature security posture with HTTPS enabled and likely standard security headers implemented. Cookie consent is managed via CookieYes, providing users control over tracking cookies. No exposed credentials or sensitive data were detected in the HTML content. The use of Jetpack and WordPress.com hosting adds layers of security and monitoring. However, the absence of a published security policy, incident response contacts, and vulnerability disclosure policy represents gaps in transparency and readiness. There is no evidence of outdated or vulnerable libraries. Overall, the site is secure but could improve by formalizing security governance documentation and contact channels.

Recommendations

  1. Publish a dedicated security policy page outlining security practices and commitments.
  2. Add incident response contact information such as security@ or abuse@ email addresses.
  3. Implement and publish a vulnerability disclosure policy and security.txt file.
  4. Provide contact details for the Data Protection Officer to enhance GDPR transparency.
  5. Regularly review and update third-party plugins and scripts to mitigate potential vulnerabilities.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Bank of England
Description
Bank Underground is a blog for Bank of England staff to share views that challenge or support prevailing policy orthodoxies. It covers topics related to financial stability, monetary policy, banking, macroeconomics, and related research areas.
Key services
Research publication, Policy discussion, Knowledge sharing
Content quality
excellent
Branding
consistent

Technology

Stack
WordPress, PHP, JavaScript, Google Fonts (Open Sans), CookieYes (cookie consent management), Jetpack plugin, Gutenberg editor, Google Analytics
Frameworks
WordPress CMS, Jetpack
Platforms
WordPress.com hosting (Atomic)
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent banner with customization
  • No exposed sensitive data in HTML
  • Use of security plugins (Jetpack)

Analytics and tracking

Services
Google Analytics, Jetpack Stats
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Jetpack Stats
Marketing tools
Jetpack Subscriptions, Juiz Social Post Sharer
Transparency
good

Site quality

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

Key observations

  1. Official Bank of England research blog with authoritative content
  2. Comprehensive cookie consent and privacy policy mechanisms
  3. No visible security or privacy red flags
  4. Use of modern WordPress CMS with Jetpack and CookieYes plugins
  5. Active content publishing with recent posts and comments
  6. Social media presence on LinkedIn and Bluesky
  7. No contact emails or phone numbers explicitly listed on homepage
  8. No terms of service or security policy pages found
  9. No vulnerability disclosure or security.txt detected
Technical notes

Notes

The website is built on a modern WordPress CMS platform hosted by WordPress.com, utilizing Jetpack for enhanced functionality and CookieYes for cookie consent management. The tech stack includes Google Fonts and Google Analytics for user experience and traffic insights. The site demonstrates good performance and mobile responsiveness, with valid HTML and CSS. Accessibility features such as skip links and ARIA labels are present. The technical debt appears low, with opportunities for modernization including adding structured data (JSON-LD) for enhanced SEO and formalizing security-related metadata. The hosting environment provides robust infrastructure and security benefits.
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 bankunderground.co.uk. 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 bankunderground.co.uk.

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.