Skip to main content

Security report for evvnt.com

Evvnt · Technology · N/a

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

Security score

75/100

Risk levelMedium

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

Evvnt is an online platform specializing in event ticketing and promotion, leveraging a network to increase ticket demand. The website is built on WordPress using the Divi theme and integrates multiple marketing and analytics tools such as Facebook Pixel, LinkedIn Insight Tag, and Google Tag Manager. The technical infrastructure is modern and moderately optimized for performance and mobile use. Security posture is adequate with HTTPS enabled and domain protections in place, but lacks advanced DNS security and security headers. Privacy compliance is weak due to absence of privacy and cookie policies and no visible consent mechanisms. Overall, the site is professional and functional but would benefit from enhanced privacy and security transparency.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 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 evvnt.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
55
Email security
80
DNS health
85
Network security
100
GDPR outside view
53
Average
75

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

Evvnt operates in the technology sector focusing on event management services. Its business model revolves around providing ticketing and promotional services to event organizers and promoters. The company has been established since 2012, indicating market experience. The website targets event professionals seeking to increase ticket sales and event visibility. The presence of multiple tracking and marketing tools suggests a data-driven approach to customer acquisition. However, the lack of explicit contact and policy information may impact trust and compliance with privacy regulations.

Security posture

The website demonstrates a basic to moderate security maturity level. HTTPS is properly implemented, and domain registration includes protective statuses against unauthorized changes. However, the absence of DNSSEC and security headers reduces the overall security robustness. No incident response or security policy information is provided, which limits transparency and preparedness. The use of multiple third-party scripts without visible consent mechanisms raises privacy concerns. No vulnerabilities or exposed sensitive data were detected in the analyzed content.

Recommendations

  1. Enable DNSSEC to enhance DNS security and prevent spoofing.
  2. Implement and publish comprehensive privacy and cookie policies with explicit consent mechanisms.
  3. Add security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options.
  4. Provide clear contact information including security incident response channels.
  5. Regularly audit third-party scripts and minimize tracking to improve privacy compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Evvnt
Description
Leverage the reach of our events network! Anyone can fulfill demand for your tickets… now let’s start increasing your demand.
Key services
Event ticketing, Event promotion, Event listing distribution
Content quality
good
Branding
consistent

Technology

Stack
WordPress, Divi Theme, Google Fonts, Google Maps API, Facebook Pixel, LinkedIn Insight Tag, YouTube Iframe API, Cloudflare DNS
Frameworks
WordPress, Divi
Platforms
Web
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • Domain status includes clientDeleteProhibited, clientTransferProhibited, clientUpdateProhibited

Analytics and tracking

Services
Google Tag Manager, Facebook Pixel, LinkedIn Insight Tag
Tracking level
extensive
Privacy practices
poor

Advertising

Tracking pixels
Facebook Pixel, LinkedIn Insight Tag
Marketing tools
Facebook Pixel, LinkedIn Insight Tag
Transparency
basic

Site quality

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

Key observations

  1. Website is a WordPress site using Divi theme with moderate performance.
  2. No explicit privacy, cookie, or terms of service pages found in the provided HTML.
  3. Contact information such as emails or phone numbers not found in the HTML content.
  4. Multiple third-party tracking scripts are present without visible consent mechanisms.
  5. No security.txt or vulnerability disclosure information found.
  6. No explicit security policies or incident response contacts found.
  7. Site uses HTTPS with valid SSL but lacks DNSSEC.
  8. No suspicious or malicious content detected.
Technical notes

Notes

The website uses a WordPress CMS with the Divi theme, integrating Google Fonts and Google Maps API for enhanced user experience. Marketing and analytics are supported by Facebook Pixel, LinkedIn Insight Tag, and Google Tag Manager. Hosting and DNS are managed via Amazon Registrar and Cloudflare respectively. Performance is moderate with good mobile optimization. Accessibility features are basic, and SEO optimization is good with proper meta tags. The site lacks DNSSEC and advanced security headers, which are recommended for improved security posture.
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 evvnt.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 evvnt.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.