Skip to main content

Security report for oplayo.com

OPLAYO GmbH · Technology · Germany

High risk. 7 critical or high findings in Network security, Security headers and 2 other checks.

Security score

49/100

Risk levelHigh

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

Oplayo GmbH is a German-based technology company specializing in privacy-compliant server-side tracking and AI analytics services. Their website emphasizes GDPR readiness and offers integrations with Google Analytics 4 and other analytics platforms. The company targets businesses seeking advanced, privacy-focused analytics solutions. Technically, the website is built on TYPO3 CMS and integrates multiple third-party analytics and advertising tools, including Google Tag Manager, Cookiebot, and Facebook Ads. The site demonstrates good mobile optimization and user experience, with clear cookie consent mechanisms and detailed cookie information. Security-wise, HTTPS is enforced, but explicit security headers and incident response information are lacking, which could be improved. The WHOIS data is unavailable, which slightly reduces trust but the professional presentation and compliance focus mitigate concerns.

Scanned

NIS2 and GDPR posture

GDPR outside view
95/ 100 · Low
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. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • Critical

      Critical Service Exposed: MySQL

      Port 3306 (MySQL) is publicly accessible - MySQL - Database server

      What to do: Immediately restrict access to MySQL using firewall or VPN

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

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

  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

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

Keep watching oplayo.com

This scan found 25 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
72
Security headers
30
Email security
60
DNS health
60
Network security
0
GDPR outside view
95
Average
53
After the cap
49

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 · found on this site
  • 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

Oplayo operates in the niche market of privacy-compliant analytics and tracking solutions, leveraging server-side technologies and AI analytics to differentiate itself. The business model is service-oriented, targeting enterprises and SMEs in Germany and Europe that require GDPR-compliant tracking. The company uses a modern tech stack and partners with major analytics and advertising platforms. The presence of detailed cookie consent and privacy policies indicates a strong compliance posture. No parent or subsidiary companies were identified. The company appears to maintain a consistent brand and professional online presence, supporting its credibility in the technology sector.

Security posture

The website enforces HTTPS and uses cookie consent management to comply with privacy regulations. However, the absence of explicit security headers such as Content Security Policy, HSTS, and X-Frame-Options is a gap. No security.txt or incident response contacts were found, which limits transparency for vulnerability reporting. The integration of multiple third-party tracking and advertising services increases the attack surface but is managed with consent mechanisms. Overall, the security posture is moderate with room for improvement in headers and incident response readiness.

Recommendations

  1. Implement and enforce security headers including CSP, HSTS, and X-Frame-Options to enhance protection against common web attacks.
  2. Publish a security.txt file and provide clear incident response contact information to improve vulnerability disclosure and response.
  3. Regularly audit third-party scripts and tracking services to minimize privacy and security risks.
  4. Enhance accessibility features to improve compliance and user experience for all users.
  5. Consider obtaining and displaying relevant security certifications or trust badges to strengthen business credibility.

Contact details published on the site

Addresses
Legal name
OPLAYO GmbH
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
OPLAYO GmbH
Description
Oplayo realisiert datenschutzkonformes Website-Tracking, AI-Analytics und GA4-Integrationen. Server-Side, DSGVO-ready, messbar besser.
Key services
Server-Side Tracking, AI Analytics, GA4 Integrations, Privacy-compliant website tracking
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, Google Tag Manager, Cookiebot, Ahrefs Analytics, Google Ads, VIPIMO tracking
Frameworks
TYPO3 CMS
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent banner implemented
  • Service worker unregister script to avoid stale caches

Analytics and tracking

Services
Google Analytics, Ahrefs Analytics, Leadinfo
Tracking level
extensive
Privacy practices
good

Advertising

Ad networks
Google Ads, Google DoubleClick, Facebook Ads
Tracking pixels
Cookiebot, Ahrefs Analytics, Leadinfo
Marketing tools
Cookiebot, VIPIMO
Transparency
good

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. Uses TYPO3 CMS with modern tracking and consent management
  3. Strong focus on privacy compliance and GDPR readiness
  4. WHOIS data unavailable, possibly due to domain not registered or privacy protection
  5. No direct contact emails found in HTML; phone number and address present in structured data
  6. Cookie consent banner and detailed cookie info present
  7. Multiple third-party analytics and advertising services integrated
  8. No explicit security.txt or incident response info found
  9. No visible security headers detected in provided data
Technical notes

Notes

The website uses TYPO3 CMS, a robust open-source content management system, indicating a mature technical foundation. It integrates modern analytics and marketing technologies such as Google Tag Manager, Cookiebot for consent management, and various tracking pixels. Performance is moderate, with asynchronous loading of scripts to optimize speed. Mobile optimization is good, and SEO practices are evident through meta tags and structured data. However, no hosting provider information was detected, and security headers are missing, which could expose the site to certain risks. The technical stack is modern but could benefit from enhanced security configurations and performance tuning.
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 oplayo.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 oplayo.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.