Point-in-time breach intelligence
Know where your identity has been exposed.
Check an email address, username, name or IP against breach intelligence. See which breaches involved it and what categories of data were exposed — without the product pretending a clean result is a guarantee.
- Encrypted before storage
- Server-enforced access
- Nine identifier types
Two checks, one page
A point-in-time query. Nothing here is continuous monitoring.
What you can check
Start with the identifier you already know.
Nine identifier types in total, from contact details to document and vehicle numbers.
Username
yourhandle
Reused handles link accounts across unrelated services.
Full name
Jane Doe
Broader matches; expect more noise than an exact identifier.
IP address
203.0.113.42
IPv4 and IPv6, against records carrying network data.
Privacy and security
Searching for exposure should not create more of it.
Every control below is implemented, not aspirational. The security page names each one and where it applies.
Encrypted at rest
Search values and resolved client IPs are sealed with AES-256-GCM before a history record exists.
Searchable without storing the value
Exact-match lookup runs over keyed hashes, so the index never contains the identifier itself.
Reveal is a deliberate act
History listings never decrypt. Seeing your own stored value requires an explicit, audited action.
The server decides what you see
Response fields are filtered by entitlement on the server. The browser is never trusted to hide anything.
Questions
The answers people actually ask for.
What does Compromised search?
Email addresses, usernames, full names, phone numbers, IPv4 or IPv6 addresses, government ID, driver's licence, vehicle identification numbers and licence plates. Passwords are checked separately and never leave your browser. Social security numbers are not searchable. Coverage varies by identifier type: the provider holds far more data about some than others, so a zero result on a less common type says less than a zero on an email address.
Does a zero result mean I am safe?
No. A zero means the configured provider reported no match at that moment. Provider coverage changes, some responses are partial and labelled as such, and no breach service can prove an identifier has never been exposed.
How are searches counted?
One search is reserved before the provider is called, so two simultaneous requests can never spend the same slot. If the provider fails, the reserved search is returned to the pool it came from — you are not charged for a search that produced no answer.
What happens when my monthly searches run out?
Your recurring allowance is always spent first. Once it is exhausted, purchased credits are used. If you have neither, the search is refused before the provider is called rather than being run and billed afterwards.
What is included in Pro?
A recurring monthly search allowance, normalized breach detail rather than counts alone, and an explicit, audited reveal of your own stored query value. The exact allowance and capabilities of each plan are shown on the pricing page, which reads them from the live plan catalog rather than from fixed copy.
How does annual billing work?
You are charged once a year, and the search allowance still resets every month. Billing frequency and allowance period are deliberately separate concepts in the system: an annual plan is not a year's worth of searches to spend at once.
How is my data protected?
Search values and resolved client IP addresses are encrypted with AES-256-GCM before any history record exists. Exact-match lookup runs over keyed hashes, so the searchable index never contains the identifier itself. Response fields are filtered by entitlement on the server — the browser is never trusted to hide anything.
Check an identifier now.
One search tells you what the provider currently holds. Your account keeps the history private and encrypted. No continuous monitoring, no credential reveal, no result treated as a guarantee.