What is happening here
A fake event ticket QR code promises entry to a concert, match, or show, but the code is copied, forged, or sold many times over. The buyer often discovers the problem at the door, when the code has already been scanned by someone else.
Fake tickets circulate on resale sites, social media, and messaging groups. The seller may sound helpful, send a screenshot, and insist the code is genuine.
Red flags to check before you scan
- The seller refuses to transfer the ticket through the official ticket app or box office.
- The ticket is a screenshot or photo rather than a transfer inside the official system.
- The price is far below the face value for a sold-out event, or the seller pushes for instant payment.
- The ticket details, such as the event name, date, seat, or barcode format, do not match the venue official format.
- The seller insists on payment methods with no buyer protection.
Verify before you trust it
1. Buy through the official box office or an authorised resale partner whenever possible.
2. Ask the seller to transfer the ticket inside the official app, and confirm it appears in your account.
3. Check the event name, date, venue, and seat against the venue official listing.
4. Treat screenshots and forwarded images as unproven, however convincing they look.
Putting this into practice
Build a habit you can use in seconds. Pause before every unexpected scan, read the destination preview, and check the domain against what you already know. If the code is printed in public, look for sticker edges and compare it with nearby signs. If the code arrived in a message, verify it through a separate channel you trust. The pause costs almost nothing, and it is the step that catches most of these scams.
Common mistakes to avoid
The most common mistake is scanning to find out whether a code is safe. A scan that opens a page can already expose you to a fake login or a payment trap. Another mistake is trusting a familiar logo, since logos are easy to copy. A third is acting under urgency, which is exactly what the message is designed to create. Slow down, verify through a channel you control, and treat any request for credentials or payment as a reason to stop.
Quick checklist
- Pause before you scan any unexpected code.
- Read the full destination preview, not just the first hop.
- Compare the domain with the official one you already know.
- Check printed codes for sticker edges and mismatched print.
- Never enter passwords, codes, or card details from a surprise scan.
- Verify through a separate, trusted channel before you act.
Related tools and guides
- Run the destination through the [QR redirect chain viewer](/qr-redirect-chain-viewer) before you trust a code you did not expect.
- Inspect the code with the [QR scan log](/qr-scan-log) before you trust a code you did not expect.
- Check the address with the [QR typosquat checker](/qr-typosquat-checker) before you trust a code you did not expect.
- Practise spotting patterns with the [bulk generator](/bulk-generator) before you trust a code you did not expect.
- Review the chain with the [QR placement guide](/qr-placement-guide) before you trust a code you did not expect.
- Keep a record with the [QR safety checker](/qr-safety-checker) before you trust a code you did not expect.
- Plan protection with the [QR size calculator](/qr-size-calculator) before you trust a code you did not expect.
