Hacker News Reader

Comment by craigds | Hacker News Reader

I don't see the point of using honeywords. I mean, I've used them a bit, but any spammer is going to strip them immediately, so they're useless for identifying which provider leaked your address, right? And now to login, you need to remember the honeyword you used to register, which is a big inconvenience for anyone not using a password manager. (Use a password manager!)

View on HN

If you primarily use honeywords, then you can filter out anything going to craigds@host.tld as spam. The hard part would be transitioning people you want to communicate with to craigds+{family,friends,correspondence}@host.tld.

Optionally, retain craigds@host.tld for personal and professional communication/correspondence, and move everything else to craigds1+{something}@host.tld (or a different host).

I just bought an entire TLD for signups/spam and made it a catchall. One positive is I know when companies are breached often before they announce it as my pagerduty@domain.com told me a little while ago.

http://www.theregister.co.uk/2015/07/31/incident_managers_pa...

This is a great idea! What's it like viewing email? Which client do you use? Is it easy to see which email address the email was sent to?

Viewing email is as you would expect, the email they sent to is in the header so it's just a single click away in Thunderbird.

I've used the same strategy for the past few years with great results. Like you said it's really nice to see early on which companies are leaking your info.

It's also nice to be able to kill specific email addresses once a breach has been disclosed and the spam becomes plentiful.

Wait, did you really mean "TLD", or just "domain"?

Reply on news.ycombinator.com