Exposed in this breach? Do this now
Change the password
On the breached site and everywhere else you reused it. Make every password unique.
Enable 2FA
A second factor keeps a leaked password from becoming a hijacked account.
Set up monitoring
and get notified the moment your data appears in a new leak.
Ticketiq breach: questions and answers
When did the Ticketiq data breach happen?
The Ticketiq breach dates to March 2016.
How many records were leaked in the Ticketiq breach?
LeakCheck has indexed 1,186 records from the Ticketiq breach.
What data was exposed in the Ticketiq breach?
The leaked records include email addresses, physical addresses and IP addresses.
Were passwords exposed in the Ticketiq breach?
No. The records indexed from Ticketiq do not include passwords — but the other details they hold can still be used for phishing.
How do I check if my data was in the Ticketiq breach?
Enter your email address, username or phone number in the search form on this page. The free check shows whether your data appears in the Ticketiq breach — and in any of the other 1,469 sources LeakCheck indexes.
What should I do if my data was in the Ticketiq breach?
Change the password you used on Ticketiq and everywhere you reused it, turn on two-factor authentication, and watch for phishing that quotes details from the leak. To hear about the next breach first, set up breach monitoring.