couldbeillegal.com - robtex.com
couldbeillegal.com
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns67.domaincontrol.com ⭐ | ||||||
| A | 2603:5:2174::2c🇺🇸 GODADDY-DNS2603:5:2170::/44 | ||||||
| PTR | ns67.domaincontrol.com | ||||||
| A | 97.74.103.44🇺🇸 GODADDY-DNS97.74.102.0/23 | ||||||
| PTR | ns67.domaincontrol.com | ||||||
| NS | ns68.domaincontrol.com | ||||||
| A | 2603:5:2274::2c🇺🇸 GODADDY-DNS2603:5:2270::/44 | ||||||
| PTR | ns68.domaincontrol.com | ||||||
| A | 173.201.71.44🇺🇸 GODADDY-DNS173.201.70.0/23 | ||||||
| PTR | ns68.domaincontrol.com | ||||||
| SOA | ns67.domaincontrol.comdns@jomax.net 2026-02-18 #26 | ||||||
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=1774480552 | ||||||
Same first word
couldbeillegal.com |
DNS History
8 records (2 active, 6 former)
○NSdns.site5.com2015-05-18 → 2018-09-10 · 3 obs
● 2018-09-10 13:36:56
○ 2026-03-25 23:36:28
○NSdns2.site5.com2015-05-18 → 2018-09-10 · 3 obs
● 2018-09-10 13:36:56
○ 2026-03-25 23:36:28
●NSns67.domaincontrol.com2026-03-25 → 2026-03-25 · 2 obs
● 2026-03-25 23:36:28
●NSns68.domaincontrol.com2026-03-25 → 2026-03-25 · 2 obs
● 2026-03-25 23:36:28
○MXcouldbeillegal.com2015-05-18 → 2018-09-10 · 3 obs
● 2018-09-10 13:36:56
○ 2026-03-25 23:36:28
○A108.168.206.1002015-10-16 → 2017-01-19 · 5 obs
● 2015-10-16 08:20:18
● 2017-01-19 09:30:24
○ 2018-09-10 13:36:56
○ 2026-03-25 23:36:28
○A192.185.134.352018-09-10 → 2018-09-10 · 3 obs
● 2018-09-10 13:36:56
○ 2026-03-25 23:36:28
○A50.23.201.2442015-05-18 → 2015-05-18 · 3 obs
○ 2015-10-16 08:20:18
○ 2026-03-25 23:36:28
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net... | - |
| couldbeillegal.com | ns67.domaincontrol.com, ns68.domaincontrol.com | 4 records |
✅ Authoritative Response
Server:97.74.103.44
NS records: ns67.domaincontrol.com, ns68.domaincontrol.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for couldbeillegal.com (unsigned zone)
⏱️ Timing
Total: 1708ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | ns67.domaincontrol.com, ns68.domaincontrol.com |
| SOA | 1 | ns67.domaincontrol.com dns.jomax.net |
📌 Glue Records Collected
Total: 4
Out-of-bailiwick: 4 (ns67.domaincontrol.com, ns67.domaincontrol.com, ns68.domaincontrol.com...)
Analysis
Name Servers
Delegation for couldbeillegal.com rests with two name servers, ns67.domaincontrol.com and ns68.domaincontrol.com.
couldbeillegal.com shares the same name server setup as other domains, including mayporthardware.com, dynalase.com, bluelightspecial.org, cwgstore.co and greatvoice.mobi.
couldbeillegal.com shares name servers with other domains at least partially, for example ndfloodinfo.com.
Host names with two IP numbers: ns67.domaincontrol.com points to 2603:5:2174::2c and 97.74.103.44; ns68.domaincontrol.com points to 2603:5:2274::2c and 173.201.71.44.