4 ms·
Strictly speaking, the dot in the latter space isn't actually necessary. It needs to be a resolvable domain, but if you bought a TLD you could be "name@tld"
by benchaney 9y ago
Strictly speaking, the dot in the latter space isn't actually necessary. It needs to be a resolvable domain, but if you bought a TLD you could be "name@tld"
- TremendousJudge 9y ago...is there someone out there who did this?
- benchaney 9y agoNot that I'm aware of. Although I wouldn't be surprised if google did it for their employees. They already own the google TLD, they could very easily make it point to the google.com emails.
- OJFord 9y agoHow many HN-reading googlers have you just made to send 'Test' emails to themselves, I wonder!
- bitJericho 9y agoI don't think an @domain is required if it's an email address on the same mail server.
- deleted 9y ago[deleted]
- OJFord 9y agoThat certainly used to work on Gmail; I haven't tried recently. (Obvious caveat being that any provider can trivially append @provid.er if you don't specify, so this isn't really proof that email is specified that way.)
- eximius 9y agoWow, that is literally the only reason I would want a TLD
- fanf2 9y agoICANN forbids application records at the apex of a TLD. The only TLDs that do funky things like this are ccTLDs. And if you try to actually use a bare TLD you will crash hard into collisions with unqualifed domains and search paths. So, fun as a hack to amuse fellow techies but not useful for anything real.
- eridius 9y agoCan you actually attach an MX record to a tld?