Skip to main content

Security report for openticket.tech

Openticket · Technology · N/a

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

Security score

65/100

Risk levelMedium

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

Openticket.tech is a technology company offering a 100% API-based white-label e-ticketing platform designed to help businesses quickly launch and manage their own ticketing services. The website positions itself as a cost-effective and customizable e-ticketing as a service (eTAAS) solution, targeting developers and businesses seeking fast market entry with extensive API capabilities. The platform emphasizes ease of setup, cost reduction, and feature-rich user experience. Technically, the website is built on the Webflow platform, leveraging modern web technologies such as jQuery and Lottie animations, ensuring fast performance and excellent mobile responsiveness. Security posture is adequate with HTTPS enforced and secure form handling, but lacks advanced security headers and published security policies. Privacy compliance is partial, with privacy and terms pages present but no cookie policy or consent mechanism. Contact is primarily via web forms, with no direct emails or phone numbers published. Overall, the site is professional and trustworthy but could improve transparency and compliance aspects.

Scanned

NIS2 and GDPR posture

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

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

  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 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 openticket.tech

This scan found 23 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
57
Security headers
30
Email security
70
DNS health
75
Network security
100
GDPR outside view
58
Average
65

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

The company operates in the technology sector, focusing on SaaS delivery of e-ticketing solutions via APIs. Its business model is centered on white-label services, enabling clients to customize and integrate ticketing functionalities into their own platforms. Market positioning highlights speed to market and cost efficiency as competitive advantages. The target audience includes startups, event organizers, and developers requiring scalable ticketing infrastructure. The website shows moderate trust signals such as demo request forms and social media presence but lacks direct contact details and certifications. Partnerships with Webflow and Flowyak indicate a reliance on established web development ecosystems. Growth potential is tied to the increasing demand for digital ticketing solutions. No parent or subsidiary companies are identified.

Security posture

Security maturity is moderate. The site uses HTTPS, ensuring encrypted communications. However, it lacks important security headers like Content-Security-Policy and X-Frame-Options, which could mitigate common web attacks. No incident response or security contact information is published, limiting transparency in handling security events. Forms are secured with required email inputs but no advanced anti-bot or CAPTCHA mechanisms are evident. No vulnerability disclosure or security.txt files are present. Privacy compliance is partial, with GDPR-related policies but no cookie consent mechanism. No exposed sensitive data or vulnerable libraries were detected. Overall, the security posture is adequate for a marketing site but could be improved to meet higher compliance and security standards.

Recommendations

  1. Implement comprehensive security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  2. Add a cookie policy page and implement a cookie consent banner to comply with privacy regulations.
  3. Publish an incident response policy and provide dedicated security contact channels such as security@ or abuse@ emails.
  4. Consider adding a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  5. Enhance contact transparency by providing verified company contact emails and phone numbers.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Openticket
Description
Openticket provides a 100% API-based white-label e-ticketing platform enabling businesses to manage their own ticketing systems quickly and cost-effectively.
Key services
E-ticketing platform, API endpoints for ticketing management, White-label customizable solutions
Content quality
good
Branding
consistent

Technology

Stack
Webflow, Google Fonts (Inter), jQuery 3.5.1, Lottie animations
Frameworks
Webflow CMS
Platforms
Webflow hosting
Performance
fast
Mobile
excellent
Accessibility
basic
SEO
basic

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Secure form submissions with required email fields

Analytics and tracking

Tracking level
minimal
Privacy practices
basic

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Content is focused on promoting an API-based e-ticketing platform.
  3. No direct company contact emails or phone numbers found; contact is via forms.
  4. Privacy and terms pages exist but cookie policy and consent are missing.
  5. No explicit security policies or incident response information published.
  6. Technical implementation uses modern Webflow platform and standard web technologies.
  7. Social media presence includes Facebook, Instagram, and Twitter links.
  8. No analytics or tracking scripts detected beyond standard Webflow and jQuery.
  9. No advertising or affiliate marketing detected.
Technical notes

Notes

The website is built on the Webflow CMS platform, utilizing Google Fonts (Inter), jQuery 3.5.1, and Lottie animations for interactive elements. Hosting is via Webflow's CDN, contributing to fast loading times and excellent mobile optimization. The site uses semantic HTML with meta tags for viewport and description, but lacks Open Graph or JSON-LD structured data for enhanced SEO and social sharing. Accessibility features are basic, with some ARIA roles and labels present. No analytics or tracking scripts beyond Webflow's default were detected, indicating minimal user tracking. The technical implementation is modern and well-structured but could benefit from enhanced SEO metadata and accessibility improvements.
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 openticket.tech. 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 openticket.tech.

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.