Skip to main content

Security report for deutscheliquidity.com

DWS · Finance · N/a

Medium risk. 4 critical or high findings in Security headers and GDPR outside view.

Security score

67/100

Risk levelMedium

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

The website deutscheliquidity.com appears to be related to financial services, specifically liquidity management and money market funds, as indicated by references to DWS and liquidity management product literature URLs. However, the site content is minimal with no visible privacy policies, contact information, or detailed business descriptions. The technical infrastructure is based on modern JavaScript frameworks such as Nuxt.js, but suffers from poor performance and lack of HTTPS security. The absence of a valid SSL certificate and lack of security headers represent critical vulnerabilities that significantly reduce the site's trustworthiness and security posture. Overall, the site demonstrates low digital maturity and poor privacy compliance, which could negatively impact user trust and regulatory adherence.

Scanned

NIS2 and GDPR posture

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

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 Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • 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 deutscheliquidity.com

This scan found 12 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
50
Security headers
75
Email security
50
DNS health
85
Network security
100
GDPR outside view
40
Average
67

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 business behind the site likely operates in the finance sector, focusing on liquidity management and investment products. The site references DWS, a known asset management brand, suggesting affiliation or content sourcing. However, no explicit company information, contact details, or certifications are present, limiting the ability to assess market positioning or competitive advantages. The lack of visible business data and minimal content suggests the site may be a partial or proxy landing page rather than a full corporate site. The target audience appears to be investors and financial professionals interested in liquidity products.

Security posture

The security posture is weak due to the absence of HTTPS and a valid SSL certificate, exposing users to potential interception and man-in-the-middle attacks. While DNS records show strict SPF and DMARC policies, the website itself lacks security headers, HSTS, OCSP stapling, and modern TLS protocols. No incident response or vulnerability disclosure information is available. These gaps indicate low security maturity and potential compliance risks, especially for a financial services-related site handling sensitive user data.

Recommendations

  1. Install and maintain a valid SSL/TLS certificate to enable HTTPS across the site.
  2. Implement HTTP security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Enable HSTS with includeSubDomains and preload options to enforce secure connections.
  4. Add visible and comprehensive privacy and cookie policies to improve compliance and user trust.
  5. Publish clear contact information and security incident response contacts to enhance transparency and support.
Technical notes

Notes

The site uses Nuxt.js, a modern Vue.js framework, indicating a contemporary front-end technology stack. However, the page load time is very slow (over 11 seconds) with a large page size (~2.3MB) and many resources (130). No CMS or backend platform is identified. Hosting appears to be via CSC DNS services. The lack of HTTPS and security headers, combined with slow performance, suggests technical debt and under-optimization. There is an opportunity to improve performance, security, and accessibility by optimizing assets, enabling HTTPS, and implementing best practices.
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 deutscheliquidity.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 deutscheliquidity.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.