As gTLDs increase in popularity they could amend that RFC.
Also it's not particularly clear and unchanging already. "TLDs for Testing, & Documentation Examples" includes .localhost. However, .localhost can be used for more than just testing and documentation. It's treated as a secure context in browsers and subdomains have different storage areas on browsers. (Shockingly, localhost:8000 and localhost:8080 aren't kept separate by browsers)
I wasn't talking about the other ones, just .test.
Maybe as a Blockchain tld :) then it isn't DNS.
Currently new gTLD applications are paused and it's hard to remember how hot it was back when they were open or see how hot it's going to be when they're reopened.
Those are fake domain names. They don't resolve in the root DNS nameservers. This is one of the many reasons that "alternate roots" are terrible and will never be widely adopted.
Also it's not particularly clear and unchanging already. "TLDs for Testing, & Documentation Examples" includes .localhost. However, .localhost can be used for more than just testing and documentation. It's treated as a secure context in browsers and subdomains have different storage areas on browsers. (Shockingly, localhost:8000 and localhost:8080 aren't kept separate by browsers)