What was exposed, when it happened, and which databases confirm it.
- accounts
- 878,708,974
- Breached
- February 25, 2019
- Last Update
- March 9, 2019
Were you caught in this breach?
Search your email, phone number or username against every record CheckLeaked indexes.
What happened
In February 2019, the email address validation service verifications.io suffered a data breach. Discovered by Bob Diachenko and Vinny Troia, the breach was due to the data being stored in a MongoDB instance left publicly facing without a password and resulted in 763 million unique email addresses being exposed. Many records within the data also included additional personal attributes such as names, phone numbers, IP addresses, dates of birth and genders. No passwords were included in the data. The Verifications.io website went offline during the disclosure process, although an archived copy remains viewable.
Compromised Info
- Dates of birth
- Email addresses
- Employers
- Genders
- Geographic locations
- IP addresses
- Job titles
- Names
- Phone numbers
- Physical addresses
Attestation
Four independent databases catalog this breach and they do not always agree. Each lane below is one source’s own count.
Sources & Link Methods
- LeakCheck— linked via automatic string matching
- HIBP
FAQ
What was leaked in the VerificationsIO breach?
The VerificationsIO breach exposed: Dates of birth, Email addresses, Employers, Genders, Geographic locations, IP addresses, Job titles, Names, Phone numbers, and Physical addresses.
When did the VerificationsIO breach happen?
The VerificationsIO breach was disclosed on February 25, 2019 and affected 763,117,241 records.
Am I affected by the VerificationsIO breach?
Search your email, phone or username at checkleaked.cc to find out whether your data appears in the VerificationsIO leak.