Breach Monitor
Which of your addresses are in a breach?
Ask Have I Been Pwned which of your addresses are in a breach, on a schedule, and hear the day a new one is — with the addresses and the data classes exposed.
Free while in beta
In beta: open to invited organisations and not billed yet. Write to us and we add yours.
What it does
- Domain-wide search, every mailbox
- New exposures the day they are published
- Data classes per breach (passwords, phone numbers…)
- Notifications to the affected people or to security
How this tool bills
Today's list prices in EUR, read from the qzila price list when this page was built. You are billed monthly for what you used.
In beta: open to invited organisations and not billed yet. Write to us and we add yours.
The API
Every qzila tool is a GraphQL API first; the web UI is one client of it. Anything you can do in the browser you can do from a script, a CI job or the Asign platform.
https://breaches.tools.qzila.com/graphqlPOST · application/json · { "query": "…" }
Requests are authenticated with your qzila session (the same sign-in as the browser). For automation, sign in once at identity.qzila.com and reuse the session cookie; API keys for service accounts are on the roadmap.
Whatever this tool detects — a verdict flip, a regression, a change, an incident — is emitted as a signal to the qzila alert hub, which forwards it to email, Slack, a webhook or Jira, and to Service Watch, which can also send it as an SMS. Each signal carries the asset it belongs to, so you can correlate it back to your own inventory (or to an Asign asset).
Main operations
upsertMonitormutationWatch an email domain for breached addresses on a schedule.
mutation { upsertMonitor(input: { domain: "example.com", schedule: DAILY }) { id } }findingsqueryExposures: which address, which breach, which data classes.
query { findings(monitorId: "m_1") { email breach dataClasses addedAt } }acknowledgeExposuremutationMark an exposure reviewed.
mutation { acknowledgeExposure(id: "e_7") { reviewed } }
Send requests to https://breaches.tools.qzila.com/graphql
Questions about Breach Monitor
Where does the breach data come from?
From public and vetted breach corpora, updated as new dumps are verified. We store only which of your addresses appeared where — never the passwords themselves.
Do I need to list every address?
No. You register the email domain and every address on it that appears in a breach is reported, including ones you did not know existed.
What should I do with a finding?
Reset the password on the affected accounts, enforce MFA, and mark the exposure reviewed so the history shows who handled it and when.
Where do alerts go?
Every tool reports through one alert hub. You choose per destination: email, Slack, a webhook, SMS or a Jira ticket — and Service Watch shows the same signals on one board.
Where is my data kept?
The tools run on AWS in the EU (Frankfurt), operated by adcore s.r.o., a Slovak company. A few services they rely on sit outside the EU — Stripe for card payments, Google for analytics after your consent, the threat-intelligence lookups behind Safe Check — and the privacy policy lists each one.
Start with one tool. Add more when you need them.
In beta: open to invited organisations and not billed yet. Write to us and we add yours.