763.1M records in February 2019. Check whether your email is in this file — then read what was taken and what to do.
763.1M
Records exposed
2019
Year
10
Data types
Free
To check
Quick answer — was Verifications.io breached?
Yes. Verifications.io was breached in February 2019, exposing 763,117,241 records including dates of birth, email addresses, employers. This breach has been independently verified. If your email was involved, your data may still be at risk today. Check if you were affected.
What happened in the Verifications.io data breach?
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.
The exposed data included 10 types of personal information. Learn more about what a data breach means for you.
Why was the Verifications.io breach so dangerous?
The Verifications.io breach exposed 763,117,241 records — 763.1M people whose personal data is now circulating in criminal markets.
If you used Verifications.io, check whether your email was exposed in this breach.
What data was stolen in the Verifications.io breach?
Dates of birth — used to verify identity for account takeover and fraud
Email addresses — used for phishing attacks and credential stuffing against your other accounts
Employers — may be combined with other breach data to build a profile for targeted attacks
Genders — may be combined with other breach data to build a profile for targeted attacks
Geographic locations — may be combined with other breach data to build a profile for targeted attacks
IP addresses — combined with other data, used for identity theft and physical fraud
Job titles — may be combined with other breach data to build a profile for targeted attacks
Names — used to build profiles and target you with personalised scams
Phone numbers — enables SIM-swapping attacks and targeted SMS phishing
Physical addresses — combined with other data, used for identity theft and physical fraud
Is the Verifications.io breach still dangerous in 2026?
Yes. Stolen data from the Verifications.io breach remains dangerous years after the incident. Attackers routinely compile data from multiple breaches to build complete profiles, and credentials from 2019 are still actively used in automated attacks today.
Personal information like email addresses, phone numbers, and dates of birth does not expire. Even if you changed your Verifications.io password, the other exposed data can be combined with information from other breaches to target you. Learn how long stolen data stays dangerous.
What to do if your email was in the Verifications.io breach
1
Change your Verifications.io password immediately
Log into Verifications.io and change your password to something strong and unique — one you have never used anywhere else. A password manager after a breach can generate and store a unique password so you never reuse one.
2
Change any account sharing that password
If you reused this password elsewhere, walk the password-reuse change checklist. You can also check whether that password appears in known leaks without sending the password itself.
3
Enable two-factor authentication
Turn on 2FA or a passkey after a breach on Verifications.io and every important account. Even if your password is known, attackers cannot sign in without the second factor.
4
Check your other accounts for this breach
Run a full email scan to see every breach your address appears in — not just this one. Then follow the after-breach playbook. If a password from this incident is still in use, check it without sending the password itself.
Check all my breaches — free5
Shrink people-search listings if your name or address was exposed
A leaked email plus a public people-search page makes phishing more convincing. That is a separate job from changing passwords. See the data broker opt-out guide for official forms and, if you want help, removal services.
Frequently asked about the Verifications.io breach
How many people were affected by the Verifications.io data breach?
Approximately 763,117,241 user records were exposed in the Verifications.io breach in February 2019.
Is the Verifications.io breach still a risk in 2026?
Yes. Leaked credentials are actively used in credential-stuffing attacks years after a breach. If you reused your Verifications.io password elsewhere and have not changed it, those accounts remain at risk today.
How do I check if my email was in the Verifications.io breach?
Enter your email in the free checker on EmailLeaked. We scan millions of breach records including the Verifications.io dataset and tell you instantly whether your email was exposed and what data was taken.
What should I do if I was in the Verifications.io breach?
Change your Verifications.io password immediately, update any account where you used the same password, and enable two-factor authentication on all important accounts. Use a unique password for every account — a password manager makes this straightforward — and monitor for phishing emails over the next 90 days.
How this breach page is reviewed
Breach pages are built from structured breach records and reviewed for practical risk guidance by EmailLeaked. Risk labels reflect exposed data types and are intended to help readers prioritise action.
Other major breaches
Was your email in this breach?
Check if your email appeared in the Verifications.io breach and 1033+ other known breaches — free, instant, no signup.
Check my email — freeWas my email hacked?
Check if your email is compromised in seconds. Free, private, no signup. Scan millions of breach records across 1034+ known breaches.
Check my email now — it's freeNo signup required · Results in under 5 seconds · Your data is never stored