Skip to main content

Security report for cakepay.com

Cake Labs LLC · Finance · United States

Medium risk. 5 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

73/100

Risk levelMedium

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

Cake Pay, operated by Cake Labs LLC, is a cryptocurrency payment platform established in 2018, offering secure and seamless crypto wallet and payment card services. The company targets crypto users seeking privacy and ease of spending digital assets globally. The website demonstrates a modern technical infrastructure built on Next.js and React with Ant Design UI components, optimized for mobile and desktop with good SEO and accessibility practices. Security posture is strong with HTTPS enforcement and comprehensive security headers, though explicit security policies and incident response contacts are not publicly visible. Privacy compliance is limited due to absence of visible privacy and cookie policies. Overall, the site is professional, trustworthy, and well-positioned in the crypto payment market.

Scanned

NIS2 and GDPR posture

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

5 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. 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

    • 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

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

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
35
Email security
85
DNS health
85
Network security
100
GDPR outside view
58
Average
73

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

Cake Pay serves a niche market of cryptocurrency users emphasizing privacy, self-custody, and multi-asset support including Monero, Bitcoin, Ethereum, and others. With over 500k users, it holds a medium-sized market presence in the fintech and crypto sectors. The business model revolves around providing crypto wallets, payment cards, and exchange services, targeting privacy-conscious consumers and crypto enthusiasts. The company maintains consistent branding and leverages modern web technologies. Partnerships or subsidiaries are not explicitly identified. The company’s US base aligns with its market focus and regulatory environment.

Security posture

The website employs HTTPS with strong SSL configuration and implements key security headers such as Content-Security-Policy, Strict-Transport-Security, and X-Frame-Options, indicating a mature security posture. No vulnerabilities or exposed sensitive data were detected in the HTML content. However, the absence of published security policies, incident response contacts, or vulnerability disclosure mechanisms suggests room for improvement in transparency and incident readiness. Privacy compliance is partial, lacking explicit GDPR statements or cookie consent mechanisms. Overall, the security posture is solid but could benefit from enhanced policy disclosures and user-facing security information.

Recommendations

  1. Publish comprehensive privacy and cookie policies with GDPR compliance details to improve privacy compliance score.
  2. Add a dedicated security policy and incident response page including contact channels such as security@ or abuse@ emails.
  3. Implement a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  4. Enhance transparency by providing physical contact information or phone numbers for customer support.
  5. Regularly review and audit third-party scripts and analytics tools to ensure no vulnerabilities or privacy risks.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Cake Labs LLC
Description
Cake Pay provides a secure, seamless, and reliable way to store, send, and exchange cryptocurrency with confidence. It empowers users to spend crypto easily anywhere, focusing on privacy, security, and self-custody.
Key services
Crypto wallet, Crypto payments, Crypto exchange, Payment cards
Content quality
good
Branding
consistent

Technology

Stack
React, Next.js, Ant Design, JavaScript, Web Fonts (woff2), SVG graphics
Frameworks
Next.js, Ant Design
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Use of modern security headers
  • No exposed sensitive data in HTML
  • Async loading of scripts

Analytics and tracking

Services
Fathom Analytics
Tracking level
minimal
Privacy practices
basic

Advertising

Tracking pixels
Fathom Analytics
Marketing tools
Fathom Analytics
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenge
  2. No explicit privacy, cookie, or terms of service pages found in provided content
  3. Contact email info@cakewallet.com found in Open Graph metadata
  4. Strong focus on cryptocurrency payment solutions and wallet services
  5. Use of modern web technologies and frameworks
  6. Good security header implementation and HTTPS usage
  7. Minimal tracking with privacy-respecting analytics (Fathom)
  8. No phone numbers or physical addresses explicitly found
  9. No social media links explicitly found in provided HTML snippet
  10. No forms detected in provided HTML content
Technical notes

Notes

The website is built using modern web technologies including React and Next.js frameworks, with Ant Design UI components for a polished user interface. It uses asynchronous script loading and web fonts optimized for performance. The site is mobile responsive and accessible with good SEO metadata including Open Graph and Twitter cards. Performance is moderate with room for optimization. Hosting provider details are not explicit but the site uses CDN for analytics scripts. No CMS detected, likely a custom or headless setup. Technical risks are minimal but continuous monitoring of dependencies and security headers is recommended.
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 cakepay.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 cakepay.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.