Skip to main content

Security report for ticket.io

Technology · N/a

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

ticket.io is a technology platform focused on providing ticketing services for events, targeting event organizers and attendees. The website is built on WordPress and optimized with WPRocket, indicating a moderate level of technical maturity. The content is professional and relevant, though some key compliance elements such as privacy and cookie policies are not detected in the provided content. Security posture appears basic with no advanced headers or security policies evident, and WHOIS data is protected, which is common but reduces transparency. Overall, the platform appears legitimate but would benefit from enhanced security and compliance measures.

Scanned

NIS2 and GDPR posture

GDPR outside view
80/ 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: SMB

      Port 445 (SMB) is publicly accessible - SMB - Windows file sharing, high risk

      What to do: Immediately restrict access to SMB 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
    • 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 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. 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

  4. 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 ticket.io

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. 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
72
Security headers
60
Email security
85
DNS health
80
Network security
0
GDPR outside view
80
Average
63
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

The business operates in the technology sector, specifically in event ticketing. The model likely involves providing a platform for ticket sales and event management. The website content suggests a focus on delivering a good user experience with clear branding and consistent design. However, the lack of visible contact information and compliance documentation may impact user trust. No partnerships or subsidiaries are identified from the data. The company size appears small based on available information.

Security posture

The security maturity level is basic. The website uses HTTPS (implied by resource URLs), but no explicit security headers are detected. There is no evidence of vulnerability disclosures, incident response contacts, or security certifications. The absence of privacy and cookie policies indicates compliance gaps, particularly with GDPR. No analytics or tracking scripts were detected, suggesting minimal user tracking. The WHOIS data is privacy protected, which is typical but reduces transparency. Recommendations include implementing security headers, publishing privacy and cookie policies, and establishing incident response contacts.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie policy with consent mechanisms.
  2. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Ensure WHOIS data transparency or provide clear business contact information on the website.
  4. Establish and publish incident response and vulnerability disclosure contacts.
  5. Conduct regular security audits and update third-party libraries to mitigate vulnerabilities.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
ticket.io appears to be a platform related to ticketing services, likely offering event ticket sales or management solutions.
Key services
ticket sales, event management
Content quality
good
Branding
consistent

Technology

Stack
WordPress, WPRocket, jQuery
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is accessible and not blocked by WAF or security mechanisms.
  2. WHOIS data is unavailable or protected, limiting domain ownership transparency.
  3. No explicit privacy, cookie, or terms of service policies detected in the provided HTML content.
  4. No contact emails or phone numbers explicitly found in the visible content.
  5. Website uses WordPress CMS with WPRocket optimization plugin.
  6. No security headers or advanced security configurations detected in the HTML content.
  7. No analytics or tracking scripts explicitly detected in the provided content.
  8. Content is professional and relevant to ticketing services.
  9. No adult or questionable content detected.
Technical notes

Notes

The website is built on WordPress CMS with WPRocket for performance optimization and uses jQuery. Fonts are loaded from the same domain, indicating self-hosting of assets. The site appears mobile optimized with responsive design. Performance is moderate based on the use of lazy loading scripts and preloading fonts. Accessibility is basic with standard HTML semantics but no advanced ARIA roles detected. SEO optimization is basic with meta tags present but no structured data or Open Graph tags found in the provided content. Hosting provider and SSL configuration details are not available from the data.
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

Earlier scans of this domain

  1. 49/100High29 findings · partial scanView report
Reviews of this site

Share your experience with ticket.io. 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 ticket.io.

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.