`whyhsk.com`

DNSSEC	⚠️ Not signed
A	183.111.242.13^{🇰🇷 KT-NET183.104.0.0/13 KORNET KOREA TELECOM}
NS	`ns1.bdm.microsoftonline.com` ⭐
		A	2603:1061:0:700::d0^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-208.azure-dns.com`
		A	13.107.236.208^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-208.azure-dns.com`
NS	`ns2.bdm.microsoftonline.com`
		A	2620:1ec:8ec:700::d0^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-208.azure-dns.net`
		A	150.171.21.208^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-208.azure-dns.net`
NS	`ns3.bdm.microsoftonline.com`
		A	2a01:111:4000:700::d0^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-208.azure-dns.org`
		A	204.14.183.208^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-208.azure-dns.org`
NS	`ns4.bdm.microsoftonline.com`
		A	2620:1ec:bda:700::d0^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-208.azure-dns.info`
		A	208.84.5.208^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-208.azure-dns.info`
MX	`whyhsk-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:cc35::^{🇰🇷 Microsoft2a01:111:f000::/36}
			PTR	`mail-slxp216cu00200.inbound.protection.outlook.com`
		A	2a01:111:f403:cc35::1^{🇰🇷 Microsoft2a01:111:f000::/36}
			PTR	`mail-sevp216cu00101.inbound.protection.outlook.com`
		A	2a01:111:f403:cc35::2^{🇰🇷 Microsoft2a01:111:f000::/36}
			PTR	`mail-se2p216cu00602.inbound.protection.outlook.com`
		A	2a01:111:f403:cc37::^{🇰🇷 Microsoft2a01:111:f000::/36}
			PTR	`mail-puwp216cu00200.inbound.protection.outlook.com`
		A	52.101.153.0^{🇰🇷 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-slxp216cu00200.inbound.protection.outlook.com`
		A	52.101.153.1^{🇰🇷 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sevp216cu00101.inbound.protection.outlook.com`
		A	52.101.153.2^{🇰🇷 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-se2p216cu00602.inbound.protection.outlook.com`
		A	52.101.155.0^{🇰🇷 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-puwp216cu00200.inbound.protection.outlook.com`
TXT	`mscid=/29eODJAfDmrnbeCcwWwZhsUu4ligrlplW6bGU4lh6VgMulv4GFzRqiowRIb8MeMBDbMtTT...`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
SOA	`ns1.bdm.microsoftonline.com`azuredns-hostmaster@microsoft.com serial=1

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

Previously NS for

whyhsk.com

Same first word

whyhsk.com

Similar names

shhkyw.com

whhsky.com

whhyks.cn

whhyks.com

swhyhk.com

hwhkys.com

DNS History

20 records (6 active, 14 former)

○NSns-103.awsdns-12.com2019-03-27 → 2019-03-27 · 4 obs

○ 2017-01-27 03:02:36
● 2019-03-27 22:40:08
○ 2026-02-15 13:46:44
○ 2026-03-24 01:31:00

○NSns-1463.awsdns-54.org2019-03-27 → 2019-03-27 · 4 obs

○ 2017-01-27 03:02:36
● 2019-03-27 22:40:08
○ 2026-02-15 13:46:44
○ 2026-03-24 01:31:00

○NSns-1633.awsdns-12.co.uk2019-03-27 → 2019-03-27 · 4 obs

○ 2017-01-27 03:02:36
● 2019-03-27 22:40:08
○ 2026-02-15 13:46:44
○ 2026-03-24 01:31:00

○NSns-654.awsdns-17.net2019-03-27 → 2019-03-27 · 4 obs

○ 2017-01-27 03:02:36
● 2019-03-27 22:40:08
○ 2026-02-15 13:46:44
○ 2026-03-24 01:31:00

○NSns.cafe24.com2015-08-01 → 2017-01-27 · 4 obs

● 2015-08-01 12:47:26
● 2017-01-27 03:02:36
○ 2019-03-27 22:40:08
○ 2026-03-24 01:31:00

○NSns0.cafe24.com2015-08-01 → 2017-01-27 · 4 obs

● 2015-08-01 12:47:26
● 2017-01-27 03:02:36
○ 2019-03-27 22:40:08
○ 2026-03-24 01:31:00

●NSns1.bdm.microsoftonline.com2026-02-15 → 2026-03-24 · 3 obs

○ 2019-03-27 22:40:08
● 2026-02-15 13:46:44
● 2026-03-24 01:31:00

○NSns1.cafe24.com2015-08-01 → 2017-01-27 · 4 obs

● 2015-08-01 12:47:26
● 2017-01-27 03:02:36
○ 2019-03-27 22:40:08
○ 2026-03-24 01:31:00

●NSns2.bdm.microsoftonline.com2026-02-15 → 2026-03-24 · 3 obs

○ 2019-03-27 22:40:08
● 2026-02-15 13:46:44
● 2026-03-24 01:31:00

○NSns2.cafe24.com2015-08-01 → 2017-01-27 · 4 obs

● 2015-08-01 12:47:26
● 2017-01-27 03:02:36
○ 2019-03-27 22:40:08
○ 2026-03-24 01:31:00

●NSns3.bdm.microsoftonline.com2026-02-15 → 2026-03-24 · 3 obs

○ 2019-03-27 22:40:08
● 2026-02-15 13:46:44
● 2026-03-24 01:31:00

●NSns4.bdm.microsoftonline.com2026-02-15 → 2026-03-24 · 3 obs

○ 2019-03-27 22:40:08
● 2026-02-15 13:46:44
● 2026-03-24 01:31:00

○NSwhyhsk.com2015-08-01 → 2017-01-27 · 4 obs

● 2015-08-01 12:47:26
● 2017-01-27 03:02:36
○ 2019-03-27 22:40:08
○ 2026-03-24 01:31:00

○MXaspmx1.naver.com2015-08-01 → 2017-01-27 · 4 obs

● 2015-08-01 12:47:26
● 2017-01-27 03:02:36
○ 2019-03-27 22:40:08
○ 2026-03-24 01:31:00

○MXaspmx2.naver.com2015-08-01 → 2017-01-27 · 4 obs

● 2015-08-01 12:47:26
● 2017-01-27 03:02:36
○ 2019-03-27 22:40:08
○ 2026-03-24 01:31:00

○MXkr1-aspmx1.worksmobile.com2019-03-27 → 2019-03-27 · 4 obs

○ 2017-01-27 03:02:36
● 2019-03-27 22:40:08
○ 2026-02-15 13:46:44
○ 2026-03-24 01:31:00

○MXkr1-aspmx2.worksmobile.com2019-03-27 → 2019-03-27 · 4 obs

○ 2017-01-27 03:02:36
● 2019-03-27 22:40:08
○ 2026-02-15 13:46:44
○ 2026-03-24 01:31:00

●MXwhyhsk-com.mail.protection.outlook.com2026-02-15 → 2026-03-24 · 3 obs

○ 2019-03-27 22:40:08
● 2026-02-15 13:46:44
● 2026-03-24 01:31:00

○A112.175.50.2282015-08-01 → 2017-01-27 · 4 obs

● 2015-08-01 12:47:26
● 2017-01-27 03:02:36
○ 2019-03-27 22:40:08
○ 2026-03-24 01:31:00

●A183.111.242.132026-02-15 → 2026-03-24 · 3 obs

○ 2019-03-27 22:40:08
● 2026-02-15 13:46:44
● 2026-03-24 01:31:00

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
whyhsk.com	ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com, ns4.bdm.microsoftonline.com	8 records

✅ Authoritative Response

Server:13.107.236.208

NS records: ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com, ns4.bdm.microsoftonline.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for whyhsk.com (unsigned zone)

⏱️ Timing

Total: 152ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`183.111.242.13`
NS	4	`ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com...`
MX	1	`whyhsk-com.mail.protection.outlook.com (`
TXT	2	`mscid=/29eODJAfDmrnbeCcwWwZhsUu4ligrlplW, v=spf1 include:spf.protection.outlook.co`
SOA	1	`ns1.bdm.microsoftonline.com azuredns-hos`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns1.bdm.microsoftonline.com, ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com...)

Analysis

IP Addresses

whyhsk.com maps to IP address 183.111.242.13.

Other host names, for instance foresco.co.kr, www.cpkorea.co.kr, dodamlaw.com, dcna.or.kr and boohan.co.kr share IP numbers with whyhsk.com.

Name Servers

whyhsk.com is delegated to four name servers: ns1.bdm.microsoftonline.com, ns2.bdm.microsoftonline.com, ns3.bdm.microsoftonline.com and ns4.bdm.microsoftonline.com.

whyhsk.com at least partially shares name servers with other domains such as wemec.co.uk, detino.com, idealknitwear.com, asianmanland.com and lpva.lv.