couldshould.com - dns.ninja
couldshould.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 3.33.251.168🇺🇸 Amazon3.33.240.0/20 | ||||||
| PTR | aec037177372cc6cd.awsglobalaccelerator.com | ||||||
| A | 15.197.225.128🇺🇸 Amazon15.197.224.0/20 | ||||||
| NS | ns71.domaincontrol.com ⭐ | ||||||
| A | 2603:5:2194::2e🇺🇸 GODADDY-DNS2603:5:2190::/44 | ||||||
| PTR | ns71.domaincontrol.com | ||||||
| A | 97.74.105.46🇺🇸 GODADDY-DNS97.74.104.0/23 | ||||||
| PTR | ns71.domaincontrol.com | ||||||
| NS | ns72.domaincontrol.com | ||||||
| A | 2603:5:2294::2e🇺🇸 GODADDY-DNS2603:5:2290::/44 | ||||||
| PTR | ns72.domaincontrol.com | ||||||
| A | 173.201.73.46🇺🇸 GODADDY-DNS173.201.72.0/23 | ||||||
| PTR | ns72.domaincontrol.com | ||||||
| SOA | ns71.domaincontrol.comdns@jomax.net 2026-07-04 #3 | ||||||
com
| 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=1784514472 | ||||||
Same first word
couldshould.com |
DNS History
10 records (4 active, 6 former)
○NSns17.domaincontrol.com2015-05-27 → 2016-04-15 · 4 obs
● 2016-04-15 19:36:10
○ 2016-11-25 20:49:06
○ 2026-07-20 02:30:32
○NSns18.domaincontrol.com2015-05-27 → 2016-04-15 · 4 obs
● 2016-04-15 19:36:10
○ 2016-11-25 20:49:06
○ 2026-07-20 02:30:32
●NSns71.domaincontrol.com2026-03-07 → 2026-07-20 · 3 obs
● 2026-03-07 04:03:58
● 2026-07-20 02:30:32
●NSns72.domaincontrol.com2026-03-07 → 2026-07-20 · 3 obs
● 2026-03-07 04:03:58
● 2026-07-20 02:30:32
○MXmailstore1.secureserver.net2015-05-27 → 2016-04-15 · 4 obs
● 2016-04-15 19:36:10
○ 2016-11-25 20:49:06
○ 2026-07-20 02:30:32
○MXsmtp.secureserver.net2015-05-27 → 2016-04-15 · 4 obs
● 2016-04-15 19:36:10
○ 2016-11-25 20:49:06
○ 2026-07-20 02:30:32
●A15.197.225.1282026-03-07 → 2026-07-20 · 3 obs
● 2026-03-07 04:03:58
● 2026-07-20 02:30:32
●A3.33.251.1682026-03-07 → 2026-07-20 · 3 obs
● 2026-03-07 04:03:58
● 2026-07-20 02:30:32
○A50.63.202.442015-05-27 → 2016-04-15 · 4 obs
● 2016-04-15 19:36:10
○ 2016-11-25 20:49:06
○ 2026-07-20 02:30:32
○A74.220.199.62018-07-22 → 2018-07-22 · 4 obs
● 2018-07-22 00:47:50
○ 2026-03-07 04:03:58
○ 2026-07-20 02:30:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | b.gtld-servers.net, j.gtld-servers.net, i.gtld-servers.net, e.gtld-servers.net... | - |
| couldshould.com | ns71.domaincontrol.com, ns72.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:97.74.105.46
NS records: ns71.domaincontrol.com, ns72.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for couldshould.com (unsigned zone)
⏱️ Timing
Total: 548ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 2 | 15.197.225.128, 3.33.251.168 |
| NS | 2 | ns71.domaincontrol.com, ns72.domaincontrol.com |
| SOA | 1 | ns71.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns71.domaincontrol.com, ns71.domaincontrol.com, ns72.domaincontrol.com...)
Analysis
IP Addresses
couldshould.com directs to two IP numbers, 3.33.251.168 and 15.197.225.128
Among the host names that share IP numbers with couldshould.com are ymas.com, edenglen.com, houserater.org and two others.
Name Servers
The NS records for couldshould.com delegate to ns71.domaincontrol.com and ns72.domaincontrol.com.
couldshould.com has the same name server delegation as a number of other domains, such as kcjacks.com, theboom.tv, tracksforyou.com and two more.
ns71.domaincontrol.com resolves to 97.74.105.46 and 2603:5:2194::2e. Likewise, ns72.domaincontrol.com resolves to 173.201.73.46 and 2603:5:2294::2e — two IP addresses apiece.