`whzan.com`

DNSSEC	⚠️ Not signed
A	51.140.37.241^{🇬🇧 Microsoft51.140.0.0/14}
NS	`ns1-03.azure-dns.com` ⭐
		A	2603:1061:0:700::3^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-03.azure-dns.com`
		A	13.107.236.3^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-03.azure-dns.com`
NS	`ns2-03.azure-dns.net`
		A	2620:1ec:8ec:700::3^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-03.azure-dns.net`
		A	150.171.21.3^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-03.azure-dns.net`
NS	`ns3-03.azure-dns.org`
		A	2a01:111:4000:700::3^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-03.azure-dns.org`
		A	204.14.183.3^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-03.azure-dns.org`
NS	`ns4-03.azure-dns.info`
		A	2620:1ec:bda:700::3^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-03.azure-dns.info`
		A	208.84.5.3^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-03.azure-dns.info`
MX	`solcom-com.mail.eo.outlook.com` ⭐
		A	2a01:111:f403:ca0b::^{🇬🇧 Microsoft2a01:111:f000::/36}
			PTR	`mail-lo2p265cu02300.inbound.protection.outlook.com`
		A	2a01:111:f403:ca0b::1^{🇬🇧 Microsoft2a01:111:f000::/36}
			PTR	`mail-lo3p265cu00301.inbound.protection.outlook.com`
		A	2a01:111:f403:ca1a::^{🇬🇧 Microsoft2a01:111:f000::/36}
			PTR	`mail-cwxp265cu00500.inbound.protection.outlook.com`
		A	2a01:111:f403:ca1a::1^{🇬🇧 Microsoft2a01:111:f000::/36}
			PTR	`mail-cwxp265cu00601.inbound.protection.outlook.com`
		A	52.101.89.0^{🇬🇧 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-lo2p265cu02300.inbound.protection.outlook.com`
		A	52.101.89.1^{🇬🇧 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-lo0p265cu00201.inbound.protection.outlook.com`
		A	52.101.89.2^{🇬🇧 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-lo3p265cu00302.inbound.protection.outlook.com`
		A	52.101.99.2^{🇬🇧 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-cwxp265cu00502.inbound.protection.outlook.com`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
TXT	`whzanuk.azurewebsites.net`
TXT	`MS=ms84123205`
TXT	`uf3145r3qql1aqaitv7a28ra49`
TXT	`atlassian-domain-verification=GcQr8bh3HqhNwEnvVVjWgNPeV/1f7ifWqwJJPc5xma1ktE6...`
SOA	`ns1-03.azure-dns.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=1774696992

Subdomains

www.whzan.com

Same first word

whzan.com

Similar names

hwazn.com

nazhw.com

zanwh.com

zhanw.com.cn

ahnzw.com.cn

wanzh.cn

zhanw.com

DNS History

17 records (6 active, 11 former)

○NSdns1.stabletransit.com2015-07-08 → 2016-06-24 · 4 obs

● 2015-07-08 23:14:24
● 2016-06-24 14:59:42
○ 2017-02-09 09:38:46
○ 2026-03-28 11:35:22

○NSdns2.stabletransit.com2015-07-08 → 2016-06-24 · 4 obs

● 2015-07-08 23:14:24
● 2016-06-24 14:59:42
○ 2017-02-09 09:38:46
○ 2026-03-28 11:35:22

●NSns1-03.azure-dns.com2026-03-24 → 2026-03-28 · 3 obs

○ 2019-03-01 08:11:14
● 2026-03-24 01:16:16
● 2026-03-28 11:35:22

○NSns1.ukdnsservers.co.uk2017-02-09 → 2019-03-01 · 5 obs

○ 2016-06-24 14:59:42
● 2017-02-09 09:38:46
● 2019-03-01 08:11:14
○ 2026-03-24 01:16:16
○ 2026-03-28 11:35:22

●NSns2-03.azure-dns.net2026-03-24 → 2026-03-28 · 3 obs

○ 2019-03-01 08:11:14
● 2026-03-24 01:16:16
● 2026-03-28 11:35:22

○NSns2.ukdnsservers.co.uk2017-02-09 → 2019-03-01 · 5 obs

○ 2016-06-24 14:59:42
● 2017-02-09 09:38:46
● 2019-03-01 08:11:14
○ 2026-03-24 01:16:16
○ 2026-03-28 11:35:22

●NSns3-03.azure-dns.org2026-03-24 → 2026-03-28 · 3 obs

○ 2019-03-01 08:11:14
● 2026-03-24 01:16:16
● 2026-03-28 11:35:22

○NSns3.ukdnsservers.co.uk2017-02-09 → 2019-03-01 · 5 obs

○ 2016-06-24 14:59:42
● 2017-02-09 09:38:46
● 2019-03-01 08:11:14
○ 2026-03-24 01:16:16
○ 2026-03-28 11:35:22

●NSns4-03.azure-dns.info2026-03-24 → 2026-03-28 · 3 obs

○ 2019-03-01 08:11:14
● 2026-03-24 01:16:16
● 2026-03-28 11:35:22

○NSns4.ukdnsservers.co.uk2017-02-09 → 2019-03-01 · 5 obs

○ 2016-06-24 14:59:42
● 2017-02-09 09:38:46
● 2019-03-01 08:11:14
○ 2026-03-24 01:16:16
○ 2026-03-28 11:35:22

○MXmx1.emailsrvr.com2015-07-08 → 2019-03-01 · 6 obs

● 2015-07-08 23:14:24
● 2016-06-24 14:59:42
○ 2017-02-09 09:38:46
● 2019-03-01 08:11:14
○ 2026-03-24 01:16:16
○ 2026-03-28 11:35:22

○MXmx2.emailsrvr.com2015-07-08 → 2019-03-01 · 6 obs

● 2015-07-08 23:14:24
● 2016-06-24 14:59:42
○ 2017-02-09 09:38:46
● 2019-03-01 08:11:14
○ 2026-03-24 01:16:16
○ 2026-03-28 11:35:22

●MXsolcom-com.mail.eo.outlook.com2026-03-24 → 2026-03-28 · 3 obs

○ 2019-03-01 08:11:14
● 2026-03-24 01:16:16
● 2026-03-28 11:35:22

○MXwhzan-com.mail.protection.outlook.com2017-02-09 → 2017-02-09 · 4 obs

○ 2016-06-24 14:59:42
● 2017-02-09 09:38:46
○ 2019-03-01 08:11:14
○ 2026-03-28 11:35:22

○A104.46.54.1192017-02-09 → 2017-02-09 · 4 obs

○ 2016-06-24 14:59:42
● 2017-02-09 09:38:46
○ 2019-03-01 08:11:14
○ 2026-03-28 11:35:22

○A174.143.163.802015-07-08 → 2016-06-24 · 4 obs

● 2015-07-08 23:14:24
● 2016-06-24 14:59:42
○ 2017-02-09 09:38:46
○ 2026-03-28 11:35:22

●A51.140.37.2412019-03-01 → 2026-03-28 · 3 obs

○ 2017-02-09 09:38:46
● 2019-03-01 08:11:14
● 2026-03-28 11:35:22

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	k.gtld-servers.net, e.gtld-servers.net, h.gtld-servers.net, a.gtld-servers.net...	-
whzan.com	ns1-03.azure-dns.com, ns2-03.azure-dns.net, ns3-03.azure-dns.org, ns4-03.azure-dns.info	2 records

✅ Authoritative Response

Server:13.107.236.3

NS records: ns1-03.azure-dns.com, ns2-03.azure-dns.net, ns3-03.azure-dns.org, ns4-03.azure-dns.info

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for whzan.com (unsigned zone)

⏱️ Timing

Total: 132ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`51.140.37.241`
NS	4	`ns1-03.azure-dns.com, ns2-03.azure-dns.net...`
MX	1	`solcom-com.mail.eo.outlook.com (pri: 0)`
TXT	5	`v=spf1 include:spf.protection.outlook.co, whzanuk.azurewebsites.net...`
SOA	1	`ns1-03.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1-03.azure-dns.com, ns1-03.azure-dns.com)

Analysis

Hierarchy

whzan.com is the parent of www.whzan.com.

IP Addresses

whzan.com points to IP number 51.140.37.241.

For instance, other host names via-moto.co.uk, tasksheets.co.uk, streetsupport.net, pricerooms.com and housing21.org.uk share IP numbers with whzan.com.

Name Servers

whzan.com is delegated to four name servers: ns1-03.azure-dns.com, ns4-03.azure-dns.info, ns2-03.azure-dns.net and ns3-03.azure-dns.org.

whzan.com shares name servers with other domains at least partially, for example pgbeauty.com, qest.cloud, zcc.w.api.fabric.microsoft-int.com, vishay.in and diamonddodge.ca.

Host names with two IP numbers:

ns1-03.azure-dns.com points to: 2603:1061:0:700::3 and 13.107.236.3

ns4-03.azure-dns.info points to: 2620:1ec:bda:700::3 and 208.84.5.3

ns2-03.azure-dns.net points to: 2620:1ec:8ec:700::3 and 150.171.21.3

ns3-03.azure-dns.org points to: 2a01:111:4000:700::3 and 204.14.183.3

Mail Servers

whzan.com is handled by a single mail server, solcom-com.mail.eo.outlook.com.

The mail server setup of whzan.com is the same as that of other domains, for instance solcom.com.

Host name solcom-com.mail.eo.outlook.com points to eight IP numbers: 2a01:111:f403:ca0b::, 2a01:111:f403:ca0b::1, 2a01:111:f403:ca1a::, 2a01:111:f403:ca1a::1, 52.101.89.0, 52.101.89.1, 52.101.89.2 and 52.101.99.2.

whzan.com - robtex.com

whzan.com

com

Subdomains

Same first word

Similar names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

Hierarchy

IP Addresses

Name Servers

Mail Servers

`whzan.com`

`com`