Skip to main content

Security report for eventrebels.com

Other · N/a

Medium risk. 6 critical or high findings in Security headers, GDPR outside view and 2 other checks.

Security score

63/100

Risk levelMedium

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

The website eventrebels.com currently presents extremely minimal content, consisting solely of a simple 'Hello, world!' message with no additional metadata, structured data, or business information. The domain is well-established, registered since 2000 with a reputable registrar and Cloudflare DNS hosting, indicating a legitimate registration history. However, the lack of substantive website content, absence of privacy and cookie policies, and no visible contact or business information significantly limit the site's digital maturity and user trust. Technically, the site lacks modern SEO, accessibility, and security best practices. No security headers or DNSSEC are enabled, and no analytics or advertising technologies are detected. The site is accessible without WAF or security challenges, but the minimal content and lack of technical sophistication suggest a very basic or placeholder web presence. From a security perspective, the site uses HTTPS but does not implement additional security headers or privacy compliance mechanisms. No vulnerabilities or exposed sensitive data were detected, but the absence of privacy policies and contact information represents compliance gaps. The domain registration is consistent and trustworthy, but the website itself does not provide sufficient information to assess business credibility or security posture comprehensively. Overall, the website scores low on content quality, technical implementation, privacy compliance, and business credibility, resulting in an overall AI score of 38 out of 100. Strategic recommendations include enhancing website content and metadata, implementing privacy and cookie policies, enabling DNSSEC, adding security headers, and improving accessibility and mobile optimization to build trust and compliance.

Scanned

NIS2 and GDPR posture

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

6 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 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 Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • 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 eventrebels.com

This scan found 24 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
45
Email security
70
DNS health
45
Network security
100
GDPR outside view
40
Average
63

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

Due to the lack of business-related content on the website, no detailed business intelligence can be derived. The domain age and registrar information suggest an established entity, but no information about market positioning, business model, revenue streams, or partnerships is available. The absence of contact details and company information limits insights into target customer segments or growth indicators.

Security posture

The security posture of the website is basic. HTTPS is enabled, but no additional security headers or DNSSEC are implemented. No incident response or vulnerability disclosure information is present. The site does not expose sensitive data or show signs of vulnerabilities but lacks compliance with privacy regulations and security best practices. The absence of privacy policies and contact channels for security incidents indicates gaps in security culture and readiness.

Recommendations

  1. Develop and publish comprehensive privacy and cookie policies to ensure GDPR and privacy compliance.
  2. Enable DNSSEC to enhance domain name system security and prevent DNS spoofing.
  3. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Enhance website content with relevant metadata, structured data, and business information to improve SEO and user trust.
  5. Add clear contact information and incident response channels to improve transparency and security readiness.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
No business description available from the provided content.
Content quality
poor
Branding
inconsistent

Technology

Performance
moderate
Mobile
poor
Accessibility
poor
SEO
poor

Security

Observed score
30/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is extremely minimal, containing only 'Hello, world!' text.
  2. No metadata, SEO tags, or structured data found.
  3. No forms, contact information, or social media links present.
  4. No privacy, cookie, or terms of service policies detected.
  5. Website uses Cloudflare DNS but does not enable DNSSEC.
  6. Domain is old and registered with a reputable registrar.
  7. No security headers or advanced security configurations detected.
  8. No analytics or advertising scripts detected.
  9. Website is accessible without WAF or security challenges.
Technical notes

Notes

The website is hosted behind Cloudflare DNS but does not utilize DNSSEC, which is a recommended security enhancement. The HTML content is minimal and lacks metadata, SEO tags, or structured data such as JSON-LD or Open Graph. No CMS or frameworks are detected. The site does not include any scripts, analytics, or advertising technologies. Performance and mobile optimization cannot be fully assessed due to minimal content but are likely poor. Accessibility features are absent. The technical infrastructure is basic and requires modernization to meet current web standards and security 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 eventrebels.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 eventrebels.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.