Re:Email obfuscation: What works in 2026?
by bit1993 on Thursday April 02, 2026 @01:52AM
(#47610441)
Good stuff, but I think the title should be Email address obfuscation. Thank you for sharing I guess, but spammers can now learn from this too (:
[ Parent
| on HN ]
Re:Email obfuscation: What works in 2026?
by ghywertelling on Thursday April 02, 2026 @03:53AM
(#47611306)
https://www.gregegan.net/
Contact details: [any mailbox] [at] [the domain name of this web site]. Please don’t ask me to give interviews, sign books, appear on podcasts, attend conferences or conventions, or provide feedback or endorsements for works of fiction, scientific theories, or slabs of text disgorged by chatbots.
I have no idea how to decipher this obfuscation.
What's difficult about it? You know the domain, gregegan.net. You know the @ symbol, presumably. Then put literally any valid text before the @.
Completely unrelated to the conversation, but our user names are remarkably similar.
Re:Email obfuscation: What works in 2026?
by ghywertelling on Thursday April 02, 2026 @07:26AM
(#47612954)
Is that even possible? Shouldn't the recipient email id need to be created first to be addressable?
Re:Email obfuscation: What works in 2026?
by cyberlimerence on Thursday April 02, 2026 @07:54AM
(#47613202)
Of course, the technical term for that setup is 'catch all', you can set this up with your email provider. You can send your email to "[email protected]", for example.
Re:Email obfuscation: What works in 2026?
by bornfreddy on Thursday April 02, 2026 @04:06PM
(#47619501)
A friend gave out an email [email protected] (he owns the domain). He says it's incredible how many people "corrected" him, and how persistent some of them were. :-)
If you use the [company name]@yourdomain.com form, people who work at [company name] often say "wow, you work for [company name]??"