bet50000.com - robtex.com
bet50000.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 2405:1c0:6711:753:6372:2af3:29b7:921🇲🇾 WOODSNET-PH2405:1c0:6711::/48 Customer Route | ||||||
| A | 103.241.28.140🇹🇭 WOODSNET-PH103.241.28.0/24 CMI (Customer Route) | ||||||
| NS | snp2k0h.39899cne.com ⭐ | ||||||
| A | 2405:1c0:605e:5229:a134:faf2:9dce:222🇲🇾 WOODSNET-PH2405:1c0:605e::/48 | ||||||
| A | 103.254.30.218🇮🇳 WOODSNET-PH103.254.30.0/24 CMI (Customer Route) | ||||||
| NS | snm1k0h.39899cne.com | ||||||
| A | 2405:1c0:6007:d055:9451:3dc2:41e6:578🇲🇾 WOODSNET-PH2405:1c0:6007::/48 | ||||||
| A | 103.226.149.108🇮🇳 WOODSNET-PH103.226.149.0/24 CMI (Customer Route) | ||||||
| NS | snn3k0h.39899cne.com | ||||||
| A | 2405:1c0:601e:f8e3:4e7f:237b:5c98:515🇲🇾 WOODSNET-PH2405:1c0:601e::/48 | ||||||
| A | 135.84.241.211🇮🇳 WOODSNET-PH135.84.241.0/24 CMI (Customer Route) | ||||||
| NS | snt4k0h.39899cne.com ⚠️ Not in zone NS records | ||||||
| SOA | snp2k0h.39899cne.comroot@bet50000.com serial=1608182090 | ||||||
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=1785998889 | ||||||
Same first word
bet50000.com |
DNS History
12 records (6 active, 6 former)
○NSns52.bet50000.com2015-06-19 → 2016-11-20 · 4 obs
● 2016-11-20 10:14:32
○ 2017-05-26 11:29:14
○ 2026-08-06 07:06:00
○NSns53.bet50000.com2015-06-19 → 2016-04-10 · 4 obs
● 2016-04-10 04:06:38
○ 2016-11-20 10:14:32
○ 2026-08-06 07:06:00
○NSns54.bet50000.com2015-06-19 → 2016-04-10 · 4 obs
● 2016-04-10 04:06:38
○ 2016-11-20 10:14:32
○ 2026-08-06 07:06:00
●NSsnm1k0h.39899cne.com2016-11-20 → 2026-08-06 · 3 obs
● 2016-11-20 10:14:32
● 2026-08-06 07:06:00
●NSsnn3k0h.39899cne.com2016-11-20 → 2026-08-06 · 3 obs
● 2016-11-20 10:14:32
● 2026-08-06 07:06:00
●NSsnp2k0h.39899cne.com2016-11-20 → 2026-08-06 · 3 obs
● 2016-11-20 10:14:32
● 2026-08-06 07:06:00
●NSsnt4k0h.39899cne.com2016-11-20 → 2026-08-06 · 3 obs
● 2016-11-20 10:14:32
● 2026-08-06 07:06:00
○A103.224.97.1052016-04-10 → 2017-05-26 · 5 obs
● 2016-04-10 04:06:38
● 2017-05-26 11:29:14
○ 2026-03-05 21:28:50
○ 2026-08-06 07:06:00
○A103.241.10.842015-06-19 → 2016-01-23 · 4 obs
● 2016-01-23 02:05:22
○ 2016-04-10 04:06:38
○ 2026-08-06 07:06:00
●A103.241.28.1402026-03-23 → 2026-08-06 · 3 obs
● 2026-03-23 01:58:02
● 2026-08-06 07:06:00
●A2405:1c0:6711:753:6372:2af3:29b7:9212026-03-05 → 2026-08-06 · 3 obs
● 2026-03-05 21:28:50
● 2026-08-06 07:06:00
○A43.246.146.372026-03-05 → 2026-03-09 · 5 obs
● 2026-03-05 21:28:50
● 2026-03-09 10:43:58
○ 2026-03-23 01:58:02
○ 2026-08-06 07:06:00
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | b.gtld-servers.net, i.gtld-servers.net, h.gtld-servers.net, g.gtld-servers.net... | - |
| bet50000.com | snt4k0h.39899cne.com, snn3k0h.39899cne.com, snm1k0h.39899cne.com, snp2k0h.39899cne.com | 8 records |
✅ Authoritative Response
Server:135.84.241.211
NS records: snt4k0h.39899cne.com, snn3k0h.39899cne.com, snm1k0h.39899cne.com, snp2k0h.39899cne.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for bet50000.com (unsigned zone)
⏱️ Timing
Total: 749ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 103.241.28.140 |
| AAAA | 1 | 2405:1c0:6711:753:6372:2af3:29b7:921 |
| NS | 3 | snp2k0h.39899cne.com, snm1k0h.39899cne.com... |
| SOA | 1 | snp2k0h.39899cne.com root.bet50000.com |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (snt4k0h.39899cne.com, snt4k0h.39899cne.com, snn3k0h.39899cne.com...)
Analysis
IP Addresses
bet50000.com has two IP addresses: 103.241.28.140 and 2405:1c0:6711:753:6372:2af3:29b7:921
Two other host names, along with js86622.com, 89997vip22.com and js860860.com, also share IP numbers with bet50000.com.
Name Servers
The NS records for bet50000.com point to four name servers: snm1k0h.39899cne.com, snn3k0h.39899cne.com, snp2k0h.39899cne.com and snt4k0h.39899cne.com.
There is at least partial name server overlap between bet50000.com and other domains — js867867.com, js850850.com, j22555.com and two more among them.
These name servers tend to appear in combination with the name servers snm1k0h.773773.vip, snn3k0h.773773.vip, snp2k0h.773773.vip and snt4k0h.773773.vip.
snm1k0h.39899cne.com, snn3k0h.39899cne.com and snp2k0h.39899cne.com all resolve to exactly two IP numbers apiece: snm1k0h.39899cne.com → 103.226.149.108 and 2405:1c0:6007:d055:9451:3dc2:41e6:578; snn3k0h.39899cne.com → 135.84.241.211 and 2405:1c0:601e:f8e3:4e7f:237b:5c98:515; snp2k0h.39899cne.com → 103.254.30.218 and 2405:1c0:605e:5229:a134:faf2:9dce:222.