Refer to RFC 5233 section 4: "Subaddress comparisons".
The HIBP implementation for this would be plain. Instead of the search index being the literal address value, it should be the normalized *deliverable* address. E.G., instead of "person+foobar@example.com", the index would contain "person@example.com".
Search input should be normalized the same way and therefore find all subaddress variations.
There is some variation in delimiter between providers, but pragmatically, there are only a few major predominant styles. At a minimum, the UI could prompt "X+Y@z.co" looks like a subaddress, do you want to include "X@z.co" in your search?
Refer to RFC 5233 section 4: "Subaddress comparisons".
The HIBP implementation for this would be plain. Instead of the search index being the literal address value, it should be the normalized *deliverable* address. E.G., instead of "person+foobar@example.com", the index would contain "person@example.com".
Search input should be normalized the same way and therefore find all subaddress variations.
There is some variation in delimiter between providers, but pragmatically, there are only a few major predominant styles. At a minimum, the UI could prompt "X+Y@z.co" looks like a subaddress, do you want to include "X@z.co" in your search?