Live data from Hacker News

Example Domain

example.com

61–68 of 68 posts

Re: Example Domain

#61

Earlier quoted context omitted.

I have a .com domain with 'test' in the name. I was mildly DNS spammed because Microsoft admins would create that thing with test in the name. I'd get 10-20 DNS packets a day. I moved it to an external DNS provider just to give my logs a break.

20 packets a day? Phew! So you barely survived the DDoS!

Well, you also have to run the Kubernetes cluster, ELK stack, Postgres, Redis, Kafka, Prometheus, Grafana and Jaeger to monitor the application and scale elastically between 0 and 20 packets.

Re: Example Domain

#62

This is a great reminder that when working with test data for stuff like email delivery, always use example.com (or a few other similar TLDs) and not stuff like "test.com" or "acme.com" or "dummyuser.com". I see this all the time by devs and they don't understand the risk and why example.com was put into the standards.

I have a .com domain with 'test' in the name. I was mildly DNS spammed because Microsoft admins would create that thing with test in the name. I'd get 10-20 DNS packets a day. I moved it to an external DNS provider just to give my logs a break.

At least you’re not a sysadmin for Contoso, those folks must have their hands full.

Re: Example Domain

#63

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

And .local, right?

Actually, no. According to RFC 2606 - Reserved Top Level DNS Names, the following four domain names are reserved:

  .test
  .example
  .invalid
  .localhost

Re: Example Domain

#66
post #45

Earlier quoted context omitted.

I always use `myco.example` for testing requests and emails, as well as documentation. https://en.wikipedia.org/wiki/.example It'll never resolve to anything, and makes it really obvious the code is for testing or sample code.

No guarantee an .example TLD won't be created

Well I am hilariously wrong. Thanks, renewiltord.

https://news.ycombinator.com/item?id=29629387

Re: Example Domain

#67

This is a great reminder that when working with test data for stuff like email delivery, always use example.com (or a few other similar TLDs) and not stuff like "test.com" or "acme.com" or "dummyuser.com". I see this all the time by devs and they don't understand the risk and why example.com was put into the standards.

I always use `myco.example` for testing requests and emails, as well as documentation. https://en.wikipedia.org/wiki/.example It'll never resolve to anything, and makes it really obvious the code is for testing or sample code.

Never heard of the .example TLD, so thanks for that. However, an issue I see with it is that it doesn’t look like a domain name. Things that end in ‘.com’ are synonymous with domain names, regardless of how accurate that assumption really is. I think people are just starting to get familiar with these new alternative TLD names, but I can easily see business people not understanding ‘myco.example’, while they would understand ’example.com’.

Re: Example Domain

#68
post #29
post #20

Earlier quoted context omitted.

There are a number of those. I use http://detectportal.firefox.com/

I always use http://perdu.com because it makes me smile. It's not even intended for testing purposes.

I use aol.com lol
Post reply on HN