Add wildcard support for spamgourmet addresses
Spamgourmet.com allows a user to create disposable email addresses on the fly. That way a unique email address can be used for each web site you sign up for. The structure of an address is identifier[.##].firstname.lastname@example.org, where the identifier can change per site and [.##] is an optional max number of emails you want to receive. Because a different address is used for each site it is currently impossible to query HIBP for breaches of all sub-addresses, like *.email@example.com. Allowing wildcard search and notification for spamgourmet addresses (or its many alias domains) would enable users to check on any of their disposable addresses.
IT should work now! commented
This was discussed at length in another thread requesting similar for gmail's use of + in their addresses. I'd love it too as I use a different <email>+<sitename>@gmail.com for every website I register on.
Troy's feedback was he's crunched the numbers and can't justify the commitment of time given the low % of addresses using the convention mentioned.
It's a shame because I have to consider re-naming all my accounts with the vanilla address so that I can find (and be notified of) the address in a breach.
JoeBloggs probably uses firstname.lastname@example.org for linked in and email@example.com for facbook. In fact, Joe probably doesn't even remember all the email addresses of this form he has given out.
Not quite sure what you are suggesting.