Data breaches → Verifications.io
Was your data in the Verifications.io breach?
2019 · verifications.io · ~763,117,241 accounts exposedCritical severity · 10/10
Verifications.io (verifications.io) suffered a data breach in 2019 that exposed around 763,117,241 accounts. If you had an account, some of your personal data may be circulating in leaked databases. The fastest way to know is to check your own email — free, in about 30 seconds, no password required.
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.
Breach details sourced from Have I Been Pwned, the industry-standard breach database. Risk analysis by Nullivo.
What was exposed, and why it matters
Not all breaches carry the same risk — what matters is which fields leaked. Here is what the Verifications.io breach exposed and what each item actually enables:
Home addresses feed people-search and data-broker sites, which republish them publicly. They also make phishing far more convincing and, in the worst cases, enable real-world harassment.
Date of birth is a permanent identifier used to verify identity by phone. Combined with a name and address it is often enough to impersonate you.
Enables SIM-swap attacks (hijacking your number to intercept SMS codes), smishing, and voice scams that appear to come from your bank.
Reveals where you live, work or travel, which supports both targeted scams and physical-safety risks.
Links this leak to your other accounts — a reused username lets anyone build a profile of you across platforms.
Puts you on spam and phishing lists, and confirms to attackers that you hold an account with this service — which makes impersonation emails more believable.
Reveals your approximate location and internet provider, which adds credibility to targeted scams.
Also listed in this breach: Dates of birth, Email addresses, Employers, Genders, Geographic locations, IP addresses, Job titles, Names, Phone numbers, Physical addresses.
What to do if you were affected
These steps are ordered for this specific breach — the most urgent action given what leaked comes first.
- Home addresses: Get your address removed from data brokers — they re-list roughly every four months, so this needs repeating.
- Dates of birth: Never confirm your date of birth to an inbound caller — hang up and dial the organisation back on a published number.
- Phone numbers: Move two-factor authentication off SMS to an authenticator app or passkey, and add a port-out PIN with your mobile provider.
- Location data: Review location sharing on the accounts you still hold with this service.
- Names and usernames: Search your usual username to see what else it exposes, and use distinct handles for sensitive accounts.
- Check whether your own email appears in this breach — run a free scan to confirm before you spend time on the steps above.
This breach put your details on data-broker sites
Because Verifications.io exposed home addresses, this is one of the breaches that feeds people-search and data-broker sites. Those sites scrape leaked databases, combine them with public records, and republish the result as a searchable profile — which is how a single breach turns into a permanent public listing. Removal works, but brokers typically re-list within about four months, so it has to be repeated.
See our broker-by-broker removal guides →
How urgent is this now?
This breach is over 7 years old. Old credentials still cause harm — leaked passwords from a decade ago are still tried against new accounts every day.
Remember: a breach can't be "un-leaked" — once a database is out, it exists in countless copies. The goal is to make the leaked data useless: change what can be changed, lock down what can't, and remove what has been republished.
Frequently asked questions
What data was exposed in the Verifications.io breach?
The Verifications.io breach exposed home addresses, dates of birth, phone numbers, location data, names and usernames, email addresses, ip addresses. Home addresses feed people-search and data-broker sites, which republish them publicly. They also make phishing far more convincing and, in the worst cases, enable real-world harassment.
How many people were affected by the Verifications.io breach?
Around 763,117,241 accounts were exposed, making it one of the largest breaches ever recorded.
What should I do if I had a Verifications.io account?
Get your address removed from data brokers — they re-list roughly every four months, so this needs repeating. You can check whether your own email appears in this breach with a free Nullivo scan — no password required.
Breaches that exposed similar data
If the Verifications.io breach affected you, these breaches exposed comparable information — worth checking too, since leaked datasets are routinely combined.
- Was your data in the Modern Business Solutions breach? (2016, ~58,843,488 accounts)
- Was your data in the Master Deeds breach? (2017, ~2,257,930 accounts)
- Was your data in the Facebook breach? (2019, ~509,458,528 accounts)
- Was your data in the Betterment breach? (2026, ~1,435,174 accounts)
- Was your data in the Exactis breach? (2018, ~131,577,763 accounts)
- Was your data in the Data & Leads breach? (2018, ~44,320,330 accounts)