About
Breach intelligence, without becoming another place your data sits.
Compromised checks whether an identifier you control appears in known breach data, and shows what was exposed. It is a point-in-time check, not monitoring, and it says so.
What the product is for
Credentials and personal details leak constantly, and most people find out long after it matters — if at all. The useful question is narrow and answerable: has this specific identifier appeared in breach data, and what kind of data went with it.
That is the question Compromised answers. It searches an email address, a username, a name or an IP address against breach intelligence, normalizes what comes back into breach names, dates, severity and data categories, and keeps the history private to the account that ran it.
It deliberately does not do more. There is no continuous monitoring, no credential reveal, no scoring of how “at risk” somebody is. Those either require holding far more data than the question needs, or they manufacture a confidence the underlying data does not support.
How it is built
Searching for exposure should not create more of it.
Collect less
The searchable index over your history is a keyed hash, not the value itself. Search values and resolved IP addresses are encrypted before a record exists. Nothing sensitive reaches application logs, analytics or webhooks.
Decide on the server
What a response contains is filtered by entitlement before it is sent. The browser is never asked to hide a field it received, because a field the browser received is a field the reader has.
State the limits
A zero result is reported as what it is — one provider, at one moment. Partial responses are labelled. The product does not present an absence of evidence as evidence of absence.
Offer only what works
Identifier types that returned nothing in practice are disabled rather than displayed as features that quietly never work. The supported list is short because it is the list that has been verified.
Who is behind it
Compromised is built and operated by Cengiz YILMAZ, who works in Microsoft identity and messaging infrastructure.
Questions about the product, its data handling or a specific account go through the contact page and reach a monitored mailbox.