leadnabber.com - dns.ninja

`leadnabber.com`

DNSSEC	⚠️ Not signed
A	13.248.243.5^{🇺🇸 Amazon13.248.240.0/20}
		PTR	`a16e665f42988324c.awsglobalaccelerator.com`
A	76.223.105.230^{🇺🇸 Amazon76.223.96.0/20}
NS	`ns47.domaincontrol.com` ⭐
		A	2603:5:2172::18^{🇺🇸 GODADDY-DNS2603:5:2170::/44}
			PTR	`ns47.domaincontrol.com`
		A	97.74.103.24^{🇺🇸 GODADDY-DNS97.74.102.0/23}
			PTR	`ns47.domaincontrol.com`
NS	`ns48.domaincontrol.com`
		A	2603:5:2272::18^{🇺🇸 GODADDY-DNS2603:5:2270::/44}
			PTR	`ns48.domaincontrol.com`
		A	173.201.71.24^{🇺🇸 GODADDY-DNS173.201.70.0/23}
			PTR	`ns48.domaincontrol.com`
MX	`leadnabber-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c902::6^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj0pr21cu00106.inbound.protection.outlook.com`
		A	2a01:111:f403:c92c::2^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-dm2pr04cu00102.inbound.protection.outlook.com`
		A	2a01:111:f403:c946::3^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-ch0pr04cu00603.inbound.protection.outlook.com`
		A	2a01:111:f403:f902::1^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-bl2pr02cu00101.inbound.protection.outlook.com`
		A	52.101.11.9^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sn1pr02cu00101.inbound.protection.outlook.com`
		A	52.101.41.3^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sj2pr05cu00103.inbound.protection.outlook.com`
		A	52.101.41.56^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-sj0pr21cu00100.inbound.protection.outlook.com`
		A	52.101.194.13^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-ch0pr04cu00605.inbound.protection.outlook.com`
TXT	`NETORGFT18214024.onmicrosoft.com`
TXT	`v=spf1 include:secureserver.net -all`
TXT	`facebook-domain-verification=0dhc0eicrh0t37g0roiqkmolcc8ngg`
SOA	`ns47.domaincontrol.com`dns@jomax.net 2025-03-04 #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=1785913024

Previously MX for

leadnabber.com

Same first word

leadnabber.com

DNS History

12 records (5 active, 7 former)

○NSns11.pinionmedia.net2015-05-08 → 2017-03-21 · 4 obs

● 2015-05-08 10:08:36
● 2017-03-21 12:07:00
○ 2026-03-02 20:33:14
○ 2026-08-05 07:08:44

○NSns12.pinionmedia.net2015-05-08 → 2017-03-21 · 4 obs

● 2015-05-08 10:08:36
● 2017-03-21 12:07:00
○ 2026-03-02 20:33:14
○ 2026-08-05 07:08:44

○NSns13.pinionmedia.net2015-05-08 → 2017-03-21 · 4 obs

● 2015-05-08 10:08:36
● 2017-03-21 12:07:00
○ 2026-03-02 20:33:14
○ 2026-08-05 07:08:44

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

○ 2017-03-21 12:07:00
● 2026-03-02 20:33:14
● 2026-08-05 07:08:44

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

○ 2017-03-21 12:07:00
● 2026-03-02 20:33:14
● 2026-08-05 07:08:44

●MXleadnabber-com.mail.protection.outlook.com2026-03-02 → 2026-08-05 · 3 obs

○ 2017-03-21 12:07:00
● 2026-03-02 20:33:14
● 2026-08-05 07:08:44

○MXleadnabber.com2015-05-08 → 2017-03-21 · 4 obs

● 2015-05-08 10:08:36
● 2017-03-21 12:07:00
○ 2026-03-02 20:33:14
○ 2026-08-05 07:08:44

●A13.248.243.52026-03-02 → 2026-08-05 · 3 obs

○ 2017-03-21 12:07:00
● 2026-03-02 20:33:14
● 2026-08-05 07:08:44

○A173.225.16.1622015-05-08 → 2016-03-19 · 4 obs

● 2015-05-08 10:08:36
● 2016-03-19 14:26:38
○ 2016-07-17 20:36:52
○ 2026-08-05 07:08:44

○A208.53.98.1282017-03-21 → 2017-03-21 · 4 obs

○ 2016-07-17 20:36:52
● 2017-03-21 12:07:00
○ 2026-03-02 20:33:14
○ 2026-08-05 07:08:44

○A76.14.121.1022016-07-17 → 2016-07-17 · 4 obs

○ 2016-03-19 14:26:38
● 2016-07-17 20:36:52
○ 2017-03-21 12:07:00
○ 2026-08-05 07:08:44

●A76.223.105.2302026-03-02 → 2026-08-05 · 3 obs

○ 2017-03-21 12:07:00
● 2026-03-02 20:33:14
● 2026-08-05 07:08:44

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
leadnabber.com	ns47.domaincontrol.com, ns48.domaincontrol.com	4 records

✅ Authoritative Response

Server:97.74.103.24

NS records: ns47.domaincontrol.com, ns48.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for leadnabber.com (unsigned zone)

⏱️ Timing

Total: 158ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`76.223.105.230, 13.248.243.5`
NS	2	`ns47.domaincontrol.com, ns48.domaincontrol.com`
MX	1	`leadnabber-com.mail.protection.outlook.c`
TXT	3	`NETORGFT18214024.onmicrosoft.com, v=spf1 include:secureserver.net -all...`
SOA	1	`ns47.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns47.domaincontrol.com, ns47.domaincontrol.com, ns48.domaincontrol.com...)

Analysis

IP Addresses

leadnabber.com points to the IP addresses 13.248.243.5 and 76.223.105.230

Among the host names that share IP numbers with leadnabber.com are technologysoupconsulting.com, modethree.net, queenofbakes.com and two others.

Name Servers

DNS delegation for leadnabber.com points to two name servers: ns47.domaincontrol.com and ns48.domaincontrol.com.

leadnabber.com has the same name server delegation as a number of other domains, such as coldboi.com, mghyderabad.co.in, orlandophotographers.com and two more.

leadnabber.com has partial name server overlap with other domains, including quantrellcadillac.com.

ns47.domaincontrol.com directs to 97.74.103.24 and 2603:5:2172::18. ns48.domaincontrol.com directs to 173.201.71.24 and 2603:5:2272::18. Each host name carries two IP addresses.

Mail Servers

leadnabber.com routes its mail through a single mail server, leadnabber-com.mail.protection.outlook.com.

leadnabber-com.mail.protection.outlook.com directs to 8 IP numbers, including 52.101.11.9, 52.101.41.3 and 52.101.41.56, along with 5 other.