my666.cc - robtex.com
my666.cc
| CNAME | url.gname.net | ||||||
| DNSSEC | ⚠️ Not signed | ||||||
| A | 172.65.235.97🇺🇸 Cloudflare172.65.224.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
cc
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ac1.nstld.com ⭐ | ||||||
| NS | ac2.nstld.com | ||||||
| NS | ac3.nstld.com | ||||||
| NS | ac4.nstld.com | ||||||
| SOA | ac1.nstld.cominfo@verisign-grs.com serial=1785081640 | ||||||
Same first word
Similar names
DNS History
7 records (5 active, 2 former)
●NSa.share-dns.com2026-07-26 → 2026-07-26 · 2 obs
○ 2018-05-17 18:10:30
● 2026-07-26 16:38:06
● 2026-07-26 16:38:06
●NSb.share-dns.net2026-07-26 → 2026-07-26 · 2 obs
○ 2018-05-17 18:10:30
● 2026-07-26 16:38:06
● 2026-07-26 16:38:06
○NSdns29.hichina.com2018-05-17 → 2018-05-17 · 2 obs
● 2018-05-17 18:10:30
○ 2026-07-26 16:38:06
○ 2026-07-26 16:38:06
○NSdns30.hichina.com2018-05-17 → 2018-05-17 · 2 obs
● 2018-05-17 18:10:30
○ 2026-07-26 16:38:06
○ 2026-07-26 16:38:06
●NSns1.gname-dns.com2026-07-26 → 2026-07-26 · 2 obs
○ 2018-05-17 18:10:30
● 2026-07-26 16:38:06
● 2026-07-26 16:38:06
●NSns2.gname-dns.com2026-07-26 → 2026-07-26 · 2 obs
○ 2018-05-17 18:10:30
● 2026-07-26 16:38:06
● 2026-07-26 16:38:06
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| cc | ac1.nstld.com, ac2.nstld.com, ac3.nstld.com, ac4.nstld.com | - |
| my666.cc | ns2.gname-dns.com, ns1.gname-dns.com | - |
✅ Authoritative Response
Server:172.64.52.212
NS records: ns2.gname-dns.com, ns1.gname-dns.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for my666.cc (unsigned zone)
⏱️ Timing
Total: 193ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | a.share-dns.com, b.share-dns.net |
| CNAME | 1 | url.gname.net |
| SOA | 1 | a.share-dns.com master.share-dns.com |
Analysis
IP Addresses
my666.cc resolves to just one IP address, 172.65.235.97.
Two other host names, along with url.gname.net, get.nic.ec.cc and get.nic.us.cc, also share IP numbers with my666.cc.