Skip to main content

Security report for rlp-tennis.de

Tennisverband Rheinland-Pfalz e. V. · Other · Germany

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

Security score

60/100

Risk levelMedium

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

The Tennisverband Rheinland-Pfalz e. V. operates as a regional tennis association in Germany, providing comprehensive tennis-related news, event management, training, and support services to clubs and players in Rheinland-Pfalz. The website serves as an information hub for tennis enthusiasts, clubs, and officials, reflecting a well-established organization with a strong regional presence and a history dating back to 1948. The association is positioned among the top ten tennis federations in Germany, emphasizing youth development, inclusion, and adult tennis activities. Technically, the website is built on the TYPO3 CMS platform with Bootstrap for responsive design, integrating accessibility tools such as eyeAble and analytics via Google Tag Manager. The site demonstrates good mobile optimization, clear navigation, and structured content, supporting a positive user experience. Hosting appears stable with dedicated nameservers, and the site uses HTTPS, although explicit security headers are not detected. From a security perspective, the site shows a moderate security posture with secure login forms and no visible sensitive data exposure. However, it lacks explicit security policies, incident response contacts, and cookie consent mechanisms, which are important for GDPR compliance and user trust. The WHOIS data aligns well with the organization's identity, showing consistent registration details and no privacy protection, indicating transparency and legitimacy. Overall, the website is professional, trustworthy, and serves its target audience effectively. Strategic improvements in security headers, privacy compliance, and published security policies would enhance its security posture and regulatory adherence.

Scanned

NIS2 and GDPR posture

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

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

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • 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

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

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

Keep watching rlp-tennis.de

This scan found 26 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. See sample alerts.

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
77
Security headers
25
Email security
70
DNS health
60
Network security
100
GDPR outside view
28
Average
60

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention rlp-tennis.de, from OffSeq Breach.

No leaked records found

Breach holds no records for rlp-tennis.de right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

The Tennisverband Rheinland-Pfalz e. V. holds a significant position in the regional sports sector, focusing on tennis development and community engagement. Its business model is non-profit, centered on supporting clubs, organizing competitions, and providing training and resources. The association benefits from partnerships with regional and national tennis bodies, enhancing its service offerings and credibility. Revenue streams likely include membership fees, event sponsorships, and training program fees. The target customers are tennis players, clubs, trainers, and youth in Rheinland-Pfalz. Growth indicators include active event calendars, youth programs, and digital presence. The partnership ecosystem includes regional tennis associations and the German Tennis Federation, supporting a collaborative sports environment.

Security posture

The website exhibits a moderate security maturity level with HTTPS enabled and secure form handling. However, the absence of key security headers such as Content Security Policy, HSTS, and X-Frame-Options reduces its defense-in-depth. No vulnerabilities or exposed sensitive data were detected in the HTML content. Compliance with GDPR is indicated by the presence of a privacy policy, but the lack of a cookie consent mechanism and incident response information suggests gaps in privacy and security governance. The site does not publish a vulnerability disclosure policy or security.txt file, limiting transparency for security researchers. Overall, the security culture appears basic but could be improved with formalized policies and technical enhancements.

Recommendations

  1. Implement comprehensive security headers including CSP, HSTS, and X-Frame-Options to strengthen browser security.
  2. Deploy a cookie consent banner/mechanism to ensure full GDPR compliance and user transparency.
  3. Publish a clear security policy and incident response contact information to improve trust and readiness.
  4. Establish a vulnerability disclosure policy and consider adding a security.txt file to facilitate responsible reporting.
  5. Regularly audit and update CMS and third-party libraries to mitigate risks from outdated components.

Contact details published on the site

Addresses
Legal name
Tennisverband Rheinland-Pfalz e. V.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Tennisverband Rheinland-Pfalz e. V.
Description
Der Tennisverband Rheinland-Pfalz e. V. ist der Landesverband für Tennis in Rheinland-Pfalz mit ca. 800 Vereinen und 85.000 Tennisspieler/innen. Er bietet Nachrichten, Informationen, Spielbetrieb, Ausbildung, und Vereinsservice rund um Tennis.
Key services
Nachrichten und Informationen, Spielbetrieb und Turniere, Ausbildung und Trainerangebote, Vereinsservice und Beratung, Jugendförderung
Content quality
good
Branding
consistent

Technology

Stack
TYPO3 CMS, Bootstrap, Google Tag Manager, eyeAble accessibility scripts
Frameworks
Bootstrap
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
70/100
Good practices seen
  • HTTPS usage implied by URL
  • No exposed sensitive data in HTML
  • Secure login form with POST method

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

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 and not blocked by WAF or security mechanisms.
  2. Content is well-structured and relevant to tennis in Rheinland-Pfalz.
  3. Clear contact information and social media presence enhance trust.
  4. No explicit privacy or security policies beyond basic GDPR compliance detected.
  5. Use of modern CMS TYPO3 and Bootstrap framework.
  6. No evident security vulnerabilities or suspicious external links.
  7. No cookie consent mechanism detected despite GDPR compliance indication.
  8. No terms of service or vulnerability disclosure policy found.
Technical notes

Notes

The website is built on TYPO3 CMS with Bootstrap framework, ensuring responsive design and accessibility. It integrates Google Tag Manager for analytics and eyeAble for accessibility enhancements. Hosting is managed via dedicated nameservers (your-server.de and second-ns domains), suggesting a professional hosting environment. Performance is moderate with compressed CSS and JS assets, but no explicit performance metrics are available. The site is mobile-optimized and SEO-friendly with proper meta tags and structured navigation. Technical risks include missing security headers and lack of explicit privacy consent mechanisms. Opportunities exist to modernize security practices and enhance privacy compliance to align with 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 rlp-tennis.de. 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 rlp-tennis.de.

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.