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 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.
Only took 12 years of posting this to get a decent discussion going:
IANA also reserves TLDs like '.test' and '.example' as well as some IDN equivalents.
Reminds me of the corp.com saga.
https://krebsonsecurity.com/2020/04/microsoft-buys-corp-com-...
$ dig example.com. mx +short
0 .
It has an interesting MX record. I wonder what this does? Specifically, what should a mail agent do when the MX record points to "." ?There are several domains dedicated for example and special purposes. This is just one.
https://www.iana.org/assignments/special-use-domain-names/sp...
Good on whomever for making it a public service rather than a crap site filled with ads.
I would to know how much traffic this website receives
The web logs on example.com must be a treasure trove of interesting traffic, and also a security risk in some ways, depending on who has been testing with it.
I wonder how they managed to get a horizontal scrollbar.
Edit: its a chrome extenstion I use.
The advantage of example.com is that its still served over HTTP, which is very helpful if you are trying to force a redirect for wifi login or 'out of quota' on a phone plan.