infinite-leverage.com - dns.ninja

`infinite-leverage.com`

DNSSEC	⚠️ Not signed
A	20.42.128.126^{🇺🇸 Microsoft20.40.0.0/13 MICROSOFT}
NS	`ns1-01.azure-dns.com` ⭐
		A	2603:1061:0:700::1^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-01.azure-dns.com`
		A	13.107.236.1^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-01.azure-dns.com`
NS	`ns2-01.azure-dns.net`
		A	2620:1ec:8ec:700::1^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-01.azure-dns.net`
		A	150.171.21.1^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-01.azure-dns.net`
NS	`ns3-01.azure-dns.org`
		A	2a01:111:4000:700::1^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-01.azure-dns.org`
		A	204.14.183.1^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-01.azure-dns.org`
NS	`ns4-01.azure-dns.info`
		A	2620:1ec:bda:700::1^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-01.azure-dns.info`
		A	208.84.5.1^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-01.azure-dns.info`
SOA	`ns1-01.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=1785350697

Same first word

infinite-leverage.com

DNS History

17 records (5 active, 12 former)

●NSns1-01.azure-dns.com2026-07-29 → 2026-07-29 · 3 obs

○ 2026-03-30 10:56:52
● 2026-07-29 18:47:46
● 2026-07-29 18:47:48

○NSns13.domaincontrol.com2015-06-26 → 2016-01-31 · 4 obs

● 2015-06-26 20:53:30
● 2016-01-31 22:13:04
○ 2016-05-07 10:31:04
○ 2026-07-29 18:47:48

○NSns14.domaincontrol.com2015-06-26 → 2016-01-31 · 4 obs

● 2015-06-26 20:53:30
● 2016-01-31 22:13:04
○ 2016-05-07 10:31:04
○ 2026-07-29 18:47:48

●NSns2-01.azure-dns.net2026-07-29 → 2026-07-29 · 3 obs

○ 2026-03-30 10:56:52
● 2026-07-29 18:47:46
● 2026-07-29 18:47:48

○NSns25.domaincontrol.com2026-03-13 → 2026-03-30 · 5 obs

○ 2020-02-12 18:53:14
● 2026-03-13 17:41:04
● 2026-03-30 10:56:52
○ 2026-07-29 18:47:46
○ 2026-07-29 18:47:48

○NSns26.domaincontrol.com2026-03-13 → 2026-03-30 · 5 obs

○ 2020-02-12 18:53:14
● 2026-03-13 17:41:04
● 2026-03-30 10:56:52
○ 2026-07-29 18:47:46
○ 2026-07-29 18:47:48

●NSns3-01.azure-dns.org2026-07-29 → 2026-07-29 · 3 obs

○ 2026-03-30 10:56:52
● 2026-07-29 18:47:46
● 2026-07-29 18:47:48

●NSns4-01.azure-dns.info2026-07-29 → 2026-07-29 · 3 obs

○ 2026-03-30 10:56:52
● 2026-07-29 18:47:46
● 2026-07-29 18:47:48

○NSns63.domaincontrol.com2020-02-12 → 2020-02-12 · 4 obs

○ 2016-05-07 10:31:04
● 2020-02-12 18:53:14
○ 2026-03-13 17:41:04
○ 2026-07-29 18:47:48

○NSns64.domaincontrol.com2020-02-12 → 2020-02-12 · 4 obs

○ 2016-05-07 10:31:04
● 2020-02-12 18:53:14
○ 2026-03-13 17:41:04
○ 2026-07-29 18:47:48

○MXmailstore1.secureserver.net2015-06-26 → 2016-01-31 · 4 obs

● 2015-06-26 20:53:30
● 2016-01-31 22:13:04
○ 2016-05-07 10:31:04
○ 2026-07-29 18:47:48

○MXsmtp.secureserver.net2015-06-26 → 2016-01-31 · 4 obs

● 2015-06-26 20:53:30
● 2016-01-31 22:13:04
○ 2016-05-07 10:31:04
○ 2026-07-29 18:47:48

○A13.248.243.52026-03-13 → 2026-03-30 · 5 obs

○ 2020-02-12 18:53:14
● 2026-03-13 17:41:04
● 2026-03-30 10:56:52
○ 2026-07-29 18:47:46
○ 2026-07-29 18:47:48

○A184.168.221.122015-06-26 → 2016-01-31 · 4 obs

● 2015-06-26 20:53:30
● 2016-01-31 22:13:04
○ 2016-05-07 10:31:04
○ 2026-07-29 18:47:48

○A184.168.221.482020-02-12 → 2020-02-12 · 4 obs

○ 2016-05-07 10:31:04
● 2020-02-12 18:53:14
○ 2026-03-13 17:41:04
○ 2026-07-29 18:47:48

●A20.42.128.1262026-07-29 → 2026-07-29 · 3 obs

○ 2026-03-30 10:56:52
● 2026-07-29 18:47:46
● 2026-07-29 18:47:48

○A76.223.105.2302026-03-13 → 2026-03-30 · 5 obs

○ 2020-02-12 18:53:14
● 2026-03-13 17:41:04
● 2026-03-30 10:56:52
○ 2026-07-29 18:47:46
○ 2026-07-29 18:47:48

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	h.gtld-servers.net, b.gtld-servers.net, a.gtld-servers.net, l.gtld-servers.net...	-
infinite-leverage.com	ns1-01.azure-dns.com, ns2-01.azure-dns.net, ns3-01.azure-dns.org, ns4-01.azure-dns.info	2 records

✅ Authoritative Response

Server:208.84.5.1

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for infinite-leverage.com (unsigned zone)

⏱️ Timing

Total: 402ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`20.42.128.126`
NS	4	`ns1-01.azure-dns.com, ns2-01.azure-dns.net...`
SOA	1	`ns1-01.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

infinite-leverage.com directs to one IP number, which is 20.42.128.126.

infinite-leverage.com shares its IP numbers with other host names like johnfoord.com, callpilotcrm.com and mail-srv25.johnfoord.com.

Name Servers

The domain infinite-leverage.com is delegated to these four name servers: ns1-01.azure-dns.com, ns4-01.azure-dns.info, ns2-01.azure-dns.net and ns3-01.azure-dns.org.

infinite-leverage.com has at least partial name server overlap with other domains, such as twelvetreasuresofsummer.com, groomandclean.us, omegaladymatic.kr and two others.

ns1-01.azure-dns.com, ns4-01.azure-dns.info, ns2-01.azure-dns.net and ns3-01.azure-dns.org all point to exactly two IP numbers each: ns1-01.azure-dns.com → 13.107.236.1 and 2603:1061:0:700::1; ns4-01.azure-dns.info → 208.84.5.1 and 2620:1ec:bda:700::1; ns2-01.azure-dns.net → 150.171.21.1 and 2620:1ec:8ec:700::1; ns3-01.azure-dns.org → 204.14.183.1 and 2a01:111:4000:700::1.