bet33666.com - robtex.com
bet33666.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@bet33666.com serial=1608182103 | ||||||
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=1786023979 | ||||||
Same first word
bet33666.com |
Similar names
DNS History
12 records (6 active, 6 former)
○NSns52.bet33666.com2015-06-23 → 2016-06-20 · 4 obs
● 2016-06-20 19:42:36
○ 2017-02-13 14:32:26
○ 2026-08-06 14:14:38
○NSns53.bet33666.com2015-06-23 → 2016-06-20 · 4 obs
● 2016-06-20 19:42:36
○ 2017-02-13 14:32:26
○ 2026-08-06 14:14:38
○NSns54.bet33666.com2015-06-23 → 2016-06-20 · 4 obs
● 2016-06-20 19:42:36
○ 2017-02-13 14:32:26
○ 2026-08-06 14:14:38
●NSsnm1k0h.39899cne.com2016-06-20 → 2026-08-06 · 3 obs
● 2016-06-20 19:42:36
● 2026-08-06 14:14:38
●NSsnn3k0h.39899cne.com2016-06-20 → 2026-08-06 · 3 obs
● 2016-06-20 19:42:36
● 2026-08-06 14:14:38
●NSsnp2k0h.39899cne.com2016-06-20 → 2026-08-06 · 3 obs
● 2016-06-20 19:42:36
● 2026-08-06 14:14:38
●NSsnt4k0h.39899cne.com2016-06-20 → 2026-08-06 · 3 obs
● 2016-06-20 19:42:36
● 2026-08-06 14:14:38
○A103.224.96.1172016-02-23 → 2020-01-27 · 5 obs
● 2016-02-23 10:53:12
● 2020-01-27 00:46:24
○ 2026-08-02 05:54:46
○ 2026-08-06 14:14:38
○A103.241.10.842015-06-23 → 2015-11-02 · 4 obs
● 2015-11-02 02:34:04
○ 2016-02-23 10:53:12
○ 2026-08-06 14:14:38
●A103.241.28.1402026-08-02 → 2026-08-06 · 3 obs
● 2026-08-02 05:54:46
● 2026-08-06 14:14:38
○A2401:cf80:6038:7235:63d2:4964:fc18:2162020-01-27 → 2020-01-27 · 4 obs
● 2020-01-27 00:46:24
○ 2026-08-02 05:54:46
○ 2026-08-06 14:14:38
●A2405:1c0:6713:753:63d2:4964:fc18:2162026-08-02 → 2026-08-06 · 3 obs
● 2026-08-02 05:54:46
● 2026-08-06 14:14:38
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | e.gtld-servers.net, i.gtld-servers.net, d.gtld-servers.net, b.gtld-servers.net... | - |
| bet33666.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 bet33666.com (unsigned zone)
⏱️ Timing
Total: 517ms | 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.bet33666.com |
📌 Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (snt4k0h.39899cne.com, snt4k0h.39899cne.com, snn3k0h.39899cne.com...)
Analysis
IP Addresses
bet33666.com resolves to the IP addresses 103.241.28.140 and 2405:1c0:6713:753:63d2:4964:fc18:216
js867867.com, j22555.com, bet77555.com and two other host names share IP numbers with bet33666.com.
Name Servers
The authoritative name servers for bet33666.com are snm1k0h.39899cne.com, snn3k0h.39899cne.com, snp2k0h.39899cne.com and snt4k0h.39899cne.com.
bet33666.com has at least partial name server overlap with other domains, such as js857857.com, 89997vip19.com, 89997vip27.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 each resolve to two IP addresses: snm1k0h.39899cne.com resolves to 103.226.149.108 and 2405:1c0:6007:d055:9451:3dc2:41e6:578; snn3k0h.39899cne.com resolves to 135.84.241.211 and 2405:1c0:601e:f8e3:4e7f:237b:5c98:515; snp2k0h.39899cne.com resolves to 103.254.30.218 and 2405:1c0:605e:5229:a134:faf2:9dce:222.