24 ms·

And "home.com" is owned by someone, and registered through GoDaddy: Domain Name: HOME.COM Registry Domain ID: 1668509_DOMAIN_COM-VRSN Registrar WHOIS

by pwg 2y ago

And "home.com" is owned by someone, and registered through GoDaddy: Domain Name: HOME.COM Registry Domain ID: 1668509_DOMAIN_COM-VRSN Registrar WHOIS Server: whois.brandsight.com Registrar URL: http://gcd.com Updated Date: 2022-04-09T03:55:51Z Creation Date: 1993-12-16T05:00:00Z Registry Expiry Date: 2031-12-15T05:00:00Z Registrar: GoDaddy Corporate Domains, LLC Registrar IANA ID: 3786 Registrar Abuse Contact Email: abuse@gcd.com Registrar Abuse Contact Phone: +1.5189669187 Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Name Server: NS2-02.AZURE-DNS.NET Name Server: NS3-02.AZURE-DNS.ORG Name Server: NS4-02.AZURE-DNS.INFO DNSSEC: unsigned

thot_experiment 2y ago
Not on my LAN it isn't! Why would I care who owns the domain?
- pwg 2y ago
  For your own devices and use (provided you can configure your devices to all use your local nameserver) you really don't need to care (unless you, at some point, want to make use of whatever the true owner is offering at "home.com"). But, for any visitors, if they have their devices configured to use their providers name servers, or if they have configured them to use one of the public name servers, if you direct them to "home.com" for something on your local lan, their device will instead resolve "home.com" to the IP assigned by the actual owner, and they will not be able to access your lan local "home.com" services.