Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I usually go for <company>@example.com where <company> is the company I’m handing my address to. After a breach I route that address to /dev/null


That's trivially easy to guess -- and game.

You want something that is sufficiently random that it can't be easily guessed or gamed, but can be quickly and easily determined on your side.

Salted cryptographic hashes might be a good place to start.


Most spammers won't go through the of "gaming" it. There's no upside. There are far easier targets to focus on than sending more mail to a single recipient who is more sophisticated.


After a breach of <company>@example.com, forward it to support@<company.com>.


Don’t give me ideas.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: