bet77333.com - robtex.com
bet77333.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 2405:1c0:6713:753:63d2:4964:fc18:216🇲🇾 WOODSNET-PH2405:1c0:6713::/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@bet77333.com serial=1608182077 | ||||||
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=1786046829 | ||||||
Same first word
bet77333.com |
Similar names
DNS History
8 records (6 active, 2 former)
○NSns52.bet77333.com2016-12-15 → 2016-12-15 · 3 obs
○ 2018-06-15 01:55:40
○ 2026-08-06 20:21:06
●NSsnm1k0h.39899cne.com2016-12-15 → 2026-08-06 · 2 obs
● 2026-08-06 20:21:06
●NSsnn3k0h.39899cne.com2016-12-15 → 2026-08-06 · 2 obs
● 2026-08-06 20:21:06
●NSsnp2k0h.39899cne.com2016-12-15 → 2026-08-06 · 2 obs
● 2026-08-06 20:21:06
●NSsnt4k0h.39899cne.com2016-12-15 → 2026-08-06 · 2 obs
● 2026-08-06 20:21:06
○A103.224.98.872016-12-15 → 2018-06-15 · 4 obs
● 2018-06-15 01:55:40
○ 2026-08-01 23:49:52
○ 2026-08-06 20:21:06
●A103.241.28.1402026-08-01 → 2026-08-06 · 3 obs
● 2026-08-01 23:49:52
● 2026-08-06 20:21:06
●A2405:1c0:6713:753:63d2:4964:fc18:2162026-08-01 → 2026-08-06 · 3 obs
● 2026-08-01 23:49:52
● 2026-08-06 20:21:06
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | h.gtld-servers.net, j.gtld-servers.net, d.gtld-servers.net, c.gtld-servers.net... | - |
| bet77333.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 bet77333.com (unsigned zone)
⏱️ Timing
Total: 532ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 103.241.28.140 |
| AAAA | 1 | 2405:1c0:6713:753:63d2:4964:fc18:216 |
| NS | 3 | snn3k0h.39899cne.com, snp2k0h.39899cne.com... |
| SOA | 1 | snp2k0h.39899cne.com root.bet77333.com |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (snt4k0h.39899cne.com, snt4k0h.39899cne.com, snn3k0h.39899cne.com...)
Analysis
IP Addresses
bet77333.com has two IP addresses: 103.241.28.140 and 2405:1c0:6713:753:63d2:4964:fc18:216
Additional host names — js812812.com, bet50000.com, js810810.com and two others — share IP numbers with bet77333.com.
Name Servers
bet77333.com has four authoritative name servers: snm1k0h.39899cne.com, snn3k0h.39899cne.com, snp2k0h.39899cne.com and snt4k0h.39899cne.com.
There is at least partial name server overlap between bet77333.com and other domains — js805805.com, 89997vip5.com, js817817.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.