cu2.com - dns.ninja
cu2.com
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=1782681545 | ||||||
Same first word
cu2.me |
cu2.us |
cu2.net |
cu2.org |
cu2.es |
cu2.com.au |
cu2.nu |
cu2.eu |
cu2.dk |
cu2.se |
cu2.fr |
cu2.it |
cu2.ir |
cu2.io |
cu2.nl |
cu2.de |
cu2.to |
cu2.com |
cu2.be |
cu2.co.nz |
cu2.mobi |
cu2.online |
Similar names
DNS History
19 records (8 active, 11 former)
○NSdns1.name-services.com2016-06-25 → 2016-12-21 · 5 obs
● 2016-06-25 07:59:06
● 2016-12-21 09:41:34
○ 2026-04-30 20:53:00
○ 2026-06-28 21:47:02
○NSdns2.name-services.com2016-06-25 → 2016-12-21 · 5 obs
● 2016-06-25 07:59:06
● 2016-12-21 09:41:34
○ 2026-04-30 20:53:00
○ 2026-06-28 21:47:02
○NSdns3.name-services.com2016-06-25 → 2016-12-21 · 5 obs
● 2016-06-25 07:59:06
● 2016-12-21 09:41:34
○ 2026-04-30 20:53:00
○ 2026-06-28 21:47:02
○NSdns4.name-services.com2016-06-25 → 2016-12-21 · 5 obs
● 2016-06-25 07:59:06
● 2016-12-21 09:41:34
○ 2026-04-30 20:53:00
○ 2026-06-28 21:47:02
○NSdns5.name-services.com2016-06-25 → 2016-12-21 · 5 obs
● 2016-06-25 07:59:06
● 2016-12-21 09:41:34
○ 2026-04-30 20:53:00
○ 2026-06-28 21:47:02
○NSns1.monikerdns.net2015-08-12 → 2016-05-01 · 4 obs
● 2016-05-01 12:59:28
○ 2016-06-25 07:59:06
○ 2026-06-28 21:47:02
●NSns1.name.com2026-04-30 → 2026-06-28 · 3 obs
● 2026-04-30 20:53:00
● 2026-06-28 21:47:02
●NSns1mpz.name.com2026-04-30 → 2026-06-28 · 3 obs
● 2026-04-30 20:53:00
● 2026-06-28 21:47:02
○NSns2.monikerdns.net2015-08-12 → 2016-05-01 · 4 obs
● 2016-05-01 12:59:28
○ 2016-06-25 07:59:06
○ 2026-06-28 21:47:02
●NSns2.name.com2026-04-30 → 2026-06-28 · 3 obs
● 2026-04-30 20:53:00
● 2026-06-28 21:47:02
●NSns2clp.name.com2026-04-30 → 2026-06-28 · 3 obs
● 2026-04-30 20:53:00
● 2026-06-28 21:47:02
○NSns3.monikerdns.net2015-08-12 → 2016-05-01 · 4 obs
● 2016-05-01 12:59:28
○ 2016-06-25 07:59:06
○ 2026-06-28 21:47:02
●NSns3.name.com2026-04-30 → 2026-06-28 · 3 obs
● 2026-04-30 20:53:00
● 2026-06-28 21:47:02
●NSns3ghw.name.com2026-04-30 → 2026-06-28 · 3 obs
● 2026-04-30 20:53:00
● 2026-06-28 21:47:02
○NSns4.monikerdns.net2015-08-12 → 2016-05-01 · 4 obs
● 2016-05-01 12:59:28
○ 2016-06-25 07:59:06
○ 2026-06-28 21:47:02
●NSns4.name.com2026-04-30 → 2026-06-28 · 3 obs
● 2026-04-30 20:53:00
● 2026-06-28 21:47:02
●NSns4dfh.name.com2026-04-30 → 2026-06-28 · 3 obs
● 2026-04-30 20:53:00
● 2026-06-28 21:47:02
○A5.22.149.1352015-08-12 → 2016-05-01 · 4 obs
● 2016-05-01 12:59:28
○ 2016-06-25 07:59:06
○ 2026-06-28 21:47:02
○A98.124.199.1072016-06-25 → 2016-12-21 · 5 obs
● 2016-06-25 07:59:06
● 2016-12-21 09:41:34
○ 2026-04-30 20:53:00
○ 2026-06-28 21:47:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net... | - |
| cu2.com | ns1mpz.name.com, ns2clp.name.com, ns3ghw.name.com, ns4dfh.name.com | 8 records |
✅ Authoritative Response
Server:163.114.217.49
NS records: ns1mpz.name.com, ns2clp.name.com, ns3ghw.name.com, ns4dfh.name.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for cu2.com (unsigned zone)
⏱️ Timing
Total: 164ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns1.name.com, ns2.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns1mpz.name.com, ns1mpz.name.com, ns2clp.name.com...)
Analysis
Name Servers
cu2.com has 8 name servers — ns1.name.com, ns1mpz.name.com, ns2.name.com and 5 others.
There is at least partial name server overlap between cu2.com and other domains — lim.email, beemark.com, mediamassa.com and two more among them.
These name servers regularly appear alongside ns3.name.com, ns4.name.com, ns3ghw.name.com and 7 other name servers in NS record sets.
Hostnames that resolve to two IP addresses:
ns1.name.com resolves to 163.114.216.17 and 2a00:edc0:107::1.
ns1mpz.name.com resolves to 163.114.216.17 and 2a00:edc0:107::1.
ns2.name.com resolves to 163.114.216.49 and 2402:cf80:107::1.
ns2clp.name.com resolves to 163.114.216.49 and 2402:cf80:107::1.
ns3.name.com resolves to 163.114.217.17 and 2a00:edc0:107::49.
ns3ghw.name.com resolves to 163.114.217.17 and 2a00:edc0:107::49.
ns4.name.com resolves to 163.114.217.49 and 2402:cf80:107::49.
ns4dfh.name.com resolves to 163.114.217.49 and 2402:cf80:107::49.
The host names ns1.name.com and ns1mpz.name.com both resolve to 2a00:edc0:107::1 IP addresses.
The host names ns1.name.com and ns1mpz.name.com both resolve to 163.114.216.17 IP addresses.
The host names ns2.name.com and ns2clp.name.com both resolve to 2402:cf80:107::1 IP addresses.
The host names ns2.name.com and ns2clp.name.com both resolve to 163.114.216.49 IP addresses.
The host names ns3.name.com and ns3ghw.name.com both resolve to 2a00:edc0:107::49 IP addresses.
The host names ns3.name.com and ns3ghw.name.com both resolve to 163.114.217.17 IP addresses.
The host names ns4.name.com and ns4dfh.name.com both resolve to 2402:cf80:107::49 IP addresses.
The host names ns4.name.com and ns4dfh.name.com both resolve to 163.114.217.49 IP addresses.