vv5002.com - robtex.com
vv5002.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 2405:1c0:6414:404:ff49:130b:b5f1:733🇲🇾 WOODSNET-PH2405:1c0:6414::/48 Customer Route | ||||||
| A | 165.84.198.144🇮🇳 WOODSNET-PH165.84.198.0/24 Customer Route | ||||||
| NS | snp2bxs.s889cne.com ⭐ | ||||||
| A | 2405:1c0:605e:5229:a134:faf2:9dce:208🇲🇾 WOODSNET-PH2405:1c0:605e::/48 | ||||||
| A | 103.254.30.31🇮🇳 WOODSNET-PH103.254.30.0/24 CMI (Customer Route) | ||||||
| NS | snm1bxs.s889cne.com | ||||||
| A | 2405:1c0:6007:d055:9451:3dc2:41e6:598🇲🇾 WOODSNET-PH2405:1c0:6007::/48 | ||||||
| A | 103.241.77.103🇰🇷 WOODSNET-PH103.241.76.0/22 Customer Route | ||||||
| NS | snn3bxs.s889cne.com | ||||||
| A | 2405:1c0:601e:f8e3:4e7f:237b:5c98:32🇲🇾 WOODSNET-PH2405:1c0:601e::/48 | ||||||
| A | 103.241.118.96🇰🇷 WOODSNET-PH103.241.118.0/24 CMI (Customer Route) | ||||||
| NS | snt4bxs.s889cne.com ⚠️ Not in zone NS records | ||||||
| SOA | snp2bxs.s889cne.comroot@vv5002.com serial=2008290070 | ||||||
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=1785727397 | ||||||
Same first word
vv5002.com |
Similar names
DNS History
11 records (6 active, 5 former)
○NSns4.dnsdun.com2016-12-14 → 2016-12-14 · 3 obs
○ 2017-08-21 22:02:02
○ 2026-08-03 03:29:46
○NSns5.dnsdun.com2017-08-21 → 2017-08-21 · 4 obs
● 2017-08-21 22:02:02
○ 2026-08-02 16:40:00
○ 2026-08-03 03:29:46
○NSns5.dnsdun.net2016-12-14 → 2017-08-21 · 4 obs
● 2017-08-21 22:02:02
○ 2026-08-02 16:40:00
○ 2026-08-03 03:29:46
●NSsnm1bxs.s889cne.com2026-08-02 → 2026-08-03 · 3 obs
● 2026-08-02 16:40:00
● 2026-08-03 03:29:46
●NSsnn3bxs.s889cne.com2026-08-02 → 2026-08-03 · 3 obs
● 2026-08-02 16:40:00
● 2026-08-03 03:29:46
●NSsnp2bxs.s889cne.com2026-08-02 → 2026-08-03 · 3 obs
● 2026-08-02 16:40:00
● 2026-08-03 03:29:46
●NSsnt4bxs.s889cne.com2026-08-02 → 2026-08-03 · 3 obs
● 2026-08-02 16:40:00
● 2026-08-03 03:29:46
●A165.84.198.1442026-08-02 → 2026-08-03 · 2 obs
● 2026-08-03 03:29:46
●A2405:1c0:6414:404:ff49:130b:b5f1:7332026-08-02 → 2026-08-03 · 2 obs
● 2026-08-03 03:29:46
○CNAMEbw002-01.pt.alicdn-kr.com2016-12-14 → 2016-12-14 · 3 obs
○ 2017-08-21 22:02:02
○ 2026-08-03 03:29:46
○CNAMEbw002.oo.dnsbaidu.com2017-08-21 → 2017-08-21 · 4 obs
● 2017-08-21 22:02:02
○ 2026-08-02 16:40:00
○ 2026-08-03 03:29:46
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | g.gtld-servers.net, f.gtld-servers.net, k.gtld-servers.net, b.gtld-servers.net... | - |
| vv5002.com | snm1bxs.s889cne.com, snp2bxs.s889cne.com, snn3bxs.s889cne.com, snt4bxs.s889cne.com | 8 records |
✅ Authoritative Response
Server:103.241.118.96
NS records: snm1bxs.s889cne.com, snp2bxs.s889cne.com, snn3bxs.s889cne.com, snt4bxs.s889cne.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for vv5002.com (unsigned zone)
⏱️ Timing
Total: 1889ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 165.84.198.144 |
| AAAA | 1 | 2405:1c0:6414:404:ff49:130b:b5f1:733 |
| NS | 3 | snn3bxs.s889cne.com, snp2bxs.s889cne.com... |
| SOA | 1 | snp2bxs.s889cne.com root.vv5002.com |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (snm1bxs.s889cne.com, snm1bxs.s889cne.com, snp2bxs.s889cne.com...)
Analysis
IP Addresses
vv5002.com has two IP addresses: 165.84.198.144 and 2405:1c0:6414:404:ff49:130b:b5f1:733
44335316.com, 50038833.com, 66555156.com and two other host names share IP numbers with vv5002.com.
Name Servers
The authoritative name servers for vv5002.com are snm1bxs.s889cne.com, snn3bxs.s889cne.com, snp2bxs.s889cne.com and snt4bxs.s889cne.com.
At least some of vv5002.com's name servers are shared with other domains, for example s5002.com, 88005003.com, 36665156.com and two more.
snm1bxs.s889cne.com, snn3bxs.s889cne.com and snp2bxs.s889cne.com all resolve to exactly two IP numbers apiece: snm1bxs.s889cne.com → 103.241.77.103 and 2405:1c0:6007:d055:9451:3dc2:41e6:598; snn3bxs.s889cne.com → 103.241.118.96 and 2405:1c0:601e:f8e3:4e7f:237b:5c98:32; snp2bxs.s889cne.com → 103.254.30.31 and 2405:1c0:605e:5229:a134:faf2:9dce:208.