Since I keep seeing developers use ‘pretty’ IP addresses like ’1.2.3.4’ in example configurations; a reminder that you MUST NOT use publicly routable addresses that you do not control in your code.
Instead, use one of the available 'TEST-NET' IPv4 or IPv6 ranges documented in RFC 6890;
192.0.2.0/24
198.51.100.0/24
203.0.113.0/24
❌ 1.2.3.4
✅ 192.0.2.4
and for IPv6;
✅ 2001:db8::/32
Pass it on to all of your fellow developers, documentation writers, and so forth.
Full RFC for special purpose addresses;
https://datatracker.ietf.org/doc/rfc6890/
Reserved for documentation, IPv4 and IPv6;
https://datatracker.ietf.org/doc/rfc5737/
https://datatracker.ietf.org/doc/rfc3849/
1/ 🧵
The same goes for domain names; do NOT use a public domain name you do not control in your configuration, documentation, or UI language.
Instead, use one of the available reserved domain names documented in RFC 2606, such as 'example.com', 'example.net', or the .example top-level domain.
❌ test.com
❌ yourdomain.com
✅ example.com
✅ yourdomain.example
Pass it on to your fellow developers, designers, documentation writers, and so forth.
Full RFC text is here;
https://datatracker.ietf.org/doc/rfc2606/
2/ 🧵
The same goes for domain names; do NOT use a public domain name you do not control in your configuration, documentation, or UI language.
Instead, use one of the available reserved domain names documented in RFC 2606, such as 'example.com', 'example.net', or the .example top-level domain.
❌ test.com
❌ yourdomain.com
✅ example.com
✅ yourdomain.example