General
56 results found
-
API access: Recurring yearly payment
This would help us alot as a company. Doing monthly bill mapping with a corporate creditcard is not working for us :-)
This is coming soon! Announcement and details here: https://www.troyhunt.com/expanding-and-enhancing-the-have-i-been-pwned-api/
385 votesThis is now complete! Read all about it here: https://www.troyhunt.com/the-have-i-been-pwned-api-now-has-different-rate-limits-and-annual-billing/
-
Search by phone number
It would be neat if you could test for pwned accounts searching by phone number. Some utility companies know my phone number but not my email.
280 votesHere’s the background on what’s been done: https://www.troyhunt.com/the-facebook-phone-numbers-are-now-searchable-in-have-i-been-pwned/
-
Add domain search capability to the API functions
I've been subscribing to the alerts for breaches related to our corporate domain, which is fantastic, but now that we have Splunk in house, I was hoping to connect directly to the API from a forwarder.
269 votesIt's now live! Thank you all for supporting this idea, enjoy: https://www.troyhunt.com/welcome-to-the-new-have-i-been-pwned-domain-search-subscription-service/
-
Create different pricing for different rate limits
Right now there is a 1.5-second delay time b/w request, which is a long delay wait-time for us.
Currently, we have to thread multiple API keys together to decrease the rate limit, though we'd rather only have to use one and pay a bit extra.
It would be very helpful if we could pay extra to have a lower rate limit (e.g. think tiers for rate limits maybe?)This is coming soon! Announcement and details here: https://www.troyhunt.com/expanding-and-enhancing-the-have-i-been-pwned-api/
119 votesThis is now complete! Read all about it here: https://www.troyhunt.com/the-have-i-been-pwned-api-now-has-different-rate-limits-and-annual-billing/
-
Add a link to the site explaining what to do when you are a victim of data breach.
My email address poped up as being part of a breach. What are the next steps?
* void the respective accounts?
* Just change the password?
* Other options?It would be nice just to have a link to some mitigation actions for present and also for the future.
Thanks for the effort put on this site
97 votesI’ve just implemented this by virtue of the 1Password partnership blogged about here: https://www.troyhunt.com/have-i-been-pwned-is-now-partnering-with-1password/
-
Allow users to remove entries associated with their email address from the database
Or give folks the option to hide their own results from the larger public. As currently configured, the site makes information that is otherwise only available on the darkweb (e.g., saliently, that you were an AdultFriendFinder user) readily accessible to anybody with an internet connection.
This would only really make sense for pwned email addresses, since there would be no easy way to prove you are the owner of a given account otherwise.
64 votes -
51 votes
This is now done! Both the top 10 biggest and the 10 newest are now on the front page.
-
Add support for NTLM(MD4) hashes to enable Active Directory auditing
I wanted to use the list to check existing Active Directory (AD) passwords against this wonderful HIBP list, but the problem is that neither the API nor the offline list support MD4 hashes (AKA NT one-way function or NTLM hash) that are stored in AD databases (together with salted SHA1 and MD5, which therefore cannot be precomputed).
Would it please be possible to also add support for this (weaker) type of hashes? It would be great to have them available at least through the API and ideally also in a downloadable form.
30 votesThis was completed last year, I just forgot to update the status!
More here: https://www.troyhunt.com/pwned-passwords-now-as-ntlm-hashes/
-
Add search passwords by a hash value
Let users use pre-generated hash values to search. Yeah, I know you calculate hashes of typed passwords on a client side, but some people still prefer not to type their password on 3rd party sites.
25 votesWell and truly done an available here: https://haveibeenpwned.com/Passwords
Docs for k-anonymity: https://haveibeenpwned.com/API/v3#PwnedPasswords
-
Include email address in email correspondance when registering
I have registered several email addresses that I own and that results in a registration email and summary page for each one.
It's not possible to see in the email body, or on the summary page, which email address they belong to. This is especially tricky with my Exchange inbox which has several email aliases.
13 votesGood suggestion, done!
-
Enable a web hook for a callback when an account I'm monitoring is pwned
At present, notifications can be set up for when an individual address is pwned or when an address on a domain someone is monitoring is pwned. This idea is to programatically enable calling an HTTP endpoint when this event occurs.
The benefit of this idea is that developers can then implement their own logic which is automatically invoked when an event like this occurs. It's of most value to those monitoring domains where notifications are no a rare occurrence, particularly when we're talking about larger domains.
12 votesThis is now complete and is documented here: http://www.troyhunt.com/2015/07/have-i-been-pwned-goes-little-bit.html
-
Add breaches that may be hoaxes, but make it clear!
Often there are "breaches" which turn out to be hoaxes. On the one hand, having only verified breaches in the system is important in terms of confidence in the data but on the other hand, people still want to know if their email address is circulating in a hoax breach.
This feature would need to indicate that the breach has not been verified and may be a hoax. It's also important that it wouldn't just automatically appear in results returned by the API, rather it could be requested by passing a parameter to the API such as "IncludeUnverifiedBreaches=true" where the…
9 votes -
Explicitly state the email address that the notification is referring to.
If you're forwarding emails from a bunch of other addresses it can be awkward to work out which address is involved in the breach. Explicitly stating the email address in the notification would make this easier.
8 votesThis has now been completed and will be included in all future breach notiifcations
-
Add more leak source
Add more leak source :
- https://twitter.com/pwnagemon
- https://twitter.com/d2dedwad26 votesJust added these to the list HIBP consumes from: https://twitter.com/haveibeenpwned/lists/paste-sources
Lot of redundancy with existing sources, but provides some resiliency if one of them is down. Thanks!
-
Create a Mastodon account
Given the exodus of accounts from Twitter to Mastodon, as well as its close relationship to the open-source and information security communities, I think you should create a Mastodon account and have it basically, at the very least, reflect what your Twitter account is saying - which is relatively easy to do via tools such as this: https://moa.party/
3 votesDone! I'd previously tried to reach out to @haveibeenpwned@mstdn.social and ask them to hand over the account but got no response. I've just set up @haveibeenpwned@infosec.exchange instead and verified it as the owner of the domain. I'm not sure how I'll actually use it yet (only a very tiny portion of the audience is there), but at least it now has a presence.
-
Use javascript front-end that converts password to hash on client before sending across web
To mitigate the risk of sending passwords as straight text over the web to your site, could you not have client-side javascript that converts the password to the SHA1 hash and send the hash to be checked?
3 votesThe pwned passwords page already does this.
-
Fix Table of Response Codes within API v3 Documentation
Can you please insert the following into https://haveibeenpwned.com/API/v3#ResponseCodes
- 503 "Service Unavailable" from https://haveibeenpwned.com/API/v3#RateLimiting
- 401 "Unauthorized" from https://haveibeenpwned.com/API/v3#Authorisation3 votesGood points, now implemented in source and will be pushed out publicly soon
-
Opt-in / Change opt-out type
It would be great to add opt-in / change opt-out type after user opted-out. For example, I started using 1password, so I would like to switch from "visible just to me" to "delete all previous breaches" so that I can get notification in 1password, resolve it and then "delete all breaches" again.
3 votesYou can already do this, just opt out again.
-
Fix "Pwned Passwords" Two APIs Sentence in Documentation
Please remove "It's also queryable via the following two APIs:" from https://haveibeenpwned.com/API/v3#PwnedPasswords please as the first API is deprecated?
3 votesFixed in source and will go out with the next release
-
update the breached password list download again
I noticed you stopped updating the download for breached passwords. I would like to continue to have an up to date data set to prevent users form choosing breached passwords but I will not use the API.
I don't want the availability of something like registering for an account to be tied to an external service, nor do I want to slow the process down by waiting on an external API.I just want an up to date list to check locally and decide to accept or reject the password my user is trying to choose.
3 votesThis is actually already done, I'll be blogging about it in the coming week: https://www.nuget.org/packages/haveibeenpwned-downloader/
- Don't see your idea?