Skip to main content

Security report for creamfinance.com

CreamFinance · Finance · N/a

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

Security score

43/100

Risk levelHigh

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

CreamFinance is a mature digital lending company founded in 2012, providing unsecured consumer loans across multiple international markets. The company leverages proprietary data science and technology to assess creditworthiness and deliver loans efficiently. Their business model focuses on digital consumer lending with a presence in seven countries and over 400 employees. The website reflects a professional and consistent brand with clear business information and subsidiary brands. Technically, the site is built on WordPress with common plugins and uses Cloudflare and WP Engine for hosting. However, the absence of a valid SSL certificate and HTTPS severely impacts security posture. Cookie consent and privacy policies are well implemented, supporting GDPR compliance. Security headers and advanced protections are minimal, and no incident response or security policies are publicly disclosed. Overall, the site is functional and informative but requires urgent security improvements to protect user data and enhance trust.

Scanned

This is an earlier scan of creamfinance.com. View the latest report

NIS2 and GDPR posture

GDPR outside view
18/ 100 · Critical
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

7 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

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

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

Keep watching creamfinance.com

This scan found 20 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
0
Security headers
15
Email security
50
DNS health
75
Network security
100
GDPR outside view
18
Average
43

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

CreamFinance operates in the finance sector, specializing in unsecured consumer loans with a data-driven approach to credit risk management. Their market positioning is strong with multiple subsidiaries and a global footprint. The company emphasizes operational excellence and cost discipline. Revenue and loan issuance figures indicate a growing business. The website highlights a professional team with LinkedIn profiles, supporting credibility. The business model is digital-first, targeting consumers seeking quick and accessible loans. Partnerships and subsidiaries are clearly presented, indicating a structured corporate ecosystem. The company invests in employee growth and benefits, reflecting a positive corporate culture.

Security posture

The website currently lacks a valid SSL certificate, resulting in no HTTPS support, which is a critical security flaw. No modern TLS protocols are enabled, and security headers such as HSTS are missing. The SPF record is correctly configured, and no subdomain takeover vulnerabilities were found. Cookie consent mechanisms are in place, supporting privacy compliance. However, the absence of incident response contacts, security policies, and vulnerability disclosure mechanisms indicates limited transparency in security governance. The overall security maturity is low, exposing users to risks such as data interception and trust issues. Immediate remediation of SSL/TLS and security headers is recommended to improve the security posture.

Recommendations

  1. Install and maintain a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable modern TLS protocols (TLS 1.2 or 1.3) and disable deprecated protocols.
  3. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives.
  4. Correct and properly configure CAA DNS records to restrict certificate issuance.
  5. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  6. Publish a security policy and incident response contact information to improve transparency and trust.
Technical notes

Notes

The website is built on WordPress CMS with plugins including Yoast SEO, Contact Form 7, and Slick Carousel. It uses jQuery and Google Tag Manager for analytics and marketing. Hosting is provided by WP Engine behind Cloudflare CDN. The site is mobile optimized with responsive design and good SEO metadata including Open Graph and JSON-LD structured data. Performance metrics are missing, but the site uses modern fonts and asynchronous script loading. Accessibility is basic but present. The lack of HTTPS and security headers is a major technical risk. The site architecture is well structured with clear navigation and multiple subsidiary brand links. Technical debt is moderate, with opportunities to improve security and performance monitoring.
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

Earlier scans of this domain

  1. 70/100Medium33 findingsView report
Reviews of this site

Share your experience with creamfinance.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 creamfinance.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.