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

Example Domain

example.com

Post reply on HN
Print view View original

21–30 of 68 posts

Re: Example Domain

#21

Post by roywiggins »

aleksi wrote: post #17
shakna wrote: post #16

Earlier quoted context omitted.

The difference being, example.com is run by IANA [0] and guaranteed by them, whereas neverssl is just a kind-hearted soul, and may one day resolve to something else. [0] https://www.iana.org/domains/reserved

That page says that example.com is registered by IANA. It makes no promises about it being plaintext HTTP only or even that HTTP service is available.

Yeah, but neverssl.com could expire and start serving porn (or whatever), but we can be pretty sure example.com won't.

Re: Example Domain

#23

Post by shakna »

aleksi wrote: post #17
shakna wrote: post #16

Earlier quoted context omitted.

The difference being, example.com is run by IANA [0] and guaranteed by them, whereas neverssl is just a kind-hearted soul, and may one day resolve to something else. [0] https://www.iana.org/domains/reserved

That page says that example.com is registered by IANA. It makes no promises about it being plaintext HTTP only or even that HTTP service is available.

Only somewhat.

> 2. Application software SHOULD NOT recognize example names as special and SHOULD use example names as they would other domain names.

> 3. Name resolution APIs and libraries SHOULD NOT recognize example names as special and SHOULD NOT treat them differently. Name resolution APIs SHOULD send queries for example names to their configured caching DNS server(s).

> 6. DNS server operators SHOULD be aware that example names are reserved for use in documentation.

You are guaranteed to be able to try and resolve the domain, which should generally be enough for the crappy man-in-the-middle systems to work.

However, example.com should never suddenly start serving you a cryptominer, etc. Which is the larger concern.

Re: Example Domain

#25

Post by colmmacc »

oftenwrong wrote: post #22

IANA also reserves TLDs like '.test' and '.example' as well as some IDN equivalents. https://www.rfc-editor.org/rfc/rfc2606.html https://www.iana.org/domains/reserved

There are also documentation and example IP prefixes! 192.0.2.0/24 and 2001:db8::/32.

Re: Example Domain

#28

Post by innocenat »

shakna wrote: post #23
aleksi wrote: post #17

Earlier quoted context omitted.

That page says that example.com is registered by IANA. It makes no promises about it being plaintext HTTP only or even that HTTP service is available.

Only somewhat. > 2. Application software SHOULD NOT recognize example names as special and SHOULD use example names as they would other domain names. > 3. Name resolution APIs and libraries SHOULD NOT recognize example names as special and SHOULD NOT treat them differently. Name resolution APIs SHOULD send queries for example names to their configured caching DNS server(s). > 6. DNS server operators SHOULD be aware t…

> You are guaranteed to be able to try and resolve the domain, which should generally be enough for the crappy man-in-the-middle systems to work.

I have never seen any captive portal work at DNS level though (and that by itself sounds problematic). They works at HTTP level. So if one day example.com start using HSTS then it will also be a problem, in addition to nowadays browser defaulting to HTTPS so you have to type http://example.com yourself.

neverssl.com guarantees all of that, at least as long as it's there.

Re: Example Domain

#30

Post by pjerem »

smashed wrote: post #6
intosi wrote: post #3

I forgot I had it installed on my phone, but clicking the link opened, to my surprise, the Simply Piano app. Why you'd associate your app with that domain for legitimate purposes is a bit of a mystery to me.

Probably by copy pasting example code?

That.
Post reply on HN