Have I Been Pwned compared with DeHashed and Mozilla Monitor| Have I Been Pwned | DeHashed | Mozilla Monitor (now Mozilla Monitor) |
|---|
| Function and data source: Checks email addresses and phone numbers against known breaches, and offers domain search for verified domains and the Pwned Passwords service. | Function and data source: A personal asset search engine over data posted on the clear and deep web, with lookups for usernames, emails and IP addresses. It returns the exposed data itself, as well as notifying about breaches. | Function and data source: The service was renamed Mozilla Monitor. It scans for exposure of an email address, and Mozilla states that its breach data comes from Have I Been Pwned. |
| API and automation: Breached account, paste, domain and stealer log queries need a 32-character API key sent in the hibp-api-key header. Pwned Passwords needs no key and uses k-anonymity: only the first 5 characters of a SHA-1 hash are sent. | API and automation: An API is offered for programmatic breach-data queries. Its pricing page does not state whether API access is part of a plan. | |
| 成本模型: API tiers are Core, Pro and High RPM, and stealer log queries require Pro or higher. Prices are on the pricing page, which could not be read here. | 成本模型: Paid plans are listed for 7 days, one month and one year, with unlimited asset searches in each plan. | 成本模型: Described as free. A public breach search works without an account, while future alerts and the detailed report need a Mozilla account. |
| Licence and verification: The breach and paste APIs are under CC BY 4.0, which requires crediting Have I Been Pwned with a link. Domain search requires proving control by a DNS TXT record or an approval email to one of five aliases (admin, hostmaster, info, security, webmaster). | | Licence and verification: Users can opt an email out of the underlying Have I Been Pwned database through its opt-out page. |