Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

foo@bar.com

bar.com

Post reply on HN
Print view View original

61–70 of 301 posts

Re: foo@bar.com

#61

Post by Hamuko »

EvanAnderson wrote: post #37
chrismeller wrote: post #4

Something that I’m surprised a lot of devs don’t know; there are official domains you’re supposed to use for documentation, testing, etc. They are specifically reserved by IANA for these purposes. Originally I think it was just example.com, but they now have a list of all them: https://www.iana.org/domains/reserved

You also have Microsoft's list of domains / companies used in their documentation and examples: https://social.technet.microsoft.com/wiki/contents/articles/...

Didn't Microsoft for the longest time use a domain in their documentation that they didn't own and were basically forced to buy it now?

Re: foo@bar.com

#62

Post by djsumdog »

I always used bob@bob.bob. It's not a real TLD (although at the rate of new TLDs, it might be soon) but it still validated on most websites.

Re: foo@bar.com

#63

Post by ssorallen »

chrismeller wrote: post #4

Something that I’m surprised a lot of devs don’t know; there are official domains you’re supposed to use for documentation, testing, etc. They are specifically reserved by IANA for these purposes. Originally I think it was just example.com, but they now have a list of all them: https://www.iana.org/domains/reserved

Thank you, I was unaware of this. I found the relevant section in the doc that was linked from your original link:

2. TLDs for Testing, & Documentation Examples

To safely satisfy these needs, four domain names are reserved as listed and described below.

                   .test
                .example
                .invalid
              .localhost
* ".test" is recommended for use in testing of current or new DNS related code.

* ".example" is recommended for use in documentation or as examples.

* ".invalid" is intended for use in online construction of domain names that are sure to be invalid and which it is obvious at a glance are invalid.

* The ".localhost" TLD has traditionally been statically defined in host DNS implementations as having an A record pointing to the loop back IP address and is reserved for such use. Any other use would conflict with widely deployed code which assumes this use.

https://tools.ietf.org/html/rfc2606#section-2

3. Reserved Example Second Level Domain Names

* example.com

* example.net

* example.org

https://tools.ietf.org/html/rfc2606#section-3

Re: foo@bar.com

#64

Post by chrismeller »

davemtl wrote: post #54
chrismeller wrote: post #4

Something that I’m surprised a lot of devs don’t know; there are official domains you’re supposed to use for documentation, testing, etc. They are specifically reserved by IANA for these purposes. Originally I think it was just example.com, but they now have a list of all them: https://www.iana.org/domains/reserved

Indeed. I've owned `invaliddomain.com` for almost 20 years. You'll be surprised how many use it for testing. One morning I woke up to 30,000 e-mails from Sony Japan with PDFs attached of scanned hand-written part orders. Something similar with Boeing sending me backup notifications. I notified each of these companies about their configuration through their official channels, only to be told "no, it's your server doin…

Haha. That’s actually surprising, I mean that one takes some work to even type. I’ve mentioned previously on HN that I own doesnthaveone.com, which is constantly bombarded with random crap. I wish I had some big public customer data to see what other fake ones show up.

Re: foo@bar.com

#65

Post by samoa42 »

Hamuko wrote: post #55
nebulous1 wrote: post #20

Earlier quoted context omitted.

A lot of people learned this the hard way when Google bought and later enabled permanent HSTS for the .dev domain (prior to actually publicly releasing it) in Chrome, breaking everybody's non https local .dev environments. As mentioned above, it should have been .test

Can't wait for .internal to be registered so that my internal DNS breaks.

should have used .local

Re: foo@bar.com

#66

Post by exikyut »

chrismeller wrote: post #4

Something that I’m surprised a lot of devs don’t know; there are official domains you’re supposed to use for documentation, testing, etc. They are specifically reserved by IANA for these purposes. Originally I think it was just example.com, but they now have a list of all them: https://www.iana.org/domains/reserved

That just provides a "this exists and is a thing" overview, with the bulk of the information hiding in https://tools.ietf.org/html/rfc6761.

That's the link that qualifies special behavior for anything ending in ".test", ".localhost", ".invalid", and the set of "example.???" domains.

Copy-pasting the RFC into a comment would be a bit spammy (it's three pages of hyper-specificity), so just go read that. It's quite accessible and the mechanics are useful to be aware of.

Re: foo@bar.com

#67

Post by yesbabyyes »

Hamuko wrote: post #61
EvanAnderson wrote: post #37

Earlier quoted context omitted.

You also have Microsoft's list of domains / companies used in their documentation and examples: https://social.technet.microsoft.com/wiki/contents/articles/...

Didn't Microsoft for the longest time use a domain in their documentation that they didn't own and were basically forced to buy it now?

Yes, you're probably thinking of corp.com, which MS used as the default for AD setups. It went up for auction this spring and MS bought it:

https://krebsonsecurity.com/2020/04/microsoft-buys-corp-com-...

Re: foo@bar.com

#68

Post by [deleted] »

Hamuko wrote: post #61
EvanAnderson wrote: post #37

Earlier quoted context omitted.

You also have Microsoft's list of domains / companies used in their documentation and examples: https://social.technet.microsoft.com/wiki/contents/articles/...

Didn't Microsoft for the longest time use a domain in their documentation that they didn't own and were basically forced to buy it now?

[deleted]

Re: foo@bar.com

#69

Post by [deleted] »

Hamuko wrote: post #61
EvanAnderson wrote: post #37

Earlier quoted context omitted.

You also have Microsoft's list of domains / companies used in their documentation and examples: https://social.technet.microsoft.com/wiki/contents/articles/...

Didn't Microsoft for the longest time use a domain in their documentation that they didn't own and were basically forced to buy it now?

[deleted]

Re: foo@bar.com

#70

Post by CydeWeys »

akritrime wrote: post #51
CydeWeys wrote: post #39

Earlier quoted context omitted.

It was unintentional. Source: The horse's mouth. I'm the guy who came up with the idea of launching .dev and .app as HTTPS-only TLDs, and I'm the one who had them added to the HSTS preload list.

How do we know you are the right horse? Sorry, just watched `/the social dilemma` and now I am skeptical of all information on the internet.

If you give me your email I can send you a message from my _lastname_@ work address, which you can then match up with published media I've done under my name, e.g. https://www.youtube.com/watch?v=kBkX30Cj7Bw and https://security.googleblog.com/2017/09/broadening-hsts-to-s...

Or you can look at the matching username on GitHub ( https://github.com/CydeWeys ) and see that I'm a member of the Google org and owner of the Nomulus repo ( https://github.com/google/nomulus/graphs/contributors ), the software running our TLD registry and which was announced here: https://opensource.googleblog.com/2016/10/introducing-nomulu...

Or I could just dig out my GPG key and sign a message.

So I respect your healthy skepticism, but I promise I'm really me, and not just someone pretending to be me! And I'll also note that, in all my time on HN, I've never once seen someone pretending to be anyone they weren't, at least not on seasoned accounts like mine. You can go back through my 5 years of comments on here, and every time I say I'm a specific person out there in the real world, it's always the same consistent person.

Post reply on HN