leesle.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`leesle.com`

DNSSEC	⚠️ Not signed
A	183.111.139.227^{🇰🇷 KT-NET183.104.0.0/13 KORNET KOREA TELECOM}
A	203.245.12.98^{🇰🇷 KT-NET203.245.0.0/18 contact chejumen@hitel.net if necessary contact country1@hitel.net if necessary contact express@hitel.net if necessary contact ezmate@hitel.net if necessary contact han322@hitel.net if necessary}
A	203.245.12.113^{🇰🇷 KT-NET203.245.0.0/18 contact chejumen@hitel.net if necessary contact country1@hitel.net if necessary contact express@hitel.net if necessary contact ezmate@hitel.net if necessary contact han322@hitel.net if necessary}
A	203.245.12.121^{🇰🇷 KT-NET203.245.0.0/18 contact chejumen@hitel.net if necessary contact country1@hitel.net if necessary contact express@hitel.net if necessary contact ezmate@hitel.net if necessary contact han322@hitel.net if necessary}
NS	`leesle.com` ⭐
		A	183.111.139.227^{🇰🇷 KT-NET183.104.0.0/13 KORNET KOREA TELECOM}
		A	203.245.12.98^{🇰🇷 KT-NET203.245.0.0/18 contact chejumen@hitel.net if necessary contact country1@hitel.net if necessary contact express@hitel.net if necessary contact ezmate@hitel.net if necessary contact han322@hitel.net if necessary}
		A	203.245.12.113^{🇰🇷 KT-NET203.245.0.0/18 contact chejumen@hitel.net if necessary contact country1@hitel.net if necessary contact express@hitel.net if necessary contact ezmate@hitel.net if necessary contact han322@hitel.net if necessary}
		A	203.245.12.121^{🇰🇷 KT-NET203.245.0.0/18 contact chejumen@hitel.net if necessary contact country1@hitel.net if necessary contact express@hitel.net if necessary contact ezmate@hitel.net if necessary contact han322@hitel.net if necessary}
NS	`dns1.cafe24.co.kr` ⚠️ Not in zone NS records
		A	112.175.246.228^{🇰🇷 KT-NET112.168.0.0/13}
		A	112.175.246.229^{🇰🇷 KT-NET112.168.0.0/13}
		A	175.125.93.132^{🇰🇷 SKB-NET175.120.0.0/13 SKB summary}
		A	175.125.93.133^{🇰🇷 SKB-NET175.120.0.0/13 SKB summary}
NS	`dns1.cafe24.com` ⚠️ Not in zone NS records
		A	112.175.246.226^{🇰🇷 KT-NET112.168.0.0/13}
		A	112.175.246.227^{🇰🇷 KT-NET112.168.0.0/13}
		A	175.125.93.130^{🇰🇷 SKB-NET175.120.0.0/13 SKB summary}
		A	175.125.93.131^{🇰🇷 SKB-NET175.120.0.0/13 SKB summary}
NS	`ns1.cafe24.co.kr` ⚠️ Not in parent delegation
		A	112.175.246.232^{🇰🇷 KT-NET112.168.0.0/13}
			PTR	`gjit.kr`
			PTR	`snoweb.kr`
			PTR	`sinc2030.co.kr`
		A	112.175.246.233^{🇰🇷 KT-NET112.168.0.0/13}
		A	175.125.93.136^{🇰🇷 SKB-NET175.120.0.0/13 SKB summary}
		A	175.125.93.137^{🇰🇷 SKB-NET175.120.0.0/13 SKB summary}
NS	`ns1.cafe24.com` ⚠️ Not in parent delegation
		A	112.175.246.230^{🇰🇷 KT-NET112.168.0.0/13}
		A	112.175.246.231^{🇰🇷 KT-NET112.168.0.0/13}
		A	116.126.143.242^{🇰🇷 SKB-NET116.126.0.0/16 SK Broadband}
		A	175.125.93.134^{🇰🇷 SKB-NET175.120.0.0/13 SKB summary}
		A	175.125.93.135^{🇰🇷 SKB-NET175.120.0.0/13 SKB summary}
NS	`ns2.cafe24.co.kr` ⚠️ Not in parent delegation
		A	112.175.247.232^{🇰🇷 KT-NET112.168.0.0/13}
			PTR	`snoweb.kr`
			PTR	`sarchi.co.kr`
		A	112.175.247.233^{🇰🇷 KT-NET112.168.0.0/13}
		A	175.125.93.146^{🇰🇷 SKB-NET175.120.0.0/13 SKB summary}
		A	175.125.93.147^{🇰🇷 SKB-NET175.120.0.0/13 SKB summary}
NS	`ns2.cafe24.com` ⚠️ Not in parent delegation
		A	1.226.85.4^{🇰🇷 SKB-NET1.224.0.0/13 auto-generated route object for 1.224.0.0/13}
		A	1.234.0.4^{🇰🇷 SKB-NET1.232.0.0/13 auto-generated route object for 1.232.0.0/13}
		A	112.175.11.4^{🇰🇷 KT-NET112.168.0.0/13}
		A	112.175.12.4^{🇰🇷 KT-NET112.168.0.0/13}
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c19::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bk-in-f27.1e100.net`
		A	192.178.155.26^{🇺🇸 Google192.178.155.0/24}
			PTR	`yuiadrs-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.26^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁶⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹¹⁾
		A	2a00:1450:400c:c23::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`v=spf1 include:mail.stibee.com ~all`
TXT	`google-site-verification=jBE7QaPON3fn9uIWXPfgYEmC7jO1zCEgJPEzGh-UbGM`
SOA	`leesle.com`postmaster@leesle.com serial=20140625

`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.net`nstld@verisign-grs.com serial=1786905849

📈 Tranco rank: #965,276

NS for

leesle.com

Subdomains

m.leesle.com

Same first word

leesle.com

leesle.kr

Similar names

elesel.com

eseell.com

ellese.com

eseell.biz

eleles.com

eselle.com

elsele.de

leslee.workers.dev

leslee.de

eseell.net

sleele.com

ellsee.my

selele.cn

lesele.com

lesele.com.cn

selele.com

ellsee.com

leslee.nl

leslee.co.uk

eseell.org

leesel.com

DNS History

19 records (16 active, 3 former)

●NSdns1.cafe24.co.kr2026-03-26 → 2026-08-16 · 3 obs

○ 2017-04-10 02:38:10
● 2026-03-26 14:05:14
● 2026-08-16 19:13:02

●NSdns1.cafe24.com2026-03-26 → 2026-08-16 · 3 obs

○ 2017-04-10 02:38:10
● 2026-03-26 14:05:14
● 2026-08-16 19:13:02

●NSleesle.com2015-07-21 → 2026-08-16 · 2 obs

● 2015-07-21 20:11:12
● 2026-08-16 19:13:02

●NSns1.cafe24.co.kr2015-07-21 → 2026-08-16 · 4 obs

● 2015-07-21 20:11:12
● 2017-04-10 02:38:10
○ 2026-03-26 14:05:14
● 2026-08-16 19:13:02

●NSns1.cafe24.com2015-07-21 → 2026-08-16 · 4 obs

● 2015-07-21 20:11:12
● 2017-04-10 02:38:10
○ 2026-03-26 14:05:14
● 2026-08-16 19:13:02

●NSns2.cafe24.co.kr2015-07-21 → 2026-08-16 · 4 obs

● 2015-07-21 20:11:12
● 2017-04-10 02:38:10
○ 2026-03-26 14:05:14
● 2026-08-16 19:13:02

●NSns2.cafe24.com2015-07-21 → 2026-08-16 · 4 obs

● 2015-07-21 20:11:12
● 2017-04-10 02:38:10
○ 2026-03-26 14:05:14
● 2026-08-16 19:13:02

●MXalt1.aspmx.l.google.com2026-03-26 → 2026-08-16 · 3 obs

○ 2017-04-10 02:38:10
● 2026-03-26 14:05:14
● 2026-08-16 19:13:02

●MXalt2.aspmx.l.google.com2026-03-26 → 2026-08-16 · 3 obs

○ 2017-04-10 02:38:10
● 2026-03-26 14:05:14
● 2026-08-16 19:13:02

●MXalt3.aspmx.l.google.com2026-03-26 → 2026-08-16 · 3 obs

○ 2017-04-10 02:38:10
● 2026-03-26 14:05:14
● 2026-08-16 19:13:02

●MXalt4.aspmx.l.google.com2026-03-26 → 2026-08-16 · 3 obs

○ 2017-04-10 02:38:10
● 2026-03-26 14:05:14
● 2026-08-16 19:13:02

●MXaspmx.l.google.com2026-03-26 → 2026-08-16 · 3 obs

○ 2017-04-10 02:38:10
● 2026-03-26 14:05:14
● 2026-08-16 19:13:02

○MXaspmx1.naver.com2015-07-21 → 2017-04-10 · 4 obs

● 2015-07-21 20:11:12
● 2017-04-10 02:38:10
○ 2026-03-26 14:05:14
○ 2026-08-16 19:13:02

○MXaspmx2.naver.com2015-07-21 → 2017-04-10 · 4 obs

● 2015-07-21 20:11:12
● 2017-04-10 02:38:10
○ 2026-03-26 14:05:14
○ 2026-08-16 19:13:02

●A183.111.139.2272026-03-26 → 2026-08-16 · 3 obs

○ 2017-04-10 02:38:10
● 2026-03-26 14:05:14
● 2026-08-16 19:13:02

○A183.111.163.1432015-07-21 → 2017-04-10 · 4 obs

● 2015-07-21 20:11:12
● 2017-04-10 02:38:10
○ 2026-03-26 14:05:14
○ 2026-08-16 19:13:02

●A203.245.12.1132026-03-26 → 2026-08-16 · 3 obs

○ 2017-04-10 02:38:10
● 2026-03-26 14:05:14
● 2026-08-16 19:13:02

●A203.245.12.1212026-03-26 → 2026-08-16 · 3 obs

○ 2017-04-10 02:38:10
● 2026-03-26 14:05:14
● 2026-08-16 19:13:02

●A203.245.12.982026-03-26 → 2026-08-16 · 3 obs

○ 2017-04-10 02:38:10
● 2026-03-26 14:05:14
● 2026-08-16 19:13:02

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	m.gtld-servers.net, g.gtld-servers.net, f.gtld-servers.net, k.gtld-servers.net...	-
leesle.com	dns1.cafe24.com, dns1.cafe24.co.kr	4 records

✅ Authoritative Response

Server:112.175.246.226

NS records: dns1.cafe24.com, dns1.cafe24.co.kr

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for leesle.com (unsigned zone)

⏱️ Timing

Total: 3438ms | Queries: -

📄 Records

Type	Count	Sample Data
A	4	`203.245.12.121, 183.111.139.227...`
NS	4	`ns1.cafe24.co.kr, ns1.cafe24.com...`
MX	5	`ALT3.ASPMX.L.GOOGLE.com (pri: 10), ASPMX.L.GOOGLE.com (pri: 1)...`
TXT	2	`v=spf1 include:mail.stibee.com ~all, google-site-verification=jBE7QaPON3fn9uI`
SOA	1	`leesle.com postmaster.leesle.com`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (dns1.cafe24.com, dns1.cafe24.com, dns1.cafe24.com...)

Analysis

Hierarchy

leesle.com is the parent zone for m.leesle.com.

Name Server Role

leesle.com has leesle.com as one of its name servers, making it self-hosted for DNS delegation.

dns1.cafe24.com, dns1.cafe24.co.kr and leesle.com regularly act as name servers together.

IP Addresses

leesle.com has four IP addresses: 183.111.139.227, 203.245.12.98, 203.245.12.113 and 203.245.12.121.

Among the host names that share IP numbers with leesle.com are suubc.kr, asigo.kr, herbnare.com and two others.

Name Servers

leesle.com is authoritative under 7 name servers: leesle.com, dns1.cafe24.com, ns1.cafe24.com and 4 more.

leesle.com partially shares its NS delegation with several other domains, including essography.com, donbennet.com, joolife.co.kr and two others.

In DNS configurations, these name servers often share authority with ns2.cafe24.com, ns1.cafe24.co.kr, ns2.cafe24.co.kr and 4 other name servers.

Hostnames that point to five IP numbers:

ns1.cafe24.com directs to 112.175.246.230, 112.175.246.231, 116.126.143.242 and two other IP addresses.

Hosts pointing to four IP addresses:

leesle.com maps to the following IP addresses: 183.111.139.227, 203.245.12.98, 203.245.12.113 and 203.245.12.121.

dns1.cafe24.com maps to the following IP addresses: 112.175.246.226, 112.175.246.227, 175.125.93.130 and 175.125.93.131.

ns2.cafe24.com maps to the following IP addresses: 1.226.85.4, 1.234.0.4, 112.175.11.4 and 112.175.12.4.

dns1.cafe24.co.kr maps to the following IP addresses: 112.175.246.228, 112.175.246.229, 175.125.93.132 and 175.125.93.133.

ns1.cafe24.co.kr maps to the following IP addresses: 112.175.246.232, 112.175.246.233, 175.125.93.136 and 175.125.93.137.

ns2.cafe24.co.kr maps to the following IP addresses: 112.175.247.232, 112.175.247.233, 175.125.93.146 and 175.125.93.147.

Mail Servers

Mail for leesle.com is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

leesle.com shares at least some of its mail servers with other domains — for example ns500754.ns500754.ns500754.ns500671.ns500705.ns500704.ns500705.ns500671.ns500671.ns500678.ns500649.ns500291.ns500666.ns500653.ns500153.tenderladiesbz.com, ns500693.ns500693.ns500699.ns500693.ns500699.ns500693.ns500699.ns500693.ns500699.ns500588.ns500588.ns500693.ns500693.ns500612.ns500632.ns500588.ns500588.ns500588.dtrkdll.com, ns500758.ns500758.ns500698.ns500698.ns500698.ns500735.ns500735.ns500735.ns500698.ns500735.ns500735.ns500576.ns500576.ns500652.ns500576.trackreceptor.com and two more.

It is common for these mail servers to co-occur with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com as mail servers.

Hosts with two IP numbers each:

aspmx.l.google.com resolves to two addresses: 192.178.155.26 and 2607:f8b0:4004:c19::1b.

alt1.aspmx.l.google.com resolves to two addresses: 192.178.234.26 and 2800:3f0:4003:c14::1b.

alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.27 and 2a00:1450:400b:c02::1a.

alt3.aspmx.l.google.com resolves to two addresses: 192.178.223.27 and 2a00:1450:4009:c0f::1b.

alt4.aspmx.l.google.com resolves to two addresses: 172.253.157.27 and 2a00:1450:400c:c23::1a.