Password Audit Bot

@passwordaudit_bot
FreeEN

A password-only breach checker that never sends your full password anywhere: it uses k-Anonymity (only a truncated SHA-1 hash prefix) against the Have I Been Pwned "Pwned Passwords" API, with open-source code so you can verify the claim yourself.

Key features

  • Checks a password against Have I Been Pwned's Pwned Passwords database
  • Uses k-Anonymity — only a 5-character SHA-1 hash prefix ever leaves your device
  • Open-source code lets you verify the privacy claims yourself
  • Rate limiting and input sanitization documented in the source

What Password Audit Bot does

Password Audit Bot answers a narrower but genuinely useful question than the email-checking bots elsewhere in this file: not "has my email leaked," but "has this exact password of mine already turned up in a known breach." Its source, published on GitHub by a developer/team using the handle CS-Era as "secure-password-auditor-bot," documents a /check command and describes precisely how it protects whatever you type: instead of sending the full password anywhere, it hashes it locally with SHA-1 and sends only the first five characters of that hash to the Have I Been Pwned "Pwned Passwords" API — the same k-Anonymity technique the official haveibeenpwned.com site itself uses, which makes it mathematically infeasible for the API to reconstruct your actual password from what it receives.

The README explicitly documents privacy-by-design and security-by-design practices: no persistence (passwords are stated to never be saved), rate limiting against brute-force and denial-of-service abuse, input sanitization, and mandatory HTTPS for all communication. Because the code is open source, none of this has to be taken purely on faith — anyone can read exactly what the bot does with what you send it.

The tradeoffs are typical of a small personal open-source project rather than a funded security company: no named individual developer beyond a GitHub organization handle, no formal privacy policy document, and a modest GitHub star count suggesting limited real-world usage so far. Treat it as a technically well-built tool rather than an established brand, and remember that even a clean result from any password checker does not replace using a unique, strong password on every account.

How to start

  1. Open @passwordaudit_bot in Telegram and send /start
  2. Send /check and follow the prompt to enter a password you actually use
  3. Read the strength and breach-check result
  4. Change that password if the bot reports it was found in a breach

Pricing and limits

Free

Pros / Cons

  • Technically sound privacy model — k-Anonymity means the full password is never transmitted
  • Open source, so the safety claims are independently verifiable
  • Free, no premium tier found
  • Small personal project — only a GitHub handle, no named individual or company
  • No formal privacy policy document, only the claims stated in the README
  • Modest usage signals: low GitHub star count, no independent press coverage found

Score breakdown

CriterionWeightPoints
Functionality256 / 10
Reliability & speed155 / 10
Popularity & trust153 / 10
Price & free tier1010 / 10
Usability107 / 10
Safety & privacy108 / 10
Freshness55 / 10
Localization53 / 10
No intrusive ads59 / 10
Score10060.0

How we rank

FAQ

Does this bot ever see my actual password in full?

According to its open-source code, no — it hashes the password locally and sends only the first five characters of the SHA-1 hash to the breach-checking API, the same k-Anonymity method haveibeenpwned.com itself uses.

Is this the same as pwned_robot or pwn3dbot in this file?

No — those two check an email address; this bot specifically checks a password, using a different hash-based technique designed so the full password never has to be sent anywhere.

Technical details

  • Inline mode
  • Mini App
  • Works in groups
  • Works in channels
  • Accepts voice
  • Accepts files
  • Requires phone number
  • Requires registration
  • Shows ads
  • Works in Russia without VPN

Updated September 7, 2026 · Report a problem