I'll give them a break if the text predates RFC2606 (1999) and the product hasn't been touched since. > Confusion and conflict can be caused by the use of a cu

I'll give them a break if the text predates RFC2606 (1999) and the product hasn't been touched since. > Confusion and conflict can be caused by the use of a current or future top level domain name in experimentation or testing, as an example in documentation, to indicate invalid names, or as a synonym for the loop back address. Test and experimental software can escape and end up being run against the global operational DNS. Even examples used "only" in documentation can end up being coded and released or cause conflicts due to later real use and the possible acquisition of intellectual property rights in such "example" names. (emphasis added)