What was exposed, when it happened, and which databases confirm it.
- accounts
- 8,809,977
- Breached
- November 19, 2016
- Last Update
- November 3, 2017
Were you caught in this breach?
Search your email, phone number or username against every record CheckLeaked indexes.
What happened
In approximately November 2016, the search engine optimisation management company RankWatch exposed a Mongo DB with no password publicly whereupon their data was exfiltrated and posted to an online forum. The data contained 7.4 million unique email addresses along with names, employers, phone numbers and job titles in a table called "us_emails". When contacted and advised of the incident, RankWatch would not reveal the purpose of the data, where it had been acquired from and whether the data owners had consented to its collection. The forum which originally posted the data explained it as being "in the same vein as the modbsolutions leak", a large list of corporate data allegedly used for spam purposes.
Compromised Info
- Email addresses
- Employers
- Job titles
- Names
- Phone numbers
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
- HIBP
FAQ
What was leaked in the Rankwatch breach?
The Rankwatch breach exposed: Email addresses, Employers, Job titles, Names, and Phone numbers.
When did the Rankwatch breach happen?
The Rankwatch breach was disclosed on November 19, 2016 and affected 7,445,067 records.
Am I affected by the Rankwatch breach?
Search your email, phone or username at checkleaked.cc to find out whether your data appears in the Rankwatch leak.