eplady.com - dns.ninja

eplady.com

DNSSEC⚠️ Not signed
A202.8.123.26🇨🇳 harry-ASN202.8.120.0/22 HONG KONG KOWLOON TELECOMMUNICATIONS CO.,LIMITED 68 Tong Mei Road, Mong Kok, Hong Kong Room 0107, block a, Fuqiang industrial building
NSns1.julydns.com ⭐ ⚠️ Not in parent delegation
A162.159.48.223Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US
NSns1.judns.com ⚠️ Not in zone NS records
A162.159.27.251Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
NSns2.judns.com ⚠️ Not in zone NS records
A162.159.27.251Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
NSns2.julydns.com ⚠️ Not in parent delegation
A162.159.48.223Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US
SOAns1.julydns.commaster@jmdns.com serial=1779077648

com

DNSSEC🔒 Signed (DS record present)
NSa.gtld-servers.net ⭐
NSb.gtld-servers.net
NSc.gtld-servers.net
NSd.gtld-servers.net
NSe.gtld-servers.net
NSf.gtld-servers.net
NSg.gtld-servers.net
NSh.gtld-servers.net
NSi.gtld-servers.net
NSj.gtld-servers.net
NSk.gtld-servers.net
NSl.gtld-servers.net
NSm.gtld-servers.net
SOAa.gtld-servers.netnstld@verisign-grs.com serial=1782837406

Same first word

eplady.com

Similar names

delpay.com
deplay.fun
played.xyz
deplay.de
played.ru
pleyad.fr
paydel.com
played.it
played.us
playde.com
ypadel.es
played.ca
deplay.com
depaly.de
edplay.biz
ledpay.ru
pleyad.com
playde.de
deplay.co.kr
played.com
playde.link
delpay.net
played.co.uk
ypedal.org
played.at
pleady.com
played.today
elpyda.com
apyled.com
played.se
pleyad.org
leadyp.com
played.pl
ledyap.com
deaply.com
depyla.com
pedaly.com
ypedal.com
deplay.ru
played.ch
edplay.online
aplyde.com
elpady.com
played.df.gov.br
played.biz
ypadel.com
dayple.com
pedaly.cz
played.be
pleyad.net
played.no
ledayp.com
ladype.com
played.by
padley.com
played.net
played.to
pedaly.pl
padley.net
aplyed.com
played.co
deplay.net
paydle.com

DNS History

16 records (5 active, 11 former)

20162017201820192020202120222023202420252026NSns1.judns.comns1.julydns.comns2.judns.comns2.julydns.comdns1.iidns.comns1.22.cnns2.22.cnns3.22.cnns4.22.cnA202.8.123.26103.214.164.252103.56.102.94202.61.84.17264.62.224.253CNAME51owner.comdns1.yumi18.com
○NSdns1.iidns.com2017-07-24 → 2017-07-24 · 4 obs
○ 2017-07-22 13:53:10
● 2017-07-24 03:36:30
○ 2026-02-27 05:21:52
○ 2026-06-30 17:00:32
○NSns1.22.cn2016-03-01 → 2016-03-01 · 3 obs
● 2016-03-01 07:11:28
○ 2017-07-22 13:53:10
○ 2026-06-30 17:00:32
●NSns1.judns.com2026-02-27 → 2026-06-30 · 3 obs
○ 2017-07-24 03:36:30
● 2026-02-27 05:21:52
● 2026-06-30 17:00:32
●NSns1.julydns.com2026-02-27 → 2026-06-30 · 3 obs
○ 2017-07-24 03:36:30
● 2026-02-27 05:21:52
● 2026-06-30 17:00:32
○NSns2.22.cn2016-03-01 → 2016-03-01 · 3 obs
● 2016-03-01 07:11:28
○ 2017-07-22 13:53:10
○ 2026-06-30 17:00:32
●NSns2.judns.com2026-02-27 → 2026-06-30 · 3 obs
○ 2017-07-24 03:36:30
● 2026-02-27 05:21:52
● 2026-06-30 17:00:32
●NSns2.julydns.com2026-02-27 → 2026-06-30 · 3 obs
○ 2017-07-24 03:36:30
● 2026-02-27 05:21:52
● 2026-06-30 17:00:32
○NSns3.22.cn2016-03-01 → 2016-03-01 · 3 obs
● 2016-03-01 07:11:28
○ 2017-07-22 13:53:10
○ 2026-06-30 17:00:32
○NSns4.22.cn2016-03-01 → 2016-03-01 · 3 obs
● 2016-03-01 07:11:28
○ 2017-07-22 13:53:10
○ 2026-06-30 17:00:32
○A103.214.164.2522026-04-02 → 2026-04-02 · 4 obs
○ 2017-07-22 13:53:10
● 2026-04-02 13:47:24
○ 2026-04-20 05:56:16
○ 2026-06-30 17:00:32
○A103.56.102.942016-03-01 → 2016-03-01 · 4 obs
○ 2015-11-25 17:15:56
● 2016-03-01 07:11:28
○ 2017-07-22 13:53:10
○ 2026-06-30 17:00:32
○A202.61.84.1722026-04-26 → 2026-05-15 · 5 obs
○ 2026-04-20 05:56:16
● 2026-04-26 10:19:16
● 2026-05-15 04:22:18
○ 2026-06-17 18:27:36
○ 2026-06-30 17:00:32
●A202.8.123.262026-06-17 → 2026-06-30 · 3 obs
○ 2026-05-15 04:22:18
● 2026-06-17 18:27:36
● 2026-06-30 17:00:32
○A64.62.224.2532015-07-06 → 2015-11-25 · 4 obs
● 2015-07-06 06:53:38
● 2015-11-25 17:15:56
○ 2016-03-01 07:11:28
○ 2026-06-30 17:00:32
○CNAME51owner.com2016-03-01 → 2016-03-01 · 3 obs
● 2016-03-01 07:11:28
○ 2017-07-22 13:53:10
○ 2026-06-30 17:00:32
○CNAMEdns1.yumi18.com2017-07-24 → 2017-07-24 · 4 obs
○ 2017-07-22 13:53:10
● 2017-07-24 03:36:30
○ 2026-02-27 05:21:52
○ 2026-06-30 17:00:32

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
comh.gtld-servers.net, f.gtld-servers.net, j.gtld-servers.net, l.gtld-servers.net...-
eplady.comns1.judns.com, ns2.judns.com2 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 eplady.com (unsigned zone)

⏱️ Timing

Total: 273ms | Queries: -

📄 Records

TypeCountSample Data
A1202.8.123.26
NS2ns1.julydns.com, ns2.julydns.com
SOA1ns1.julydns.com master.jmdns.com

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.judns.com, ns2.judns.com)

Analysis

IP Addresses

eplady.com directs to one IP number, which is 202.8.123.26.

Among the host names that share IP numbers with eplady.com are uer88.com, aatp.com, aijuzhenwang.cn and two others.

Name Servers

The domain eplady.com is delegated to these four name servers: ns1.judns.com, ns2.judns.com, ns1.julydns.com and ns2.julydns.com.

eplady.com has at least partial name server overlap with other domains, such as sdepartment.com, 829332.cn, creuea.cn and two others.

It is common to see these name servers used together with name servers ns1.onclouddns.com and ns2.onclouddns.com.

Each of ns1.judns.com, ns2.judns.com, ns1.julydns.com and ns2.julydns.com has a single IP address — ns1.judns.com and ns2.judns.com direct to 162.159.27.251, and ns1.julydns.com and ns2.julydns.com direct to 162.159.48.223.

These two host names — ns1.judns.com and ns2.judns.com — each point to 162.159.27.251 IP addresses.

These two host names — ns1.julydns.com and ns2.julydns.com — each point to 162.159.48.223 IP addresses.