From the RFC about URLs: https://tools.ietf.org/html/rfc3986#section-3.2.2 https://tools.ietf.org/html/rfc3986#section-3.2.2 > The presence of a host subcompon

From the RFC about URLs: https://tools.ietf.org/html/rfc3986#section-3.2.2 https://tools.ietf.org/html/rfc3986#section-3.2.2 > The presence of a host subcomponent within a URI does not imply that the scheme requires access to the given host on the Internet. In many cases, the host syntax is used only for the sake of reusing the existing registration process created and deployed for DNS, thus obtaining a globally unique name without the cost of deploying another registry. However, such use comes with its own costs: domain name ownership may change over time for reasons not anticipated by the URI producer. In other cases, the data within the host component identifies a registered name that has nothing to do with an Internet host. We use the name "host" for the ABNF rule because that is its most common purpose, not its only purpose. So, the fact that the host part of http(s) URLs are resolved using DNS is not a limitation of the URL spec. Instead that's an implementation restriction.