Limeleads.com data breach

9,020,262 records Breach date: August 2019 no passwords

Exposed data

Email addressesPhone numbersGeographic locations

In August 2019, Limeleads.com suffered a data breach. The dataset indexed by LeakCheck contains 9,020,262 records.

The leaked records include email addresses, phone numbers and geographic locations.

The indexed records do not include passwords, but the details they hold can still be used for phishing. Run a free check below to see whether you are affected.

Check if your account is affected

Enter your email, username or phone number — the check is free and confidential, and the result will tell you whether this breach mentions you.

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.

Limeleads.com breach: questions and answers

When did the Limeleads.com data breach happen?

The Limeleads.com breach dates to August 2019.

How many records were leaked in the Limeleads.com breach?

LeakCheck has indexed 9,020,262 records from the Limeleads.com breach.

What data was exposed in the Limeleads.com breach?

The leaked records include email addresses, phone numbers and geographic locations.

Were passwords exposed in the Limeleads.com breach?

No. The records indexed from Limeleads.com 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 Limeleads.com 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 Limeleads.com breach — and in any of the other 1,468 sources LeakCheck indexes.

What should I do if my data was in the Limeleads.com breach?

Change the password you used on Limeleads.com 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.