could.net - robtex.com
could.net
| DNSSEC | ⚠️ Not signed | ||||||
| A | 3.33.243.145🇺🇸 Amazon3.33.240.0/20 | ||||||
| PTR | a3edc0dabdef92d6d.awsglobalaccelerator.com | ||||||
| A | 15.197.204.56🇺🇸 Amazon15.197.192.0/20 | ||||||
| NS | ns37.domaincontrol.com ⭐ | ||||||
| A | 2603:5:21c1::13🇺🇸 GODADDY-DNS2603:5:21c0::/44 | ||||||
| PTR | ns37.domaincontrol.com | ||||||
| A | 97.74.108.19🇺🇸 GODADDY-DNS97.74.108.0/23 | ||||||
| NS | ns38.domaincontrol.com | ||||||
| A | 2603:5:22c1::13🇺🇸 GODADDY-DNS2603:5:22c0::/44 | ||||||
| PTR | ns38.domaincontrol.com | ||||||
| A | 173.201.76.19🇺🇸 GODADDY-DNS173.201.76.0/23 | ||||||
| SOA | ns37.domaincontrol.comdns@jomax.net 2023-03-31 #16 | ||||||
net
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.gtld-servers.net ⭐ | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1784722257 | ||||||
Same first word
could.uk |
could.do |
could.info |
could.de |
could.co.jp |
could.ru |
could.com |
could.jp |
could.ca |
could.us |
could.net |
could.it |
could.work |
could.co |
could.eu |
Similar names
DNS History
12 records (4 active, 8 former)
○NSns1.namefind.com2016-03-20 → 2018-07-08 · 5 obs
● 2016-03-20 05:59:54
● 2018-07-08 12:59:28
○ 2026-02-25 11:26:22
○ 2026-07-22 12:37:32
○NSns1.sedoparking.com2015-07-19 → 2015-12-07 · 4 obs
● 2015-12-07 14:48:16
○ 2016-03-20 05:59:54
○ 2026-07-22 12:37:32
○NSns2.namefind.com2018-07-08 → 2018-07-08 · 4 obs
● 2018-07-08 12:59:28
○ 2026-02-25 11:26:22
○ 2026-07-22 12:37:32
○NSns2.sedoparking.com2015-07-19 → 2015-12-07 · 4 obs
● 2015-12-07 14:48:16
○ 2016-03-20 05:59:54
○ 2026-07-22 12:37:32
●NSns37.domaincontrol.com2026-02-25 → 2026-07-22 · 3 obs
● 2026-02-25 11:26:22
● 2026-07-22 12:37:32
●NSns38.domaincontrol.com2026-02-25 → 2026-07-22 · 3 obs
● 2026-02-25 11:26:22
● 2026-07-22 12:37:32
○MXmail.nickstel.com2015-07-19 → 2015-12-07 · 4 obs
● 2015-12-07 14:48:16
○ 2016-03-20 05:59:54
○ 2026-07-22 12:37:32
●A15.197.204.562026-02-25 → 2026-07-22 · 3 obs
● 2026-02-25 11:26:22
● 2026-07-22 12:37:32
○A208.73.211.702016-03-20 → 2016-09-11 · 5 obs
● 2016-03-20 05:59:54
● 2016-09-11 21:50:42
○ 2018-07-08 12:59:28
○ 2026-07-22 12:37:32
●A3.33.243.1452026-02-25 → 2026-07-22 · 3 obs
● 2026-02-25 11:26:22
● 2026-07-22 12:37:32
○A68.178.213.612018-07-08 → 2018-07-08 · 4 obs
● 2018-07-08 12:59:28
○ 2026-02-25 11:26:22
○ 2026-07-22 12:37:32
○A72.52.4.912015-07-19 → 2015-12-07 · 4 obs
● 2015-12-07 14:48:16
○ 2016-03-20 05:59:54
○ 2026-07-22 12:37:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| net | m.gtld-servers.net, k.gtld-servers.net, b.gtld-servers.net, f.gtld-servers.net... | - |
| could.net | ns37.domaincontrol.com, ns38.domaincontrol.com | - |
✅ Authoritative Response
Server:173.201.76.19
NS records: ns37.domaincontrol.com, ns38.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for could.net (unsigned zone)
⏱️ Timing
Total: 262ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 15.197.204.56, 3.33.243.145 |
| NS | 2 | ns37.domaincontrol.com, ns38.domaincontrol.com |
| SOA | 1 | ns37.domaincontrol.com dns.jomax.net |
Analysis
IP Addresses
could.net has two IP addresses: 3.33.243.145 and 15.197.204.56
Additional host names — ww8.homeworkcentral.com, www.arrogant.com, zqob.com and two others — share IP numbers with could.net.
Name Servers
could.net has two authoritative name servers — ns37.domaincontrol.com and ns38.domaincontrol.com.
could.net shares its name server setup with other domains, including apa-ma.com, freewords.us, riehlenterprises.com and two others.
The name servers for could.net overlap at least partially with those of other domains — for example drous.com.
Both ns37.domaincontrol.com and ns38.domaincontrol.com have two IP addresses each. ns37.domaincontrol.com resolves to 97.74.108.19 and 2603:5:21c1::13; ns38.domaincontrol.com resolves to 173.201.76.19 and 2603:5:22c1::13.