`mkanand.com`

DNSSEC	⚠️ Not signed
A	18.208.88.157^{🇺🇸 Amazon18.208.0.0/13 EC2 IAD prefix}
		PTR	`ec2-18-208-88-157.compute-1.amazonaws.com`
A	98.84.224.111^{🇺🇸 Amazon98.80.0.0/13 EC2 IAD Prefix}
NS	`dns1.p01.nsone.net` ⭐
		A	2620:4d:4000:6259:7:1:0:1^{🇺🇸 NSONE2620:4d:4000::/48 PNAP-ACS nsone-1}
			PTR	`dns1.p01.nsone.net`
		A	198.51.44.1^{🇺🇸 NSONE198.51.44.0/24}
			PTR	`dns1.p01.nsone.net`
NS	`dns1.p03.nsone.net`
		A	2620:4d:4000:6259:7:3:0:1^{🇺🇸 NSONE2620:4d:4000::/48 PNAP-ACS nsone-1}
			PTR	`dns1.p03.nsone.net`
		A	198.51.44.3^{🇺🇸 NSONE198.51.44.0/24}
			PTR	`dns1.p03.nsone.net`
NS	`dns2.p03.nsone.net`
		A	2a00:edc0:6259:7:3::2^{🇺🇸 NSONE2a00:edc0:6259::/48 NS1-2}
			PTR	`dns2.p03.nsone.net`
		A	198.51.45.3^{🇺🇸 NSONE198.51.45.0/24}
			PTR	`dns2.p03.nsone.net`
NS	`dns3.p03.nsone.net`
		A	2620:4d:4000:6259:7:3:0:3^{🇺🇸 NSONE2620:4d:4000::/48 PNAP-ACS nsone-1}
			PTR	`dns3.p03.nsone.net`
		A	198.51.44.67^{🇺🇸 NSONE198.51.44.0/24}
			PTR	`dns3.p03.nsone.net`
NS	`dns4.p03.nsone.net`
		A	2a00:edc0:6259:7:3::4^{🇺🇸 NSONE2a00:edc0:6259::/48 NS1-2}
			PTR	`dns4.p03.nsone.net`
		A	198.51.45.67^{🇺🇸 NSONE198.51.45.0/24}
			PTR	`dns4.p03.nsone.net`
SOA	`dns1.p01.nsone.net`domains+netlify@netlify.com serial=1779889682

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

Same first word

mkanand.com

Similar names

dankman.com

DNS History

20 records (7 active, 13 former)

○NSdns011.c.register.com2017-01-03 → 2018-06-06 · 4 obs

● 2017-01-03 09:15:20
● 2018-06-06 02:03:30
○ 2026-03-04 19:17:46
○ 2026-08-11 04:39:28

●NSdns1.p01.nsone.net2026-08-06 → 2026-08-11 · 3 obs

○ 2026-03-04 19:17:46
● 2026-08-06 19:35:22
● 2026-08-11 04:39:28

●NSdns1.p03.nsone.net2026-08-06 → 2026-08-11 · 3 obs

○ 2026-03-04 19:17:46
● 2026-08-06 19:35:22
● 2026-08-11 04:39:28

○NSdns141.b.register.com2017-01-03 → 2018-06-06 · 4 obs

● 2017-01-03 09:15:20
● 2018-06-06 02:03:30
○ 2026-03-04 19:17:46
○ 2026-08-11 04:39:28

○NSdns177.d.register.com2017-01-03 → 2018-06-06 · 4 obs

● 2017-01-03 09:15:20
● 2018-06-06 02:03:30
○ 2026-03-04 19:17:46
○ 2026-08-11 04:39:28

●NSdns2.p03.nsone.net2026-08-06 → 2026-08-11 · 3 obs

○ 2026-03-04 19:17:46
● 2026-08-06 19:35:22
● 2026-08-11 04:39:28

○NSdns201.a.register.com2017-01-03 → 2018-06-06 · 4 obs

● 2017-01-03 09:15:20
● 2018-06-06 02:03:30
○ 2026-03-04 19:17:46
○ 2026-08-11 04:39:28

●NSdns3.p03.nsone.net2026-08-06 → 2026-08-11 · 3 obs

○ 2026-03-04 19:17:46
● 2026-08-06 19:35:22
● 2026-08-11 04:39:28

●NSdns4.p03.nsone.net2026-08-06 → 2026-08-11 · 3 obs

○ 2026-03-04 19:17:46
● 2026-08-06 19:35:22
● 2026-08-11 04:39:28

○MXalt1.aspmx.l.google.com2017-01-03 → 2018-06-06 · 4 obs

● 2017-01-03 09:15:20
● 2018-06-06 02:03:30
○ 2026-03-04 19:17:46
○ 2026-08-11 04:39:28

○MXalt2.aspmx.l.google.com2017-01-03 → 2018-06-06 · 4 obs

● 2017-01-03 09:15:20
● 2018-06-06 02:03:30
○ 2026-03-04 19:17:46
○ 2026-08-11 04:39:28

○MXalt3.aspmx.l.google.com2017-01-03 → 2018-06-06 · 4 obs

● 2017-01-03 09:15:20
● 2018-06-06 02:03:30
○ 2026-03-04 19:17:46
○ 2026-08-11 04:39:28

○MXalt4.aspmx.l.google.com2017-01-03 → 2018-06-06 · 4 obs

● 2017-01-03 09:15:20
● 2018-06-06 02:03:30
○ 2026-03-04 19:17:46
○ 2026-08-11 04:39:28

○MXaspmx.l.google.com2017-01-03 → 2018-06-06 · 4 obs

● 2017-01-03 09:15:20
● 2018-06-06 02:03:30
○ 2026-03-04 19:17:46
○ 2026-08-11 04:39:28

●A18.208.88.1572026-08-11 → 2026-08-11 · 2 obs

○ 2026-08-06 19:35:22
● 2026-08-11 04:39:28

○A199.34.228.1502018-06-06 → 2018-06-06 · 4 obs

○ 2017-01-03 09:15:20
● 2018-06-06 02:03:30
○ 2026-03-04 19:17:46
○ 2026-08-11 04:39:28

○A199.34.228.682017-01-03 → 2017-01-03 · 3 obs

● 2017-01-03 09:15:20
○ 2018-06-06 02:03:30
○ 2026-08-11 04:39:28

○A35.157.26.1352026-08-06 → 2026-08-06 · 3 obs

○ 2026-03-04 19:17:46
● 2026-08-06 19:35:22
○ 2026-08-11 04:39:28

○A63.176.8.2182026-08-06 → 2026-08-06 · 3 obs

○ 2026-03-04 19:17:46
● 2026-08-06 19:35:22
○ 2026-08-11 04:39:28

●A98.84.224.1112026-08-11 → 2026-08-11 · 2 obs

○ 2026-08-06 19:35:22
● 2026-08-11 04:39:28

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
mkanand.com	dns1.p03.nsone.net, dns2.p03.nsone.net, dns3.p03.nsone.net, dns4.p03.nsone.net	-

✅ Authoritative Response

Server:198.51.44.67

NS records: dns1.p03.nsone.net, dns2.p03.nsone.net, dns3.p03.nsone.net, dns4.p03.nsone.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for mkanand.com (unsigned zone)

⏱️ Timing

Total: 491ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`98.84.224.111, 18.208.88.157`
NS	4	`dns1.p03.nsone.net, dns2.p03.nsone.net...`
SOA	1	`dns1.p01.nsone.net domains+netlify.netli`

Analysis

IP Addresses

mkanand.com directs to two IP numbers, 18.208.88.157 and 98.84.224.111

deploy-preview-998--hashicorp-staging.netlify.com, mnaks.me, condescending-saha-9f3295.netlify.app plus two other host names have IP numbers in common with mkanand.com.

Name Servers

Five name servers handle delegation for mkanand.com: dns1.p01.nsone.net, dns1.p03.nsone.net, dns2.p03.nsone.net and two others.

mkanand.com shares at least some of its name servers with other domains, including kaulbarschoutdoors.org, wildthingsanatomy.com, ejmdesigns.com and two others.

These name servers are frequently seen alongside dns3.p03.nsone.net, dns4.p03.nsone.net, ns01.squarespacedns.com and 7 other name servers.

Host names pointing to two IP addresses:

dns1.p01.nsone.net points to 198.51.44.1 and 2620:4d:4000:6259:7:1:0:1.

dns1.p03.nsone.net points to 198.51.44.3 and 2620:4d:4000:6259:7:3:0:1.

dns2.p03.nsone.net points to 198.51.45.3 and 2a00:edc0:6259:7:3::2.

dns3.p03.nsone.net points to 198.51.44.67 and 2620:4d:4000:6259:7:3:0:3.

dns4.p03.nsone.net points to 198.51.45.67 and 2a00:edc0:6259:7:3::4.