Hacker News Reader

Shame it requires polluting the root of your zone. Could have used a TXT record at "_redirect-name.example.com" or similar instead.

[edit] Also, this service will be abused by spammers and it will then become impossible to use a "redirect.name" URL in email.

View on HN

This is the kind of feedback I was looking for by putting this out there - so thanks!

I hadn't thought about putting the TXT records on another hostname. That would actually be advantageous for using a CNAME instead of a A record, too.

Can you elaborate on "impossible to use redirect.name URL in email"?

Does something about the redirect.name setup negate the use of DKIM?

It shouldn't. Nor should it affect SPF records and the like.

My point was that it will be used by spammers to hide their domains. So redirect.name will quickly get added to email blacklists, so people wont be able to send legitimate emails containing redirect.name URLs as they'll be rejected/blocked/filtered.

redirect.name is never part of the actual redirect. It's only the documentation site. It's always your domain that is serving the HTTP redirect.

Reply on news.ycombinator.com