bet53333.com - robtex.com
bet53333.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 2405:1c0:6714:753:4bfe:533:597e:34🇲🇾 WOODSNET-PH2405:1c0:6714::/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@bet53333.com serial=1608182104 | ||||||
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=1786104684 | ||||||
Same first word
bet53333.com |
Similar names
DNS History
8 records (6 active, 2 former)
○NSns52.bet53333.com2016-12-15 → 2016-12-15 · 3 obs
○ 2017-06-25 04:43:00
○ 2026-08-07 12:20:28
●NSsnm1k0h.39899cne.com2016-12-15 → 2026-08-07 · 2 obs
● 2026-08-07 12:20:28
●NSsnn3k0h.39899cne.com2016-12-15 → 2026-08-07 · 2 obs
● 2026-08-07 12:20:28
●NSsnp2k0h.39899cne.com2016-12-15 → 2026-08-07 · 2 obs
● 2026-08-07 12:20:28
●NSsnt4k0h.39899cne.com2016-12-15 → 2026-08-07 · 2 obs
● 2026-08-07 12:20:28
○A103.224.96.1172016-12-15 → 2017-06-25 · 4 obs
● 2017-06-25 04:43:00
○ 2026-08-01 23:21:44
○ 2026-08-07 12:20:28
●A103.241.28.1402026-08-01 → 2026-08-07 · 3 obs
● 2026-08-01 23:21:44
● 2026-08-07 12:20:28
●A2405:1c0:6714:753:4bfe:533:597e:342026-08-01 → 2026-08-07 · 3 obs
● 2026-08-01 23:21:44
● 2026-08-07 12:20:28
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | h.gtld-servers.net, g.gtld-servers.net, f.gtld-servers.net, k.gtld-servers.net... | - |
| bet53333.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 bet53333.com (unsigned zone)
⏱️ Timing
Total: 609ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 103.241.28.140 |
| AAAA | 1 | 2405:1c0:6714:753:4bfe:533:597e:34 |
| NS | 3 | snn3k0h.39899cne.com, snp2k0h.39899cne.com... |
| SOA | 1 | snp2k0h.39899cne.com root.bet53333.com |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (snt4k0h.39899cne.com, snt4k0h.39899cne.com, snn3k0h.39899cne.com...)
Analysis
IP Addresses
bet53333.com resolves to the IP addresses 103.241.28.140 and 2405:1c0:6714:753:4bfe:533:597e:34
Among the host names that share IP numbers with bet53333.com are 89997vip8.com, js848848.com, jshvip7.com and two others.
Name Servers
The domain bet53333.com is delegated to these four name servers: snm1k0h.39899cne.com, snn3k0h.39899cne.com, snp2k0h.39899cne.com and snt4k0h.39899cne.com.
bet53333.com has at least partial name server overlap with other domains, such as jshvip4.com, j11555.com, 89997vip4.com and two others.
It is common to find these name servers paired 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.