Skip to main content

Security report for oneclickreporting.com

Bankhaus Metzler · Finance · Germany

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 website www.oneclickreporting.com/1clickreporting/ serves as a login portal for one-click reporting services, likely provided by Bankhaus Metzler, a reputable German financial institution. The portal targets clients requiring secure access to financial reporting tools. The site is primarily in German with an English option, reflecting a professional and client-focused service. The business model centers on providing secure online access to financial data and reporting services, positioning itself as a specialized service platform within the finance sector. Technically, the site is built using JavaServer Faces (JSF) with PrimeFaces UI components, jQuery, and Font Awesome for styling and interactivity. The presence of Google Fonts indicates some attention to design aesthetics. The site shows moderate performance and basic mobile optimization, with room for improvement in accessibility and SEO. The cookie consent mechanism is implemented, indicating awareness of privacy compliance requirements. From a security perspective, the site uses HTTPS and implements a cookie consent banner, but lacks visible security headers such as Content-Security-Policy or HSTS in the provided HTML content. No contact information or incident response details are present on the login page, and WHOIS data for the domain is unavailable, which raises concerns about domain legitimacy. However, the strong association with Bankhaus Metzler and links to their official domain for legal and privacy information mitigate some of these concerns. Overall, the site presents a professional and secure interface for its intended users but would benefit from enhanced security headers, improved transparency in contact and incident response information, and resolution of WHOIS data inconsistencies to strengthen trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
68/ 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

  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 oneclickreporting.com

This scan found 21 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
57
Security headers
55
Email security
70
DNS health
80
Network security
100
GDPR outside view
68
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

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 oneclickreporting.com, from OffSeq Breach.

No leaked records found

Breach holds no records for oneclickreporting.com 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

Bankhaus Metzler operates this portal as part of its financial services offering, targeting clients who require streamlined access to reporting tools. The business leverages a service portal model, focusing on secure client interactions and data delivery. The partnership with the main metzler.com domain for legal and privacy information suggests a centralized compliance and corporate governance approach. The lack of direct contact information on the portal indicates a controlled access environment, likely relying on existing client relationships. The company appears to maintain a medium-sized operation with a focus on finance, banking, and client service excellence. Growth opportunities may include expanding digital services and improving mobile and accessibility features to enhance client experience.

Security posture

The current security posture shows basic compliance with HTTPS and cookie consent but lacks advanced security headers and visible incident response mechanisms. The absence of WHOIS data is a notable risk factor, potentially impacting domain trustworthiness. No vulnerabilities or exposed sensitive data were detected in the provided HTML content. The site would benefit from implementing security best practices such as CSP, HSTS, and X-Content-Type-Options headers. Additionally, publishing clear security policies and incident response contacts would improve transparency and readiness. GDPR compliance appears addressed through cookie consent and links to privacy policies on the parent domain. Overall, the security maturity is moderate but requires enhancements to meet higher standards expected in financial services.

Recommendations

  1. Implement comprehensive security headers including Content-Security-Policy, HSTS, and X-Frame-Options to mitigate common web attacks.
  2. Resolve WHOIS data availability issues to improve domain legitimacy and trust.
  3. Enhance mobile optimization and accessibility to meet modern usability standards.
  4. Publish clear security policies and incident response contact information on the portal.
  5. Regularly audit and update privacy compliance measures to align with evolving regulations such as GDPR and NIS2.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Bankhaus Metzler
Description
The website provides a login portal for one-click reporting services, likely related to financial reporting or banking services offered by Bankhaus Metzler.
Key services
Online reporting, Client login portal
Content quality
good
Branding
consistent

Technology

Stack
JavaServer Faces (JSF), PrimeFaces, jQuery, Font Awesome, Google Fonts
Frameworks
PrimeFaces, JSF
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
60/100
Good practices seen
  • HTTPS usage implied by external links
  • Cookie consent mechanism implemented

Analytics and tracking

Tracking level
minimal
Privacy practices
good

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a login portal for financial reporting services.
  2. Content is in German with English language option.
  3. Cookie consent banner is implemented with language selection.
  4. No contact emails or phone numbers found on the login page.
  5. No social media links detected.
  6. No explicit privacy or security policy pages hosted on this domain; links point to metzler.com.
  7. No visible security headers in provided HTML content.
  8. WHOIS data unavailable, raising legitimacy questions but mitigated by association with Bankhaus Metzler.
Technical notes

Notes

The website utilizes a JavaServer Faces framework with PrimeFaces UI components, indicating a Java EE backend architecture. The frontend includes jQuery and Font Awesome for UI enhancements and iconography. Google Fonts are used for typography styling. The site is served with session-based URLs indicating stateful user sessions. Performance is moderate with no explicit optimization indicators. Accessibility and SEO are basic, with no ARIA landmarks or advanced metadata detected. The site lacks modern CMS integration and appears custom-built for the reporting service. Hosting provider details are not discernible from the HTML content. Technical debt may exist due to limited mobile responsiveness and missing security headers, suggesting opportunities for modernization and hardening.
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 oneclickreporting.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 oneclickreporting.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.