Email obfuscation: What works in 2026?

Re:Email obfuscation: What works in 2026? by 0x3f on Thursday April 02, 2026 @04:15AM (#47611453)

What's difficult about it? You know the domain, gregegan.net. You know the @ symbol, presumably. Then put literally any valid text before the @.

[ Parent | on HN ]

Re:Email obfuscation: What works in 2026? by 0xEF on Thursday April 02, 2026 @04:35AM (#47611609)

Completely unrelated to the conversation, but our user names are remarkably similar.

[ Parent | on HN ]

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?

[ Parent | on HN ]

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.

[ Parent | on HN ]

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. :-)

[ Parent | on HN ]

Re:Email obfuscation: What works in 2026? by 0x3f on Saturday April 04, 2026 @04:51AM (#47637218)

If you use the [company name]@yourdomain.com form, people who work at [company name] often say "wow, you work for [company name]??"

[ Parent | on HN ]