For developersPublished
BreachDirectory API: What It Is, Security Uses, and Privacy Risks
Our existing guide explores breach lookup APIs, defensive security workflows, and the privacy questions organizations should consider.
Read guide ↗The BreachDirectory learning hub
BreachDirectory guides: Your data has
a history.
Understand it.
Make sense of breach exposure. Explore BreachDirectory, understand what results mean, and find a clearer path to protecting your accounts.
Understand the signal
Exposure literacy
A match needs context.
An email in a breach dataset is a reason to review security. It does not, by itself, establish current account compromise.
Understand exposure.
Choose your next step.
Choose your next step.
01Learn the basics02Interpret your results03Protect your accounts04Explore the API
Start here · Published
The foundation for this guide collection.
BreachDirectory API: What It Is, Security Uses, and Privacy Risks
Our existing guide explores breach lookup APIs, defensive security workflows, and the privacy questions organizations should consider.
Read the complete article ↗Build your understanding
One topic. Clearer answers.
Explore BreachDirectory guides, from your first lookup to technical integration.
ComparisonsPublished
BreachDirectory vs. Have I Been Pwned
Compare documented searches, privacy practices, password checks, and what still needs verification before choosing BreachDirectory or Have I Been Pwned.
Read guide ↗Safety & recoveryPublished
Is BreachDirectory safe?
Understand what to check before sharing information, how to read privacy claims, and what breach results actually mean.
Read guide ↗Safety & recoveryPublished
Found your email? What to do next
Understand a breach match, prioritize affected accounts, and review passwords, sessions, recovery settings, and authentication.
Read guide ↗Getting startedPublished
How to use BreachDirectory
Follow a beginner-friendly workflow for choosing an identifier, submitting a search, and interpreting the response without overstating what it proves.
Read guide ↗Getting startedPublished
BreachDirectory results explained
Understand what matched identifiers, source labels, dates, password-related information, and counts can—and cannot—tell you.
Read guide ↗Getting startedPublished
No results: does that mean you are safe?
Learn what a completed negative search establishes, how to recognize an unknown outcome, and which account-security checks still matter.
Read guide ↗ComparisonsPublished
Why breach checkers show different results
Compare coverage, identifiers, timing, disclosure rules, and result counts before deciding why two breach checkers disagree.
Read guide ↗For developersPublished
BreachDirectory not working?
Separate website problems, incomplete searches, API errors, and CORS issues while keeping failed lookups distinct from negative results.
Read guide ↗ComparisonsPublished
BreachDirectory alternatives
Choose between email exposure checks, alerts, saved-password reviews, and business monitoring by purpose, privacy, and documented scope.
Read guide ↗Safety & recoveryPublished
Can you remove your information?
Understand deletion-request scope, confirm the current process, and separate lookup removal from securing affected accounts.
Read guide ↗For developersPublished
A privacy-conscious API tutorial
Build and test a synthetic-data checker with limited outputs and explicit failure states, then plan a verified server-side provider adapter.
Read guide ↗For developersPublished
BreachDirectory for small businesses
Assign ownership, review employee-email exposure alongside account evidence, and take proportionate action without spreading sensitive findings.
Read guide ↗13 guides shown
From information to action
Found a match?
Start with your account security.
Use the result as context for a security review. Avoid posting sensitive breach details or passwords in public.
- 01Review the source and age of the exposure.
- 02Replace any exposed or reused passwords.
- 03Enable stronger authentication where available.
- 04Review recent sign-ins and account recovery settings.
A few questions, answered.
Is ACyberSec the official BreachDirectory website?
No. This is an independent educational collection from ACyberSec. It is not operated by or affiliated with BreachDirectory.
Can I check my email address on this page?
This page is a reading hub. It does not perform breach searches, collect email addresses, or connect to a breach lookup API.
Which guide can I read right now?
The BreachDirectory API overview, the BreachDirectory vs. Have I Been Pwned comparison, Is BreachDirectory safe?, Found your email? What to do next, How to use BreachDirectory, BreachDirectory results explained, No results: does that mean you are safe?, Why breach checkers show different results, BreachDirectory not working?, BreachDirectory alternatives, Can you remove your information?, A privacy-conscious API tutorial, and BreachDirectory for small businesses are published. This hub lists the guides that are available now and will add more as they are published.
Why might different breach checkers give different answers?
Services can differ in dataset coverage, matching methods, update schedules, and disclosure rules. A missing result is not proof that information has never been exposed.
Independent educational content. Not affiliated with BreachDirectory. Practical cybersecurity. Clear explanations.