Skip to main content

Security report for ivymayhem.io

ivy.mayhem GmbH · Technology · Germany

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

Security score

59/100

Risk levelMedium

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

ivy.mayhem GmbH is a Germany-based digital product and service studio specializing in SaaS platform development. Founded in 2016, the company develops and operates multiple SaaS products such as eniston, releasesapp, deftform, and others, serving a diverse clientele from startups to large corporations. The company recently expanded by acquiring stella.projects, a full-service web development agency, enhancing its service offerings. The website presents a professional and modern design with clear navigation and responsive layout, targeting technology-focused businesses and entrepreneurs. Technically, the site uses modern frontend technologies including Alpine.js and Tailwind CSS, hosted with Cloudflare DNS and agenturserver.de mail services. However, the website lacks a valid SSL certificate, resulting in no HTTPS support, which is a significant security concern. Security best practices such as HSTS, security headers, and OCSP stapling are absent, reducing the overall security posture. Privacy compliance is addressed with a comprehensive privacy policy and GDPR compliance statements, but no cookie consent mechanism is implemented. The site uses minimal user tracking via Fathom Analytics, respecting user privacy. Overall, the website is functional and professional but requires urgent improvements in SSL configuration and security headers to enhance trust and security.

Scanned

NIS2 and GDPR posture

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

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

Keep watching ivymayhem.io

This scan found 22 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
85
Security headers
50
Email security
55
DNS health
80
Network security
40
GDPR outside view
43
Average
59

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

ivy.mayhem operates in the technology sector focusing on SaaS product development and client services. Its business model combines proprietary SaaS ventures with client work, including the integration of stella.projects to broaden capabilities. The company targets startups, SMEs, and large corporations, positioning itself as a versatile product studio with a growing portfolio. Revenue streams likely include SaaS subscriptions and client project fees. The partnership ecosystem is expanding with plans for a partner ad network. The company emphasizes GDPR compliance and ISO 27001 certification, which are strong trust signals. Growth indicators include multiple product launches and recent acquisition activity. Strategic observations suggest a focus on scalable SaaS products and service diversification.

Security posture

The current security posture of the website is moderate to low due to the absence of a valid SSL certificate and HTTPS support, which is critical for protecting data in transit. The lack of security headers and HSTS further weakens the security stance. No vulnerabilities such as Heartbleed or POODLE were detected, and no subdomain takeover risks are present. The company claims ISO 27001 certification and GDPR compliance, indicating a mature security framework internally, but the website implementation does not fully reflect these standards. Incident response and vulnerability disclosure mechanisms are not publicly documented. Overall, the security maturity is adequate internally but requires immediate remediation on the public-facing website to align with best practices and regulatory requirements.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire website immediately.
  2. Implement HTTP security headers including Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, and Referrer-Policy.
  3. Enable HSTS with includeSubDomains and preload directives to enforce secure connections.
  4. Add a cookie consent mechanism to comply fully with GDPR requirements and enhance user trust.
  5. Publish a vulnerability disclosure policy or security.txt file to improve transparency and incident response readiness.
Technical notes

Notes

The website is built using modern frontend technologies such as Alpine.js and Tailwind CSS, providing a responsive and visually appealing user experience. Hosting is managed via Cloudflare DNS and agenturserver.de mail servers, ensuring reliable infrastructure. Performance is moderate with a page load time of approximately 6.3 seconds, which could be optimized further. SEO is well addressed with proper meta tags and structured content. Accessibility is basic but functional. The absence of a CMS suggests a custom or static site approach. Technical risks include the lack of HTTPS and security headers, which could expose users to man-in-the-middle attacks and reduce search engine ranking. Modernization opportunities include improving SSL configuration, optimizing performance, and enhancing accessibility features.
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 ivymayhem.io. 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 ivymayhem.io.

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.