keyf5.com - dns.ninja

`keyf5.com`

DNSSEC	⚠️ Not signed
A	222.122.86.139^{🇰🇷 KT-NET222.122.0.0/16 Korea Telecom, Seoul, Korea}
NS	`keyf5.com` ⭐
		A	222.122.86.139^{🇰🇷 KT-NET222.122.0.0/16 Korea Telecom, Seoul, Korea}
NS	`ns1.cafe24.co.kr`
		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`
		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`
		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`
		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	`bn64-033.cafe24.com` ⭐
		A	222.122.86.139^{🇰🇷 KT-NET222.122.0.0/16 Korea Telecom, Seoul, Korea}
TXT	`v=spf1 ip4:222.122.86.139 ~all`
SOA	`keyf5.com`postmaster@keyf5.com serial=20220214

`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=1785892894

NS for

keyf5.com

Same first word

keyf5.com

DNS History

21 records (7 active, 14 former)

○NSdns1.registrar-servers.com2016-03-06 → 2017-02-09 · 4 obs

● 2016-03-06 02:53:54
● 2017-02-09 08:35:00
○ 2019-04-11 09:48:02
○ 2026-08-05 01:29:36

○NSdns2.registrar-servers.com2016-03-06 → 2017-02-09 · 4 obs

● 2016-03-06 02:53:54
● 2017-02-09 08:35:00
○ 2019-04-11 09:48:02
○ 2026-08-05 01:29:36

○NSdns3.registrar-servers.com2016-03-06 → 2017-02-09 · 4 obs

● 2016-03-06 02:53:54
● 2017-02-09 08:35:00
○ 2019-04-11 09:48:02
○ 2026-08-05 01:29:36

○NSdns4.registrar-servers.com2016-03-06 → 2017-02-09 · 4 obs

● 2016-03-06 02:53:54
● 2017-02-09 08:35:00
○ 2019-04-11 09:48:02
○ 2026-08-05 01:29:36

○NSdns5.registrar-servers.com2016-03-06 → 2017-02-09 · 4 obs

● 2016-03-06 02:53:54
● 2017-02-09 08:35:00
○ 2019-04-11 09:48:02
○ 2026-08-05 01:29:36

●NSkeyf5.com2026-03-02 → 2026-08-05 · 3 obs

○ 2019-04-11 09:48:02
● 2026-03-02 10:09:56
● 2026-08-05 01:29:36

●NSns1.cafe24.co.kr2026-03-02 → 2026-08-05 · 3 obs

○ 2019-04-11 09:48:02
● 2026-03-02 10:09:56
● 2026-08-05 01:29:36

●NSns1.cafe24.com2026-03-02 → 2026-08-05 · 3 obs

○ 2019-04-11 09:48:02
● 2026-03-02 10:09:56
● 2026-08-05 01:29:36

●NSns2.cafe24.co.kr2026-03-02 → 2026-08-05 · 3 obs

○ 2019-04-11 09:48:02
● 2026-03-02 10:09:56
● 2026-08-05 01:29:36

●NSns2.cafe24.com2026-03-02 → 2026-08-05 · 3 obs

○ 2019-04-11 09:48:02
● 2026-03-02 10:09:56
● 2026-08-05 01:29:36

○NSns4.wixdns.net2019-04-11 → 2019-04-11 · 4 obs

○ 2017-02-09 08:35:00
● 2019-04-11 09:48:02
○ 2026-03-02 10:09:56
○ 2026-08-05 01:29:36

○NSns5.wixdns.net2019-04-11 → 2019-04-11 · 4 obs

○ 2017-02-09 08:35:00
● 2019-04-11 09:48:02
○ 2026-03-02 10:09:56
○ 2026-08-05 01:29:36

●MXbn64-033.cafe24.com2026-03-02 → 2026-08-05 · 3 obs

○ 2019-04-11 09:48:02
● 2026-03-02 10:09:56
● 2026-08-05 01:29:36

○MXeforward1.registrar-servers.com2016-03-06 → 2017-02-09 · 4 obs

● 2016-03-06 02:53:54
● 2017-02-09 08:35:00
○ 2019-04-11 09:48:02
○ 2026-08-05 01:29:36

○MXeforward2.registrar-servers.com2016-03-06 → 2017-02-09 · 4 obs

● 2016-03-06 02:53:54
● 2017-02-09 08:35:00
○ 2019-04-11 09:48:02
○ 2026-08-05 01:29:36

○MXeforward3.registrar-servers.com2016-03-06 → 2017-02-09 · 4 obs

● 2016-03-06 02:53:54
● 2017-02-09 08:35:00
○ 2019-04-11 09:48:02
○ 2026-08-05 01:29:36

○MXeforward4.registrar-servers.com2016-03-06 → 2017-02-09 · 4 obs

● 2016-03-06 02:53:54
● 2017-02-09 08:35:00
○ 2019-04-11 09:48:02
○ 2026-08-05 01:29:36

○MXeforward5.registrar-servers.com2016-03-06 → 2017-02-09 · 4 obs

● 2016-03-06 02:53:54
● 2017-02-09 08:35:00
○ 2019-04-11 09:48:02
○ 2026-08-05 01:29:36

○A162.255.119.2492016-03-06 → 2017-02-09 · 4 obs

● 2016-03-06 02:53:54
● 2017-02-09 08:35:00
○ 2019-04-11 09:48:02
○ 2026-08-05 01:29:36

●A222.122.86.1392026-03-02 → 2026-08-05 · 3 obs

○ 2019-04-11 09:48:02
● 2026-03-02 10:09:56
● 2026-08-05 01:29:36

○A23.236.62.1472019-04-11 → 2019-04-11 · 4 obs

○ 2017-02-09 08:35:00
● 2019-04-11 09:48:02
○ 2026-03-02 10:09:56
○ 2026-08-05 01:29:36

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, i.gtld-servers.net, e.gtld-servers.net, j.gtld-servers.net...	-
keyf5.com	ns2.cafe24.com, ns1.cafe24.com, ns2.cafe24.co.kr, ns1.cafe24.co.kr	9 records

✅ Authoritative Response

Server:112.175.247.233

NS records: ns2.cafe24.com, ns1.cafe24.com, ns2.cafe24.co.kr, ns1.cafe24.co.kr

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for keyf5.com (unsigned zone)

⏱️ Timing

Total: 1281ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`222.122.86.139`
NS	4	`ns1.cafe24.co.kr, ns2.cafe24.com...`
MX	1	`bn64-033.cafe24.com (pri: 10)`
TXT	1	`v=spf1 ip4:222.122.86.139 ~all`
SOA	1	`keyf5.com postmaster.keyf5.com`

📌 Glue Records Collected

Total: 9

Out-of-bailiwick: 9 (ns2.cafe24.com, ns2.cafe24.com, ns2.cafe24.com...)

Analysis

Name Server Role

keyf5.com acts as a name server for keyf5.com, meaning it is self-referentially delegated.

keyf5.com is commonly paired with ns1.cafe24.com, ns2.cafe24.com and ns1.cafe24.co.kr to act as name servers.

IP Addresses

keyf5.com resolves to one IP address: 222.122.86.139.

tewoo.co.kr, surimtech.com, suseongmint.com and two other host names share IP numbers with keyf5.com.

Name Servers

Five name servers are authoritative for keyf5.com, which are keyf5.com, ns1.cafe24.com, ns2.cafe24.com and two others.

At least some of keyf5.com's name servers are shared with other domains, for example chairplus.com, jocompany.co.kr, mece.co.kr and two more.

These name servers tend to co-occur with ns2.cafe24.co.kr, ns.cafe24.com, ns0.cafe24.com and 6 other name servers in the same DNS delegations.

Hostnames pointing to five IP numbers:

ns1.cafe24.com resolves to four IP addresses: 112.175.246.230, 112.175.246.231, 116.126.143.242 and two others.

Hosts that point to four IP numbers:

ns2.cafe24.com directs to 1.226.85.4, 1.234.0.4, 112.175.11.4 and 112.175.12.4.

ns1.cafe24.co.kr directs to 112.175.246.232, 112.175.246.233, 175.125.93.136 and 175.125.93.137.

ns2.cafe24.co.kr directs to 112.175.247.232, 112.175.247.233, 175.125.93.146 and 175.125.93.147.

Hosts with just one IP address:

keyf5.com directs to 222.122.86.139.

Mail Servers

Mail for keyf5.com is handled by a single mail server, bn64-033.cafe24.com.

keyf5.com uses an identical mail server configuration to several other domains — among them saehanhitec.com, mulsafe.com, asempsy.com and two more.

bn64-033.cafe24.com has exactly one IP number: 222.122.86.139.