could.net checked at 2025-01-01T17:36:11.730Z 143ms 60/60/60 100% R:9
DNSTREE.COM - could.net
Search for IP or hostnames
could.net
NS | ns37.domaincontrol.com | ||||||
A | 2603:5:21c1::13 🇺🇸 GODADDY-DNS | ||||||
PTR | ns37.domaincontrol.com | ||||||
A | 97.74.108.19🇺🇸 GODADDY-DNS | ||||||
PTR | ns37.domaincontrol.com | ||||||
NS | ns38.domaincontrol.com | ||||||
A | 2603:5:22c1::13 🇺🇸 GODADDY-DNS | ||||||
PTR | ns38.domaincontrol.com | ||||||
A | 173.201.76.19🇺🇸 GODADDY-DNS | ||||||
PTR | ns38.domaincontrol.com | ||||||
A | 3.33.243.145🇺🇸 Amazon | ||||||
PTR | a3edc0dabdef92d6d.awsglobalaccelerator.com | ||||||
A | 15.197.204.56🇺🇸 Amazon | ||||||
PTR | a3edc0dabdef92d6d.awsglobalaccelerator.com |
net
AI analysis
could.net is configured to point to two IP addresses: 3.33.243.145 and 15.197.204.56.
IP numbers are shared between could.net and other host names such as kbh.biz, supercars.tv, my-e-bookstore.com, savannahchevy.com, and mail.encryption-cloud.com.
Two name servers, ns37.domaincontrol.com and ns38.domaincontrol.com, have been delegated to could.net.
The name server setup of could.net is identical to that of other domains such as freewords.us, riehlenterprises.com, olliebh.com, polvis.net, and tenlv.net.
The domain could.net shares name servers, at least in part, with other domains such as drous.com.
ns37.domaincontrol.com and ns38.domaincontrol.com both point to two IP numbers each: 2603:5:21c1::13, 97.74.108.19 for ns37.domaincontrol.com and 2603:5:22c1::13, 173.201.76.19 for ns38.domaincontrol.com.