Search

← Customer feedback for Have I been pwned?
(thinking…)
Reset
  • All (25)
  • Articles (0)
  • Ideas (25)

    1. Enabl API to be queried such that it returns only the breach name

    2. Add potential causes for the 503 response.  ·  completed

    3. Incomplete Data  ·  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. The ability to report data breaches

    6. Add an API endpoint that returns a rate limited response

    7. Domain wide search results - Refined export of data

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

    9. API option to only return whether an account is breached or not  ·  completed

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

    11. Allow notifications for an entire domain or allow a way to pull the domain report without having to verify every time.  ·  declined

    12. Add wpengine.com breach  ·  declined

    13. Include the affected email address in the API json structure as well.

    14. Ok, so I've been pwned, now what?  ·  declined

    15. Add wildcard support for spamgourmet addresses

    16. Add sprashivai.ru breach  ·  completed

    17. Mark ArmorGames as confirmed pwned  ·  declined

    18. add a date column to the excel export to make pinpointing recent data breaches easier

    19. ... make it easy to see what data are associated with a breach for a given account.  ·  declined

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

    ← Previous 1

    Feedback and Knowledge Base

    (thinking…)