Skip to main content

Security report for finance-watch.org

Finance Watch · Finance · N/a

Low risk. 3 critical or high findings in Security headers and SSL/TLS.

Security score

76/100

Risk levelLow

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

Finance Watch is a non-profit association dedicated to reforming finance in the interest of citizens. The website presents a professional and consistent brand image with a clear mission focused on financial reform advocacy. The technical infrastructure is based on WordPress CMS, enhanced with modern SEO and marketing tools such as HubSpot and Google Tag Manager, indicating a mature digital presence. Security posture is solid with HTTPS enforced and cookie consent mechanisms in place, though additional security headers and explicit security policies could further strengthen defenses. Privacy compliance is well addressed with clear privacy and cookie policies, reflecting GDPR awareness. Overall, the website is trustworthy and serves its advocacy purpose effectively.

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

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 Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • 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. 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 finance-watch.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. 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
55
Email security
75
DNS health
65
Network security
100
GDPR outside view
88
Average
76

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention finance-watch.org, from OffSeq Breach.

No leaked records found

Breach holds no records for finance-watch.org right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Finance Watch operates in the finance sector as a non-profit entity focusing on policy reform and public interest representation. Its market position is that of an established advocacy group targeting citizens and financial stakeholders. The business model revolves around research, advocacy, and influencing financial regulations. The organization leverages digital marketing and analytics tools to engage its audience and measure impact. No direct contact details or partner domains were identified in the provided data, suggesting a controlled communication channel primarily via web forms. The absence of WHOIS registrant data is typical for privacy-conscious non-profits.

Security posture

The website demonstrates a good security maturity level with HTTPS enabled and cookie consent implemented. However, the lack of visible security headers such as Content-Security-Policy or X-Frame-Options suggests room for improvement. No vulnerabilities or exposed sensitive data were detected in the analyzed content. The absence of a published security policy or incident response contact limits transparency in security governance. The use of third-party marketing and analytics scripts introduces a moderate tracking footprint, which is managed with consent mechanisms. Overall, the security posture is adequate but could benefit from enhanced header policies and explicit vulnerability disclosure.

Recommendations

  1. Implement comprehensive security headers including Content-Security-Policy and X-Frame-Options.
  2. Publish a dedicated security policy and incident response contact information.
  3. Consider adding a vulnerability disclosure or security.txt file to improve transparency.
  4. Regularly audit third-party scripts to minimize potential vulnerabilities.
  5. Enhance contact information availability to improve business credibility and user trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Finance Watch
Description
Finance Watch is a non-profit association dedicated to reforming finance in the interest of citizens.
Key services
Finance reform advocacy, Policy research, Public interest representation
Content quality
good
Branding
consistent

Technology

Stack
WordPress, Google Fonts, HubSpot scripts, Facebook Pixel, Google Tag Manager
Frameworks
All in One SEO Pro
Platforms
WordPress
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent banner implemented

Analytics and tracking

Services
HubSpot Analytics, Google Analytics (via GTM)
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Facebook Pixel, HubSpot Analytics
Marketing tools
HubSpot
Transparency
good

Site quality

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

Key observations

  1. Website is accessible and fully functional.
  2. Content is focused on finance reform advocacy.
  3. No exposed sensitive data or security issues detected.
  4. Use of modern marketing and analytics tools.
  5. Privacy and cookie policies are implemented with consent mechanisms.
  6. WHOIS data is privacy protected, limiting domain ownership transparency.
  7. No direct contact emails or phone numbers found in provided HTML.
  8. Social media links not explicitly found in provided snippet.
Technical notes

Notes

The website is built on WordPress CMS with integration of modern SEO and marketing frameworks such as All in One SEO Pro and HubSpot. It uses Google Fonts for typography and includes tracking scripts from HubSpot, Facebook Pixel, and Google Tag Manager. The site is mobile optimized with good accessibility features and moderate performance. The technical implementation follows best practices for metadata and structured data, improving SEO and social media sharing. Hosting provider details are not explicitly found. The site could improve by optimizing performance further and adding advanced security headers.
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 finance-watch.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 finance-watch.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.