Customer account protection
See which of your customers' logins have leaked.
Stealer logs and password lists are full of logins for sites like yours, saved by your own customers. We find the ones for your site, so you can reset them before they're used to take over accounts.
The free customer report for acme-shop.com: 1,874 leaked logins for accounts on the site, 612 of them from customers' infected devices, with a sample showing only each login's email provider and the page it was saved on.
Open the full exampleCustomer account report
Acme Shop
1,874
leaked logins for accounts on acme-shop.com.
612
from customers' infected devices
1,262
from leaked password lists
203
posted in the last 90 days
How customer accounts get taken over
- 01A customer's login leaks
Malware on their laptop copies every password saved in the browser, or another site they use gets breached. Either way, the login they use for your site goes with it.
- 02It's posted and sold
The login ends up in a stealer log or a password list, traded on Telegram channels and dark-web markets, often within days.
- 03Someone tries it on your sign-in page
Bots run these lists against sign-in pages in bulk. Every login that still works is an account they can open.
- 04The cost lands on you
Drained gift cards and loyalty points, orders shipped to new addresses, chargebacks and support tickets. The customer rarely knows the leak started on their own device.
None of this needs a flaw in your site. The leak happened on the customer's side, so the place to catch it is the lists themselves. We search 44 billion stealer-log records and leaked password lists for logins saved on yours.
What the free check shows
Leaked logins for your site
The exact number of logins saved for your domain and its subdomains, from stealer logs and leaked password lists.
From infected devices
How many came straight off customers' computers. These often include the session cookie, which can get past a password and MFA.
Where they were saved
The page each login was typed into: sign-in, sign-up, checkout, account settings or password reset.
What customers sign in with
The email providers behind the logins, like Gmail or Outlook, and how many sign in with a username instead.
When they were posted
Twelve months of postings, and how recently the newest one appeared.
Your staff, set aside
Logins on your staff's own pages, like email or single sign-on, are counted separately, with a link to the employee report.
Free check or full list
| Feature | Free check | With a plan |
|---|---|---|
| Exact number of leaked logins for your site | Yes | Yes |
| The page each one was saved on | Yes | Yes |
| Email providers, with the rest of the address hidden | Yes | Yes |
| Every login, with the full email address and password | No | Yes |
| How many customer devices hold a session cookie for your site | No | Yes |
| Alerts when new ones are posted | No | Yes |
| CSV export and API | No | Yes |
| Device details and cookie alerts by webhook, on Growth and Enterprise | No | Yes |
Plans start at $82 a month billed yearly, or $99 billed monthly, with a data processing agreement and unlimited seats included. See pricing.
What to do with a leaked login
Check the leaked password against the one on the account. Your site already does this at every sign-in, so it's a small job for your developers. Where it still matches, reset the password and sign the account out everywhere.
For logins from stealer logs, end the customer's sessions too, because the cookie that keeps them signed in was taken with the password. Then tell them their device may be infected: a new password won't stay private for long while the malware is still there.
Questions
Is the check really free?
Yes. It costs nothing and you don't need an account. It shows a summary of what we hold for your site, with every customer's identity hidden, so you can decide whether the full list is worth paying for.
Do I have to run the site?
No, you can check any website. That's why the free report only shows counts, pages and email providers. The full list, with email addresses and passwords, only goes to the company that runs the site, after it proves it owns the domain.
How is this different from BreachDetect for staff?
The staff product starts from your email domain: every leaked login for an @yourcompany.com address, wherever it leaked. Customer Protection starts from your website: every login saved for it, whoever it belongs to. Most companies with a customer sign-in page need both, and the free customer report links to the staff one.
Do you need access to our user database?
No. We find leaked logins by your website's address. You compare them with your own accounts on your side, so your customer records never leave your systems.
What can we do with our customers' leaked passwords?
Use them to protect those accounts and nothing else: check whether each one still works on your site, reset the accounts where it does, then delete it. Every plan comes with a data processing agreement that says so.
What do plans show about session cookies and devices?
Every plan counts the customer devices that hold a session cookie for your site. A stolen session cookie gets past the password and two-factor authentication, so those are the accounts to sign out first. On Growth and Enterprise you can open each affected customer's infected device to see what else was saved on it, and get an alert by webhook when new cookies for your site turn up.
Is my search private?
We store each website's result for 24 hours so that checking it again doesn't run a new search. Anyone who checks the same site in that time sees the same summary. Our website analytics also record which site was checked.
How current is the data?
New stealer logs and password lists are added every day. A result is reused for up to 24 hours, and after that a check runs a fresh search.
