51–60 of 68 posts
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.
There is a huge chance that you hit a mailbox when you make up an email address.
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.
It's a real domain with functioning... whatever I need to test. Email, DNS, Identity servers, etc.
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!
Earlier quoted context omitted.
Let me introduce you to neverssl.com!
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
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
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.
Exactly this. People heavily underestimate how many domain names are registered. There is a huge chance that you hit a mailbox when you make up an email address.
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.
This shouldn't be possible on Android. Google requires apps capturing http/s deeplinks verify ownership of the URI.[1] They can accept any other schema declared in their manifest otherwise. Example code would seem most plausible, but I can't see how it would work. [1] https://developer.android.com/training/app-links/verify-site...