SaaS Ranking

security.txt (RFC 9116) in Venue ticketing

It tells a researcher where to report a vulnerability instead of guessing.

0 of 27 companies we measured here publish it, that is 0%. Last checked 2026-10-18.

0% here against 11% across every category we measure. Venue ticketing sits below the overall share for this criterion.

This page counts companies, not product entries: a company with two products in this category is one company here and two rows below.

Back to security.txt (RFC 9116) across all categories, or to Venue ticketing.

The evidence at a glance
  • Found0
  • Not found at checked addresses27
  • Not measured11

38 companies in total. Unmeasured companies are excluded from the published share.

Published

Served at /.well-known/security.txt.

None of the companies we measured here published this.

No security.txt found.

We reached at least one address for each of these vendors and none of them carried it. That is what we found at the addresses we checked, on the date we checked them, and not a statement about what the vendor has.

VendorWhat we found
accesso 1 address checkedChecked
Agile Ticketing Solutions 1 address checkedChecked
AudienceView 1 address checkedChecked
Connect&GO 1 address checkedChecked
Digitickets 1 address checkedChecked
Eventix 1 address checkedChecked
Fatsoma 1 address checkedChecked
Galaxy Ticketing 1 address checkedChecked
Leap Events 1 address checkedChecked
n-gage.io 1 address checkedChecked
PatronManager 1 address checkedChecked
Prism 1 address checkedChecked
Roller 1 address checkedChecked
Semnox 1 address checkedChecked
Skiddle 1 address checkedChecked
Tessitura 1 address checkedChecked
ThunderTix 1 address checkedChecked
TicketCo 1 address checkedChecked
TicketingHub 1 address checkedChecked
Ticketmaster Presence 1 address checkedChecked
TicketSpice 1 address checkedChecked
Ticketure 1 address checkedChecked
TicketWeb 1 address checkedChecked
Vantix 1 address checkedChecked
Veevart 1 address checkedChecked
VISIT 1 address checkedChecked
Yapsody 1 address checkedChecked
Not measured

We could not look at these, or their robots.txt asks us not to. That says something about our measurement, not about them, and they are left out of the percentage above.

VendorWhat we found
Aluvii The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked
DICE The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked
Gatemaster The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked
Merac None of the addresses could be reached, so this was not measured.Checked
Purplepass The vendor’s robots.txt excludes us from at least one of these addresses, so this was not measured.Checked
See Tickets The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked
Spektrix The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked
Ticketbud The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked
TicketSource The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked
Tix The vendor’s server blocked or rate-limited our crawler, so this was not measured.Checked
Univents None of the addresses could be reached, so this was not measured.Checked

Other criteria in Venue ticketing

security.txt (RFC 9116) in related categories

Found something we missed? Tell us. A correction moves that vendor into our next nightly run. That run reads the same fixed addresses we check for every vendor, not the address you send.