ilanham.com - dns.ninja

`ilanham.com`

DNSSEC	⚠️ Not signed
A	50.209.217.197^{🇺🇸 COMCAST-IBONE50.128.0.0/9 Comcast Cable Communications, Inc. 1800 Bishops Gate Blvd Mount Laurel, NJ 08054}
		PTR	`50-209-217-197-static.hfc.comcastbusiness.net`
NS	`ns01.domaincontrol.com` ⭐
		A	2603:5:2140::1^{🇺🇸 GODADDY-DNS2603:5:2140::/44}
			PTR	`ns01.domaincontrol.com`
		A	97.74.100.1^{🇺🇸 GODADDY-DNS97.74.100.0/23}
			PTR	`ns01.domaincontrol.com`
NS	`ns02.domaincontrol.com`
		A	2603:5:2240::1^{🇺🇸 GODADDY-DNS2603:5:2240::/44}
			PTR	`ns02.domaincontrol.com`
		A	173.201.68.1^{🇺🇸 GODADDY-DNS173.201.68.0/23}
			PTR	`ns02.domaincontrol.com`
MX	`ilanham-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c801::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sn1pr0501cu00101.inbound.protection.outlook.com`
		A	2a01:111:f403:c922::2^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bl0pr02cu00702.inbound.protection.outlook.com`
		A	2a01:111:f403:f905::4^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-dm2pr04cu00404.inbound.protection.outlook.com`
		A	2a01:111:f403:f908::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bn1pr21cu00100.inbound.protection.outlook.com`
		A	52.101.10.12^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bn1pr21cu00204.inbound.protection.outlook.com`
		A	52.101.40.4^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-cy5pr03cu00204.inbound.protection.outlook.com`
		A	52.101.41.54^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sj2pr05cu00506.inbound.protection.outlook.com`
		A	52.101.50.7^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-co1pr21cu00207.inbound.protection.outlook.com`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
TXT	`NETORGFT8161124.onmicrosoft.com`
TXT	`2u3ne3hubc84i2l277o8j6n3su`
SOA	`ns01.domaincontrol.com`dns@jomax.net 2025-07-07 #0

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

⚠️ On DNS blocklist: tif

Same first word

ilanham.com

Similar names

hanmail.co.kr

laianhm.com

nhamail.com

mahanil.org

hanamil.net

anilmah.com

hamilan.com

mailahn.com

milanah.com

halmani.com

mailahn.de

halamin.com

anhimal.com

ahnmail.net

hailman.guru

nahmail.uk

almihan.com

lanhaim.com

hanmail.kr

hanmail.me

mahalin.com

hanimal.com

lahanmi.com

manahil.net

ahliman.info

animalh.com

manahil.com

manilha.com

malahin.com

alhanim.com

nahmail.com

lanimah.com

animahl.com

hailman.de

manilah.com

milhaan.com

haminal.com

mihalna.ru

manahil.us

hilaman.com

hlaiman.com

hnamail.com

hailman.com

hanmail.com

hanimal.es

hamnail.net

hanmail.net

manilah.be

malahni.com

hanmali.net

minhala.com

hamnail.com

hanmali.com

minahal.com

DNS History

23 records (4 active, 19 former)

●NSns01.domaincontrol.com2026-02-20 → 2026-07-01 · 3 obs

○ 2017-03-09 11:00:44
● 2026-02-20 22:47:54
● 2026-07-01 15:48:54

●NSns02.domaincontrol.com2026-02-20 → 2026-07-01 · 3 obs

○ 2017-03-09 11:00:44
● 2026-02-20 22:47:54
● 2026-07-01 15:48:54

○NSns1.changeip.com2015-06-03 → 2017-03-09 · 5 obs

○ 2008-03-18 16:12:20
● 2015-06-03 09:07:00
● 2017-03-09 11:00:44
○ 2026-02-20 22:47:54
○ 2026-07-01 15:48:54

○NSns1.mydyndns.org2008-03-18 → 2008-03-18 · 3 obs

● 2008-03-18 16:12:20
○ 2015-06-03 09:07:00
○ 2026-07-01 15:48:54

○NSns2.changeip.com2015-06-03 → 2017-03-09 · 5 obs

○ 2008-03-18 16:12:20
● 2015-06-03 09:07:00
● 2017-03-09 11:00:44
○ 2026-02-20 22:47:54
○ 2026-07-01 15:48:54

○NSns2.mydyndns.org2008-03-18 → 2008-03-18 · 3 obs

● 2008-03-18 16:12:20
○ 2015-06-03 09:07:00
○ 2026-07-01 15:48:54

○NSns3.changeip.com2015-06-03 → 2017-03-09 · 5 obs

○ 2008-03-18 16:12:20
● 2015-06-03 09:07:00
● 2017-03-09 11:00:44
○ 2026-02-20 22:47:54
○ 2026-07-01 15:48:54

○NSns3.mydyndns.org2008-03-18 → 2008-03-18 · 3 obs

● 2008-03-18 16:12:20
○ 2015-06-03 09:07:00
○ 2026-07-01 15:48:54

○NSns4.changeip.com2015-06-03 → 2017-03-09 · 5 obs

○ 2008-03-18 16:12:20
● 2015-06-03 09:07:00
● 2017-03-09 11:00:44
○ 2026-02-20 22:47:54
○ 2026-07-01 15:48:54

○NSns4.mydyndns.org2008-03-18 → 2008-03-18 · 3 obs

● 2008-03-18 16:12:20
○ 2015-06-03 09:07:00
○ 2026-07-01 15:48:54

○NSns5.changeip.com2015-06-03 → 2017-03-09 · 5 obs

○ 2008-03-18 16:12:20
● 2015-06-03 09:07:00
● 2017-03-09 11:00:44
○ 2026-02-20 22:47:54
○ 2026-07-01 15:48:54

○NSns6.changeip.com2015-06-03 → 2017-03-09 · 5 obs

○ 2008-03-18 16:12:20
● 2015-06-03 09:07:00
● 2017-03-09 11:00:44
○ 2026-02-20 22:47:54
○ 2026-07-01 15:48:54

○NSns7.changeip.com2015-06-03 → 2017-03-09 · 5 obs

○ 2008-03-18 16:12:20
● 2015-06-03 09:07:00
● 2017-03-09 11:00:44
○ 2026-02-20 22:47:54
○ 2026-07-01 15:48:54

●MXilanham-com.mail.protection.outlook.com2026-02-20 → 2026-07-01 · 3 obs

○ 2017-03-09 11:00:44
● 2026-02-20 22:47:54
● 2026-07-01 15:48:54

○MXilanham.com.c2.mx1.ik2.com2015-10-30 → 2017-03-09 · 5 obs

○ 2008-03-18 16:12:20
● 2015-10-30 19:27:00
● 2017-03-09 11:00:44
○ 2026-02-20 22:47:54
○ 2026-07-01 15:48:54

○MXilanham.com.c2.mx2.ik2.io2015-10-30 → 2017-03-09 · 5 obs

○ 2008-03-18 16:12:20
● 2015-10-30 19:27:00
● 2017-03-09 11:00:44
○ 2026-02-20 22:47:54
○ 2026-07-01 15:48:54

○MXilanham.com.c2.mx3.ik2.eu2015-10-30 → 2017-03-09 · 5 obs

○ 2008-03-18 16:12:20
● 2015-10-30 19:27:00
● 2017-03-09 11:00:44
○ 2026-02-20 22:47:54
○ 2026-07-01 15:48:54

○MXmx0.ik2.com2015-06-03 → 2015-06-03 · 4 obs

○ 2008-03-18 16:12:20
● 2015-06-03 09:07:00
○ 2015-10-30 19:27:00
○ 2026-07-01 15:48:54

○MXmx1.ik2.com2015-06-03 → 2015-06-03 · 4 obs

○ 2008-03-18 16:12:20
● 2015-06-03 09:07:00
○ 2015-10-30 19:27:00
○ 2026-07-01 15:48:54

○MXmx2.ik2.com2015-06-03 → 2015-06-03 · 4 obs

○ 2008-03-18 16:12:20
● 2015-06-03 09:07:00
○ 2015-10-30 19:27:00
○ 2026-07-01 15:48:54

○MXmx3.ik2.com2015-06-03 → 2015-06-03 · 4 obs

○ 2008-03-18 16:12:20
● 2015-06-03 09:07:00
○ 2015-10-30 19:27:00
○ 2026-07-01 15:48:54

●A50.209.217.1972026-02-20 → 2026-07-01 · 3 obs

○ 2017-03-09 11:00:44
● 2026-02-20 22:47:54
● 2026-07-01 15:48:54

○A74.95.213.52008-03-18 → 2017-03-09 · 4 obs

● 2008-03-18 16:12:20
● 2017-03-09 11:00:44
○ 2026-02-20 22:47:54
○ 2026-07-01 15:48:54

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
ilanham.com	ns01.domaincontrol.com, ns02.domaincontrol.com	4 records

✅ Authoritative Response

Server:97.74.100.1

NS records: ns01.domaincontrol.com, ns02.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for ilanham.com (unsigned zone)

⏱️ Timing

Total: 106ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`50.209.217.197`
NS	2	`ns01.domaincontrol.com, ns02.domaincontrol.com`
MX	1	`ilanham-com.mail.protection.outlook.com`
TXT	3	`v=spf1 include:spf.protection.outlook.co, NETORGFT8161124.onmicrosoft.com...`
SOA	1	`ns01.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns01.domaincontrol.com, ns01.domaincontrol.com, ns02.domaincontrol.com...)

Analysis

IP Addresses

ilanham.com resolves to one IP address: 50.209.217.197.

Name Servers

ilanham.com is delegated to two name servers: ns01.domaincontrol.com and ns02.domaincontrol.com.

ilanham.com uses the same name servers as several other domains — among them napoletanolaw.com, masterprograming.com, tenderheartssc.org and two more.

ns01.domaincontrol.com and ns02.domaincontrol.com each resolve to two IP addresses: ns01.domaincontrol.com points to 97.74.100.1 and 2603:5:2140::1, while ns02.domaincontrol.com points to 173.201.68.1 and 2603:5:2240::1.

Mail Servers

Mail for ilanham.com is handled by a single mail server, ilanham-com.mail.protection.outlook.com.

ilanham-com.mail.protection.outlook.com resolves to 8 IP addresses — 52.101.10.12, 52.101.40.4, 52.101.41.54 and 5 others.