hmydt.com - robtex.com
hmydt.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 223.82.108.187🇨🇳 CMNET-Jiangxi-AP223.82.108.0/24 CMI (Customer Route) | ||||||
| NS | dns3.4cun.com ⭐ | ||||||
| A | 2408:4005:3dc:af00:a6be:339e:a1a0:d2b8🇨🇳 Alibaba-Cloud2408:4005::/33 | ||||||
| A | 61.172.183.74🇨🇳 SHANGHAITELECOM61.172.182.0/23 SHIDC | ||||||
| NS | dns.4cun.com ⚠️ Not in zone NS records | ||||||
| NS | dns4.51dns.top ⚠️ Not in zone NS records | ||||||
| A | 2408:4005:3dc:af00:a6be:339e:a1a0:d2b8🇨🇳 Alibaba-Cloud2408:4005::/33 | ||||||
| A | 219.138.102.210🇨🇳 CHINATELECOM-HUBEI-YICHANG-IDC219.138.102.0/24 yichang | ||||||
| SOA | dns.4cun.comadmin@hmydt.com serial=1779938397 | ||||||
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=1785045822 | ||||||
Same first word
hmydt.com |
Similar names
dmhty.com |
hdymt.com |
mhtyd.com |
dyhtm.com |
hydmt.com |
mtdyh.com |
myhdt.com |
ythmd.cn |
dhymt.com |
mthyd.com |
mydth.de |
mytdh.com |
hdmyt.info |
hytdm.com |
myhdt.de |
mhtdy.com |
hdmyt.xyz |
mtyhd.org |
mydth.ca |
yhdtm.blogspot.com |
DNS History
18 records (4 active, 14 former)
●NSdns.4cun.com2026-05-18 → 2026-07-26 · 3 obs
○ 2020-01-23 04:43:18
● 2026-05-18 07:39:00
● 2026-07-26 06:09:10
● 2026-05-18 07:39:00
● 2026-07-26 06:09:10
○NSdns1.everdns.com2015-06-11 → 2016-01-25 · 4 obs
● 2015-06-11 21:46:46
● 2016-01-25 02:58:54
○ 2016-04-23 06:56:58
○ 2026-07-26 06:09:10
● 2016-01-25 02:58:54
○ 2016-04-23 06:56:58
○ 2026-07-26 06:09:10
○NSdns2.everdns.com2015-06-11 → 2016-01-25 · 4 obs
● 2015-06-11 21:46:46
● 2016-01-25 02:58:54
○ 2016-04-23 06:56:58
○ 2026-07-26 06:09:10
● 2016-01-25 02:58:54
○ 2016-04-23 06:56:58
○ 2026-07-26 06:09:10
●NSdns3.4cun.com2026-05-18 → 2026-07-26 · 3 obs
○ 2020-01-23 04:43:18
● 2026-05-18 07:39:00
● 2026-07-26 06:09:10
● 2026-05-18 07:39:00
● 2026-07-26 06:09:10
●NSdns4.51dns.top2026-05-18 → 2026-07-26 · 3 obs
○ 2020-01-23 04:43:18
● 2026-05-18 07:39:00
● 2026-07-26 06:09:10
● 2026-05-18 07:39:00
● 2026-07-26 06:09:10
○NSjm1.dns.com2020-01-23 → 2020-01-23 · 4 obs
○ 2017-03-25 09:51:50
● 2020-01-23 04:43:18
○ 2026-05-18 07:39:00
○ 2026-07-26 06:09:10
● 2020-01-23 04:43:18
○ 2026-05-18 07:39:00
○ 2026-07-26 06:09:10
○NSjm2.dns.com2020-01-23 → 2020-01-23 · 4 obs
○ 2017-03-25 09:51:50
● 2020-01-23 04:43:18
○ 2026-05-18 07:39:00
○ 2026-07-26 06:09:10
● 2020-01-23 04:43:18
○ 2026-05-18 07:39:00
○ 2026-07-26 06:09:10
○NSjuming.dnsdun.com2016-09-01 → 2016-09-01 · 4 obs
○ 2016-04-23 06:56:58
● 2016-09-01 04:30:10
○ 2017-03-25 09:51:50
○ 2026-07-26 06:09:10
● 2016-09-01 04:30:10
○ 2017-03-25 09:51:50
○ 2026-07-26 06:09:10
○NSjuming.dnsdun.net2016-09-01 → 2016-09-01 · 4 obs
○ 2016-04-23 06:56:58
● 2016-09-01 04:30:10
○ 2017-03-25 09:51:50
○ 2026-07-26 06:09:10
● 2016-09-01 04:30:10
○ 2017-03-25 09:51:50
○ 2026-07-26 06:09:10
○NSns1.eedns.com2017-03-25 → 2017-03-25 · 4 obs
○ 2016-09-01 04:30:10
● 2017-03-25 09:51:50
○ 2020-01-23 04:43:18
○ 2026-07-26 06:09:10
● 2017-03-25 09:51:50
○ 2020-01-23 04:43:18
○ 2026-07-26 06:09:10
○NSns2.eedns.com2017-03-25 → 2017-03-25 · 4 obs
○ 2016-09-01 04:30:10
● 2017-03-25 09:51:50
○ 2020-01-23 04:43:18
○ 2026-07-26 06:09:10
● 2017-03-25 09:51:50
○ 2020-01-23 04:43:18
○ 2026-07-26 06:09:10
○A103.56.102.92016-09-01 → 2016-09-01 · 4 obs
○ 2016-04-23 06:56:58
● 2016-09-01 04:30:10
○ 2017-03-25 09:51:50
○ 2026-07-26 06:09:10
● 2016-09-01 04:30:10
○ 2017-03-25 09:51:50
○ 2026-07-26 06:09:10
○A107.148.223.342017-03-25 → 2017-03-25 · 4 obs
○ 2016-09-01 04:30:10
● 2017-03-25 09:51:50
○ 2020-01-23 04:43:18
○ 2026-07-26 06:09:10
● 2017-03-25 09:51:50
○ 2020-01-23 04:43:18
○ 2026-07-26 06:09:10
○A156.227.38.2352020-01-23 → 2020-01-23 · 4 obs
○ 2017-03-25 09:51:50
● 2020-01-23 04:43:18
○ 2026-05-18 07:39:00
○ 2026-07-26 06:09:10
● 2020-01-23 04:43:18
○ 2026-05-18 07:39:00
○ 2026-07-26 06:09:10
●A223.82.108.1872026-05-18 → 2026-07-26 · 3 obs
○ 2020-01-23 04:43:18
● 2026-05-18 07:39:00
● 2026-07-26 06:09:10
● 2026-05-18 07:39:00
● 2026-07-26 06:09:10
○A69.165.73.262015-06-11 → 2015-06-11 · 3 obs
● 2015-06-11 21:46:46
○ 2026-05-18 07:39:00
○ 2026-07-26 06:09:10
○ 2026-05-18 07:39:00
○ 2026-07-26 06:09:10
○A69.165.73.302015-10-31 → 2016-01-25 · 5 obs
○ 2015-06-11 21:46:46
● 2015-10-31 12:19:06
● 2016-01-25 02:58:54
○ 2016-04-23 06:56:58
○ 2026-07-26 06:09:10
● 2015-10-31 12:19:06
● 2016-01-25 02:58:54
○ 2016-04-23 06:56:58
○ 2026-07-26 06:09:10
○CNAMEhk3.vnetdns.com2015-06-11 → 2016-01-25 · 4 obs
● 2015-06-11 21:46:46
● 2016-01-25 02:58:54
○ 2016-04-23 06:56:58
○ 2026-07-26 06:09:10
● 2016-01-25 02:58:54
○ 2016-04-23 06:56:58
○ 2026-07-26 06:09:10
🔍 DNS Trace
Analysis
IP Addresses
hmydt.com resolves to just one IP address, 223.82.108.187.
Name Servers
hmydt.com carries NS records delegating to dns3.4cun.com, dns.4cun.com and dns4.51dns.top.
The name servers of hmydt.com overlap at least partially with those of other domains — among them 245sf.com, 1sic.com, 273sf.com and two more.
These name servers commonly appear in delegations together with dns7.4cun.com, dns1.4cun.com, dns2.51dns.top and 7 other.
Both dns3.4cun.com and dns4.51dns.top have two IP addresses each. dns3.4cun.com resolves to 61.172.183.74 and 2408:4005:3dc:af00:a6be:339e:a1a0:d2b8; dns4.51dns.top resolves to 219.138.102.210 and 2408:4005:3dc:af00:a6be:339e:a1a0:d2b8.
dns3.4cun.com along with dns4.51dns.top each resolve to 2408:4005:3dc:af00:a6be:339e:a1a0:d2b8 IP addresses.