Ticket QR codes

Resold or transferred tickets are a common vector: a forwarded screenshot or PDF containing a ticket QR code can just as easily contain a substituted or fraudulent one, especially when tickets change hands outside the platform's official transfer feature. If you're buying a resold ticket, verify it directly within the ticketing platform's own app — never trust a screenshot alone, regardless of how official it looks.

Badge and check-in codes

Conference badges and event check-in codes are typically bulk-generated ahead of time and often contain more than just an identifier — sometimes networking or contact-sharing data. A code from an unfamiliar or unofficial event app, or a "scan to connect" prompt from someone you haven't actually spoken with, deserves the same scrutiny as any other unsolicited QR code.

For event organizers

Much of our business QR safety guide applies directly here, with one addition specific to events: because attendee-facing codes are often printed and displayed in high-traffic, loosely supervised areas (registration desks, signage, sponsor booths) for the duration of a single event, physical tampering has a narrow but real window of opportunity. A quick visual check of public event signage each morning of a multi-day event is a low-effort habit that closes most of that window.

If you're using a third-party ticketing or event platform

Treat that platform account the same way our static vs. dynamic QR codes guide describes — a compromised account can silently redirect every deployed code at once. Strong, unique credentials and two-factor authentication on that account matter as much as the physical signage.

Before you scan

Check any event code first

A quick check takes seconds and costs nothing — free, no account needed.

Check a QR code →