comnetcom.com - dns.ninja
comnetcom.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 66.45.246.141🇺🇸 NJIIX-166.45.224.0/19 NJIIX.net 110B Meadowlands Pkwy Secaucus, NJ 07094 | ||||||
| NS | ns1.domainrecover.com ⭐ | ||||||
| A | 149.248.38.58🇺🇸 AS-VULTR149.248.32.0/20 Vultr Assigned Prefix | ||||||
| PTR | 149.248.38.58.vultrusercontent.com | ||||||
| NS | ns2.domainrecover.com | ||||||
| A | 199.247.16.62🇩🇪 AS-VULTR199.247.16.0/21 Vultr Assigned Prefix | ||||||
| TXT | yGjyZf7SHD | ||||||
| SOA | ns1.domainrecover.comhostmaster@domainreover.com serial=1623031840 | ||||||
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=1782659940 | ||||||
Same first word
Similar names
tecnocomm.com.mx |
commontec.dk |
tecnocomm.mx |
cocomment.org |
nocommtec.com |
cocomment.com |
netcomcom.com |
nocommtec.de |
commontec.com |
tecnocomm.com |
DNS History
12 records (3 active, 9 former)
○NShost.tradenames.com2015-11-24 → 2016-03-08 · 4 obs
● 2016-03-08 17:28:46
○ 2016-06-29 12:58:36
○ 2026-06-28 15:31:12
○NSns.tradenames.com2015-11-24 → 2016-03-08 · 4 obs
● 2016-03-08 17:28:46
○ 2016-06-29 12:58:36
○ 2026-06-28 15:31:12
●NSns1.domainrecover.com2026-03-28 → 2026-06-28 · 3 obs
● 2026-03-28 17:18:38
● 2026-06-28 15:31:12
○NSns1.dsredirection.com2016-06-29 → 2016-06-29 · 4 obs
● 2016-06-29 12:58:36
○ 2017-02-15 12:49:46
○ 2026-06-28 15:31:12
●NSns2.domainrecover.com2026-03-28 → 2026-06-28 · 3 obs
● 2026-03-28 17:18:38
● 2026-06-28 15:31:12
○NSns2.dsredirection.com2016-06-29 → 2016-06-29 · 4 obs
● 2016-06-29 12:58:36
○ 2017-02-15 12:49:46
○ 2026-06-28 15:31:12
○A141.8.230.202016-06-29 → 2017-02-15 · 5 obs
● 2016-06-29 12:58:36
● 2017-02-15 12:49:46
○ 2019-03-14 20:07:02
○ 2026-06-28 15:31:12
○A64.20.35.1552008-03-19 → 2008-03-19 · 3 obs
○ 2015-08-05 10:07:12
○ 2026-06-28 15:31:12
○A66.45.246.1402015-11-24 → 2016-03-08 · 5 obs
● 2015-11-24 10:12:40
● 2016-03-08 17:28:46
○ 2016-06-29 12:58:36
○ 2026-06-28 15:31:12
●A66.45.246.1412026-03-28 → 2026-06-28 · 3 obs
● 2026-03-28 17:18:38
● 2026-06-28 15:31:12
○CNAMEpres.serverhome.com2016-06-29 → 2019-03-14 · 4 obs
● 2019-03-14 20:07:02
○ 2026-03-28 17:18:38
○ 2026-06-28 15:31:12
○CNAMEthie5ku9.dsgeneration.com2016-06-29 → 2016-06-29 · 3 obs
○ 2017-02-15 12:49:46
○ 2026-06-28 15:31:12
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | d.gtld-servers.net, g.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net... | - |
| comnetcom.com | ns1.domainrecover.com, ns2.domainrecover.com | 2 records |
✅ Authoritative Response
Server:149.248.38.58
NS records: ns1.domainrecover.com, ns2.domainrecover.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for comnetcom.com (unsigned zone)
⏱️ Timing
Total: 472ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 66.45.246.141 |
| NS | 2 | NS2.DOMAINRECOVER.com, NS1.DOMAINRECOVER.com |
| TXT | 1 | yGjyZf7SHD |
| SOA | 1 | ns1.domainrecover.com hostmaster.domainr |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.domainrecover.com, ns2.domainrecover.com)
Analysis
IP Addresses
comnetcom.com has exactly one IP address — 66.45.246.141.
itkomm.com, kompor.com, railcontainer.com plus two other host names have IP numbers in common with comnetcom.com.
Name Servers
comnetcom.com is served by two delegated name servers, ns1.domainrecover.com and ns2.domainrecover.com.
The name server configuration of comnetcom.com is shared with other domains, for instance tequenos.com, wunschtermin.com, new-host.com and two others.
comnetcom.com has at least partial name server overlap with other domains, such as didiz.com, vaurio.com, creafil.com and two others.
It is common to see these name servers used together with name servers ns1.serverhome.com and ns2.serverhome.com.
ns1.domainrecover.com directs to 149.248.38.58 and ns2.domainrecover.com directs to 199.247.16.62; each host name points to exactly one IP number.