3chm.com - robtex.com
3chm.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 45.203.70.93🇭🇰 HDHK45.203.64.0/21 Proxy-registered route object | ||||||
| NS | ns1.julydns.com ⭐ ⚠️ Not in parent delegation | ||||||
| A | 47.97.51.45🇨🇳 Alibaba-Cloud47.96.0.0/15 Aliyun Computing Co., LTD | ||||||
| NS | ns1.judns.com ⚠️ Not in zone NS records | ||||||
| A | 47.97.51.45🇨🇳 Alibaba-Cloud47.96.0.0/15 Aliyun Computing Co., LTD | ||||||
| NS | ns2.judns.com ⚠️ Not in zone NS records | ||||||
| A | 162.159.27.251Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns2.julydns.com ⚠️ Not in parent delegation | ||||||
| A | 162.159.48.223Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| SOA | ns1.julydns.commaster@jmdns.com serial=1765702994 | ||||||
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=1774387587 | ||||||
Same first word
3chm.com |
Similar names
DNS History
17 records (5 active, 12 former)
●NSns1.judns.com2026-03-09 → 2026-03-24 · 3 obs
○ 2018-01-12 19:55:04
● 2026-03-09 23:52:50
● 2026-03-24 21:37:32
● 2026-03-09 23:52:50
● 2026-03-24 21:37:32
●NSns1.julydns.com2026-03-09 → 2026-03-24 · 3 obs
○ 2018-01-12 19:55:04
● 2026-03-09 23:52:50
● 2026-03-24 21:37:32
● 2026-03-09 23:52:50
● 2026-03-24 21:37:32
○NSns1cnb.domain-resolution.net2017-01-08 → 2017-01-08 · 3 obs
● 2017-01-08 13:47:18
○ 2018-01-12 19:55:04
○ 2026-03-24 21:37:32
○ 2018-01-12 19:55:04
○ 2026-03-24 21:37:32
○NSns1cnb.name.com2018-01-12 → 2018-01-12 · 4 obs
○ 2017-01-08 13:47:18
● 2018-01-12 19:55:04
○ 2026-03-09 23:52:50
○ 2026-03-24 21:37:32
● 2018-01-12 19:55:04
○ 2026-03-09 23:52:50
○ 2026-03-24 21:37:32
●NSns2.judns.com2026-03-09 → 2026-03-24 · 3 obs
○ 2018-01-12 19:55:04
● 2026-03-09 23:52:50
● 2026-03-24 21:37:32
● 2026-03-09 23:52:50
● 2026-03-24 21:37:32
●NSns2.julydns.com2026-03-09 → 2026-03-24 · 3 obs
○ 2018-01-12 19:55:04
● 2026-03-09 23:52:50
● 2026-03-24 21:37:32
● 2026-03-09 23:52:50
● 2026-03-24 21:37:32
○NSns2dqx.domain-resolution.net2017-01-08 → 2017-01-08 · 3 obs
● 2017-01-08 13:47:18
○ 2018-01-12 19:55:04
○ 2026-03-24 21:37:32
○ 2018-01-12 19:55:04
○ 2026-03-24 21:37:32
○NSns2dqx.name.com2018-01-12 → 2018-01-12 · 4 obs
○ 2017-01-08 13:47:18
● 2018-01-12 19:55:04
○ 2026-03-09 23:52:50
○ 2026-03-24 21:37:32
● 2018-01-12 19:55:04
○ 2026-03-09 23:52:50
○ 2026-03-24 21:37:32
○NSns3cna.domain-resolution.net2017-01-08 → 2017-01-08 · 3 obs
● 2017-01-08 13:47:18
○ 2018-01-12 19:55:04
○ 2026-03-24 21:37:32
○ 2018-01-12 19:55:04
○ 2026-03-24 21:37:32
○NSns3cna.name.com2018-01-12 → 2018-01-12 · 4 obs
○ 2017-01-08 13:47:18
● 2018-01-12 19:55:04
○ 2026-03-09 23:52:50
○ 2026-03-24 21:37:32
● 2018-01-12 19:55:04
○ 2026-03-09 23:52:50
○ 2026-03-24 21:37:32
○NSns4fpy.domain-resolution.net2017-01-08 → 2017-01-08 · 3 obs
● 2017-01-08 13:47:18
○ 2018-01-12 19:55:04
○ 2026-03-24 21:37:32
○ 2018-01-12 19:55:04
○ 2026-03-24 21:37:32
○NSns4fpy.name.com2018-01-12 → 2018-01-12 · 4 obs
○ 2017-01-08 13:47:18
● 2018-01-12 19:55:04
○ 2026-03-09 23:52:50
○ 2026-03-24 21:37:32
● 2018-01-12 19:55:04
○ 2026-03-09 23:52:50
○ 2026-03-24 21:37:32
○MXin1-smtp.messagingengine.com2017-01-08 → 2018-01-12 · 4 obs
● 2017-01-08 13:47:18
● 2018-01-12 19:55:04
○ 2026-03-09 23:52:50
○ 2026-03-24 21:37:32
● 2018-01-12 19:55:04
○ 2026-03-09 23:52:50
○ 2026-03-24 21:37:32
○MXin2-smtp.messagingengine.com2017-01-08 → 2018-01-12 · 4 obs
● 2017-01-08 13:47:18
● 2018-01-12 19:55:04
○ 2026-03-09 23:52:50
○ 2026-03-24 21:37:32
● 2018-01-12 19:55:04
○ 2026-03-09 23:52:50
○ 2026-03-24 21:37:32
○A158.69.124.2132017-01-08 → 2017-01-08 · 3 obs
● 2017-01-08 13:47:18
○ 2018-01-12 19:55:04
○ 2026-03-24 21:37:32
○ 2018-01-12 19:55:04
○ 2026-03-24 21:37:32
○A173.212.206.1512018-01-12 → 2018-01-12 · 4 obs
○ 2017-01-08 13:47:18
● 2018-01-12 19:55:04
○ 2026-03-09 23:52:50
○ 2026-03-24 21:37:32
● 2018-01-12 19:55:04
○ 2026-03-09 23:52:50
○ 2026-03-24 21:37:32
●A45.203.70.932026-03-09 → 2026-03-24 · 3 obs
○ 2018-01-12 19:55:04
● 2026-03-09 23:52:50
● 2026-03-24 21:37:32
● 2026-03-09 23:52:50
● 2026-03-24 21:37:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | e.gtld-servers.net, g.gtld-servers.net, l.gtld-servers.net, a.gtld-servers.net... | - |
| 3chm.com | ns1.judns.com, ns2.judns.com | 2 records |
✅ Authoritative Response
Server:162.159.27.251
NS records: ns1.judns.com, ns2.judns.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for 3chm.com (unsigned zone)
⏱️ Timing
Total: 357ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 45.203.70.93 |
| NS | 2 | ns1.julydns.com, ns2.julydns.com |
| SOA | 1 | ns1.julydns.com master.jmdns.com |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns1.judns.com, ns2.judns.com)
Analysis
IP Addresses
3chm.com points to a single IP number: 45.203.70.93.
Name Servers
3chm.com is delegated to four name servers: ns1.judns.com, ns2.judns.com, ns1.julydns.com and ns2.julydns.com.
3chm.com at least partially shares name servers with other domains, for instance pjfsdd.cn, jnlvshi.cn, qmid.cn, hrjsw.cn and swyang.com.
These name servers are commonly used with the name servers jm1.dns.com.
Host names with one IP number:
ns1.judns.com points to 47.97.51.45.
ns2.judns.com points to 162.159.27.251.
ns1.julydns.com points to 47.97.51.45.
ns2.julydns.com points to 162.159.48.223.
Host names pointing to 47.97.51.45: ns1.judns.com and ns1.julydns.com.