3 ms·

Number 2: already dealt with: * .test * .example * .invalid * .localhost http://www.rfc-editor.org/rfc/rfc2606.txt http://www.rfc-editor.org/rfc/rfc26

• zonidjan 7y ago
  What? No. While those are meant to be reserved, nothing stops you from configuring your resolver to answer for them.
  • mschuster91 7y ago
    Yes, but users will not be happy if they see ".example" on the URL bar. And you can't get a trusted cert for them either. Not confusing users is why the fiasco with the https certificate problem here was initially created. And to be honest I do not have any idea how all needs (users have a trusted HTTPS certificate, a domain name and no "insecure" oe other warnings in the browser, while hackers don't get access to the certificate, and all of it works without internet uplink) can be met...