ylgmy.com - robtex.com
ylgmy.com
| DNSSEC | ⚠️ Not signed | ||||||
| A | 160.124.233.158🇿🇦 POWERLINE-HK160.124.224.0/20 Proxy-registered route object | ||||||
| NS | ns1.julydns.com ⭐ ⚠️ Not in parent delegation | ||||||
| A | 162.159.48.223Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | ns1.onclouddns.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 | ||||||
| NS | ns2.onclouddns.com ⚠️ Not in zone NS records | ||||||
| A | 162.159.27.251Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| SOA | ns1.julydns.commaster@jmdns.com serial=1776855711 | ||||||
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=1777204346 | ||||||
Same first word
ylgmy.com |
Similar names
yymlg.com |
gymyl.com |
ymgyl.com |
mylyg.com |
myygl.org |
gymly.ru |
lygym.com |
gylmy.com |
lygym.net |
myylg.com |
gylym.com |
mylyg.cn |
mlyyg.com |
ygylm.com |
glymy.com |
gyylm.com |
lygym.tw |
mygyl.com |
gylym.kz |
lgymy.top |
DNS History
20 records (5 active, 15 former)
○NSns1.judns.com2026-03-17 → 2026-04-16 · 5 obs
○ 2017-04-19 23:49:52
● 2026-03-17 18:27:26
● 2026-04-16 18:47:06
○ 2026-04-26 12:02:44
○ 2026-04-26 12:02:46
● 2026-03-17 18:27:26
● 2026-04-16 18:47:06
○ 2026-04-26 12:02:44
○ 2026-04-26 12:02:46
●NSns1.julydns.com2026-03-17 → 2026-04-26 · 3 obs
○ 2017-04-19 23:49:52
● 2026-03-17 18:27:26
● 2026-04-26 12:02:46
● 2026-03-17 18:27:26
● 2026-04-26 12:02:46
○NSns1.myhostadmin.net2015-05-07 → 2017-04-19 · 4 obs
● 2015-05-07 01:13:00
● 2017-04-19 23:49:52
○ 2026-03-17 18:27:26
○ 2026-04-26 12:02:46
● 2017-04-19 23:49:52
○ 2026-03-17 18:27:26
○ 2026-04-26 12:02:46
●NSns1.onclouddns.com2026-04-26 → 2026-04-26 · 3 obs
○ 2026-04-16 18:47:06
● 2026-04-26 12:02:44
● 2026-04-26 12:02:46
● 2026-04-26 12:02:44
● 2026-04-26 12:02:46
○NSns2.judns.com2026-03-17 → 2026-04-16 · 5 obs
○ 2017-04-19 23:49:52
● 2026-03-17 18:27:26
● 2026-04-16 18:47:06
○ 2026-04-26 12:02:44
○ 2026-04-26 12:02:46
● 2026-03-17 18:27:26
● 2026-04-16 18:47:06
○ 2026-04-26 12:02:44
○ 2026-04-26 12:02:46
●NSns2.julydns.com2026-03-17 → 2026-04-26 · 3 obs
○ 2017-04-19 23:49:52
● 2026-03-17 18:27:26
● 2026-04-26 12:02:46
● 2026-03-17 18:27:26
● 2026-04-26 12:02:46
○NSns2.myhostadmin.net2015-05-07 → 2017-04-19 · 4 obs
● 2015-05-07 01:13:00
● 2017-04-19 23:49:52
○ 2026-03-17 18:27:26
○ 2026-04-26 12:02:46
● 2017-04-19 23:49:52
○ 2026-03-17 18:27:26
○ 2026-04-26 12:02:46
●NSns2.onclouddns.com2026-04-26 → 2026-04-26 · 3 obs
○ 2026-04-16 18:47:06
● 2026-04-26 12:02:44
● 2026-04-26 12:02:46
● 2026-04-26 12:02:44
● 2026-04-26 12:02:46
○NSns3.myhostadmin.net2015-05-07 → 2017-04-19 · 4 obs
● 2015-05-07 01:13:00
● 2017-04-19 23:49:52
○ 2026-03-17 18:27:26
○ 2026-04-26 12:02:46
● 2017-04-19 23:49:52
○ 2026-03-17 18:27:26
○ 2026-04-26 12:02:46
○NSns4.myhostadmin.net2015-05-07 → 2017-04-19 · 4 obs
● 2015-05-07 01:13:00
● 2017-04-19 23:49:52
○ 2026-03-17 18:27:26
○ 2026-04-26 12:02:46
● 2017-04-19 23:49:52
○ 2026-03-17 18:27:26
○ 2026-04-26 12:02:46
○NSns5.myhostadmin.net2015-05-07 → 2017-04-19 · 4 obs
● 2015-05-07 01:13:00
● 2017-04-19 23:49:52
○ 2026-03-17 18:27:26
○ 2026-04-26 12:02:46
● 2017-04-19 23:49:52
○ 2026-03-17 18:27:26
○ 2026-04-26 12:02:46
○NSns6.myhostadmin.net2015-05-07 → 2017-04-19 · 4 obs
● 2015-05-07 01:13:00
● 2017-04-19 23:49:52
○ 2026-03-17 18:27:26
○ 2026-04-26 12:02:46
● 2017-04-19 23:49:52
○ 2026-03-17 18:27:26
○ 2026-04-26 12:02:46
○A103.41.65.1642026-03-17 → 2026-04-16 · 5 obs
○ 2017-04-19 23:49:52
● 2026-03-17 18:27:26
● 2026-04-16 18:47:06
○ 2026-04-26 12:02:44
○ 2026-04-26 12:02:46
● 2026-03-17 18:27:26
● 2026-04-16 18:47:06
○ 2026-04-26 12:02:44
○ 2026-04-26 12:02:46
○A116.255.205.692016-09-11 → 2016-09-11 · 4 obs
○ 2015-12-16 18:43:06
● 2016-09-11 18:14:16
○ 2017-04-19 23:49:52
○ 2026-04-26 12:02:46
● 2016-09-11 18:14:16
○ 2017-04-19 23:49:52
○ 2026-04-26 12:02:46
○A116.255.205.732015-05-07 → 2015-12-16 · 4 obs
● 2015-05-07 01:13:00
● 2015-12-16 18:43:06
○ 2016-09-11 18:14:16
○ 2026-04-26 12:02:46
● 2015-12-16 18:43:06
○ 2016-09-11 18:14:16
○ 2026-04-26 12:02:46
○A116.255.235.252017-04-19 → 2017-04-19 · 4 obs
○ 2016-09-11 18:14:16
● 2017-04-19 23:49:52
○ 2026-03-17 18:27:26
○ 2026-04-26 12:02:46
● 2017-04-19 23:49:52
○ 2026-03-17 18:27:26
○ 2026-04-26 12:02:46
●A160.124.233.1582026-04-26 → 2026-04-26 · 3 obs
○ 2026-04-16 18:47:06
● 2026-04-26 12:02:44
● 2026-04-26 12:02:46
● 2026-04-26 12:02:44
● 2026-04-26 12:02:46
○CNAMEftp.bgp82.vhostgo.com2017-04-19 → 2017-04-19 · 4 obs
○ 2016-09-11 18:14:16
● 2017-04-19 23:49:52
○ 2026-03-17 18:27:26
○ 2026-04-26 12:02:46
● 2017-04-19 23:49:52
○ 2026-03-17 18:27:26
○ 2026-04-26 12:02:46
○CNAMEftp.zz73.vhostgo.com2015-10-11 → 2016-09-11 · 5 obs
○ 2015-05-07 01:13:00
● 2015-10-11 14:01:52
● 2016-09-11 18:14:16
○ 2017-04-19 23:49:52
○ 2026-04-26 12:02:46
● 2015-10-11 14:01:52
● 2016-09-11 18:14:16
○ 2017-04-19 23:49:52
○ 2026-04-26 12:02:46
○CNAMEzhangxuefei.gotoftp1.com2015-05-07 → 2017-04-19 · 4 obs
● 2015-05-07 01:13:00
● 2017-04-19 23:49:52
○ 2026-03-17 18:27:26
○ 2026-04-26 12:02:46
● 2017-04-19 23:49:52
○ 2026-03-17 18:27:26
○ 2026-04-26 12:02:46
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| ylgmy.com | ns1.onclouddns.com, ns2.onclouddns.com | 2 records |
✅ Authoritative Response
Server:162.159.27.251
NS records: ns1.onclouddns.com, ns2.onclouddns.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for ylgmy.com (unsigned zone)
⏱️ Timing
Total: 271ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 160.124.233.158 |
| 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.onclouddns.com, ns2.onclouddns.com)
Analysis
IP Addresses
ylgmy.com resolves to one IP number: 160.124.233.158.
Other host names, for instance hrbmhkj.com, share IP numbers with ylgmy.com.
Name Servers
ylgmy.com is delegated to four name servers: ns1.julydns.com, ns2.julydns.com, ns1.onclouddns.com and ns2.onclouddns.com.
ylgmy.com at least partially shares name servers with other domains, for instance sdodun.com, maokai.net, umpaycz.cn, gnsby.com and homehappy.com.cn.
These name servers are commonly used alongside ns1.judns.com and ns2.judns.com.
Host names with a single IP:
ns1.julydns.com points to 162.159.48.223.
ns2.julydns.com points to 162.159.48.223.
ns1.onclouddns.com points to 162.159.27.251.
ns2.onclouddns.com points to 162.159.27.251.
Host names pointing to 162.159.48.223: ns1.julydns.com and ns2.julydns.com.
Host names pointing to 162.159.27.251: ns1.onclouddns.com and ns2.onclouddns.com.