Breach data
What's actually behind the breach check.
Every analysis on Augis runs against an aggregated breach index automatically, at no extra cost. Here's what that means in practice.
Forum dump · 2019
Online shop · 2021
Mobile operator · 2025
Illustrative example with sample values. Passwords, hashes and tokens are never shown.
Reading a result
What a breach result does, and does not, tell you.
A match
A record in the index is tied to the identifier you analyzed. It shows what leaked, and from which service.
A clean result
Nothing indexed was found. That is not a guarantee the identifier is safe, only that nothing has surfaced yet.
Linked identifiers
Phone numbers, secondary emails and usernames found alongside a match can be followed up in their own analysis.
Uneven coverage
A widely reused email will usually have more hits than a niche username. Coverage varies a lot by identifier.
Where the data comes from
Augis's breach index is powered by a third-party aggregator that indexes data from publicly circulated breach dumps, leak forums, and previously compromised services. It isn't a single source, it's a combined index built from thousands of individual incidents collected over time.
We don't run our own scraping or hacking operations. Augis is an aggregation layer on top of data that has already leaked and is already circulating, indexed and made queryable in one place instead of scattered across forums and archives.
What an analysis actually checks
Every regular analysis (1 credit) does two things at once: it checks the breach index for that identifier, and it runs the relevant public-source sweep for that identifier type (the 600+ site username sweep for a username, WHOIS/DNS for a domain, and so on). Both are included, there's no separate fee for the breach half.
What kind of data typically shows up
Credentials
Emails paired with password hashes or, in older/lower-quality dumps, plaintext passwords.
Contact info
Phone numbers, secondary emails, usernames tied to the identifier you analyzed.
Account metadata
Which service the record came from, and sometimes registration dates or IP addresses logged at signup.
Personal details
Occasionally full names, addresses, or dates of birth, when the source breach included them.
Coverage varies a lot by identifier. A widely reused email will usually have more hits than a niche username, and not every analysis returns a match, a clean result means nothing indexed was found, not that the identifier is guaranteed safe.
Freshness and coverage
The index grows as new breaches surface and get indexed by that aggregator, it's not a fixed, one-time snapshot. That said, there's inherent lag between when a breach actually happens and when it's publicly circulating and gets indexed, so a very recent incident may not show up immediately.
Use it responsibly
Breach data is exposed personal information, treat it that way. Augis is built for legitimate use: checking your own exposure, due diligence, authorized investigations, and research. Using it to harass, stalk, or target someone is against our terms, and in most places, against the law.
Questions
Does Augis run its own collection?
No. Augis runs no scraping or hacking operations of its own. It queries an aggregated index of data that has already leaked and is already circulating.
How fresh is the index?
It grows as new breaches surface and are indexed, but there is lag between a breach happening and it showing up. It is not real-time.
Can I keep a breach check private?
Yes. Run the analysis in incognito and nothing is written to your history.
Keep exploring
Run your first analysis
Every plan includes the breach check on every analysis, no extra step.
Get Started