Skip to content

Search

  1. question here... are non-user data not exposed?  ·  declined

  2. Investigate this: Dear Alumni & Friends, Report of a Data Security Incident I am writing to notify you of a data security incident that ha  ·  declined

  3. Add Retry-After to Access-Control-Expose-Headers  ·  declined

  4. Provide a way for me to see the password data or other data associated with my email. Since I use unique passwords, the source is known.  ·  declined

  5. Add % of p0wn count already in DB as new field in API

  6. Put Resellers in their own data domain for Stripe  ·  completed

  7. Link Breach Lawsuits  ·  declined

  8. Add incremental updates to the PWNd password data sets  ·  declined

  9. Makes no sense why you wont give information concerning pending lawsuits or how to get things started  ·  declined

  10. If possible discover and add - https://www.dchealthlink.com/data-breach  ·  declined

  11. consider social security numbers?  ·  declined

  12. Make it possible to opt-out ex-employee addresses from domain search.  ·  declined

  13. Include the Breach Model Name attribute in the HIBP breach notification email.  ·  declined

  14. Include last seen / affected date in stealer results  ·  declined

  15. improvements to domain search for bigger companies  ·  declined

  16. Add basic correlation logic to compare newly found pastes against current breaches...

  17. Option to email a report of all exposed passwords linked to my email address back to my email address  ·  declined

  18. To use hashed email address as part of the query instead of HTML encoded  ·  declined

  19. Filter known breaches and pastes in the API  ·  declined

  20. API for recommending to allow/forbid a specific credential set.  ·  declined

Feedback and Knowledge Base