Search
-
question here... are non-user data not exposed? · declined
-
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
-
Add Retry-After to Access-Control-Expose-Headers · declined
-
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
-
Add % of p0wn count already in DB as new field in API
-
Put Resellers in their own data domain for Stripe · completed
-
Link Breach Lawsuits · declined
-
Add incremental updates to the PWNd password data sets · declined
-
Makes no sense why you wont give information concerning pending lawsuits or how to get things started · declined
-
If possible discover and add - https://www.dchealthlink.com/data-breach · declined
-
consider social security numbers? · declined
-
Make it possible to opt-out ex-employee addresses from domain search. · declined
-
Include the Breach Model Name attribute in the HIBP breach notification email. · declined
-
Include last seen / affected date in stealer results · declined
-
improvements to domain search for bigger companies · declined
-
Add basic correlation logic to compare newly found pastes against current breaches...
-
Option to email a report of all exposed passwords linked to my email address back to my email address · declined
-
To use hashed email address as part of the query instead of HTML encoded · declined
-
Filter known breaches and pastes in the API · declined
-
API for recommending to allow/forbid a specific credential set. · declined