leadshift.net - dns.ninja

`leadshift.net`

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 2620:4D:4000::/48}
			PTR	`dns1.p01.nsone.net`
		A	198.51.44.1^{🇺🇸 NSONE198.51.44.0/24 198.51.44.0}
			PTR	`dns1.p01.nsone.net`
NS	`dns1.p03.nsone.net`
		A	2620:4d:4000:6259:7:3:0:1^{🇺🇸 NSONE2620:4d:4000::/48 2620:4D:4000::/48}
			PTR	`dns1.p03.nsone.net`
		A	198.51.44.3^{🇺🇸 NSONE198.51.44.0/24 198.51.44.0}
			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 198.51.45.0}
			PTR	`dns2.p03.nsone.net`
NS	`dns3.p03.nsone.net`
		A	2620:4d:4000:6259:7:3:0:3^{🇺🇸 NSONE2620:4d:4000::/48 2620:4D:4000::/48}
			PTR	`dns3.p03.nsone.net`
		A	198.51.44.67^{🇺🇸 NSONE198.51.44.0/24 198.51.44.0}
			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 198.51.45.0}
			PTR	`dns4.p03.nsone.net`
SOA	`dns1.p01.nsone.net`domains+netlify@netlify.com serial=1774367850

`net`

	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=1782901066

Same first word

leadshift.net

Similar names

DNS History

14 records (7 active, 7 former)

●NSdns1.p01.nsone.net2026-03-27 → 2026-07-01 · 3 obs

○ 2017-05-04 20:30:16
● 2026-03-27 06:33:08
● 2026-07-01 10:37:54

●NSdns1.p03.nsone.net2026-03-27 → 2026-07-01 · 3 obs

○ 2017-05-04 20:30:16
● 2026-03-27 06:33:08
● 2026-07-01 10:37:54

●NSdns2.p03.nsone.net2026-03-27 → 2026-07-01 · 3 obs

○ 2017-05-04 20:30:16
● 2026-03-27 06:33:08
● 2026-07-01 10:37:54

●NSdns3.p03.nsone.net2026-03-27 → 2026-07-01 · 3 obs

○ 2017-05-04 20:30:16
● 2026-03-27 06:33:08
● 2026-07-01 10:37:54

●NSdns4.p03.nsone.net2026-03-27 → 2026-07-01 · 3 obs

○ 2017-05-04 20:30:16
● 2026-03-27 06:33:08
● 2026-07-01 10:37:54

○NSns51.domaincontrol.com2015-07-12 → 2017-05-04 · 4 obs

● 2015-07-12 18:39:04
● 2017-05-04 20:30:16
○ 2026-03-27 06:33:08
○ 2026-07-01 10:37:54

○NSns52.domaincontrol.com2015-07-12 → 2017-05-04 · 4 obs

● 2015-07-12 18:39:04
● 2017-05-04 20:30:16
○ 2026-03-27 06:33:08
○ 2026-07-01 10:37:54

○MXmailstore1.secureserver.net2015-07-12 → 2017-05-04 · 4 obs

● 2015-07-12 18:39:04
● 2017-05-04 20:30:16
○ 2026-03-27 06:33:08
○ 2026-07-01 10:37:54

○MXsmtp.secureserver.net2015-07-12 → 2017-05-04 · 4 obs

● 2015-07-12 18:39:04
● 2017-05-04 20:30:16
○ 2026-03-27 06:33:08
○ 2026-07-01 10:37:54

○A13.52.188.952026-03-27 → 2026-04-02 · 5 obs

○ 2017-05-04 20:30:16
● 2026-03-27 06:33:08
○ 2026-03-29 21:17:32
● 2026-04-02 11:09:40
○ 2026-07-01 10:37:54

●A18.208.88.1572026-03-29 → 2026-07-01 · 4 obs

○ 2026-03-27 06:33:08
● 2026-03-29 21:17:32
○ 2026-04-02 11:09:40
● 2026-07-01 10:37:54

○A52.52.192.1912026-03-27 → 2026-04-02 · 5 obs

○ 2017-05-04 20:30:16
● 2026-03-27 06:33:08
○ 2026-03-29 21:17:32
● 2026-04-02 11:09:40
○ 2026-07-01 10:37:54

○A97.74.144.2032015-07-12 → 2017-05-04 · 4 obs

● 2015-07-12 18:39:04
● 2017-05-04 20:30:16
○ 2026-03-27 06:33:08
○ 2026-07-01 10:37:54

●A98.84.224.1112026-03-29 → 2026-07-01 · 4 obs

○ 2026-03-27 06:33:08
● 2026-03-29 21:17:32
○ 2026-04-02 11:09:40
● 2026-07-01 10:37:54

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	c.gtld-servers.net, f.gtld-servers.net, b.gtld-servers.net, l.gtld-servers.net...	-
leadshift.net	dns1.p03.nsone.net, dns2.p03.nsone.net, dns3.p03.nsone.net, dns4.p03.nsone.net	8 records

✅ Authoritative Response

Server:198.51.44.3

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 leadshift.net (unsigned zone)

⏱️ Timing

Total: 132ms | 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`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (dns1.p03.nsone.net, dns1.p03.nsone.net, dns2.p03.nsone.net...)

Analysis

IP Addresses

leadshift.net points to the IP addresses 18.208.88.157 and 98.84.224.111

Additional host names — srthk.com, stuffzz.com, japacrunch.com and two others — share IP numbers with leadshift.net.

Name Servers

Delegation for leadshift.net is to five name servers: dns1.p01.nsone.net, dns1.p03.nsone.net, dns2.p03.nsone.net and two others.

There is at least partial name server overlap between leadshift.net and other domains — cancommit.com, adiaart.com, oahurentalmanagement.com and two more among them.

These name servers regularly appear alongside dns3.p03.nsone.net, dns4.p03.nsone.net, ns02.squarespacedns.com and 7 other name servers in NS record sets.

Host names with two IP numbers:

dns1.p01.nsone.net maps to two IP addresses — 198.51.44.1 and 2620:4d:4000:6259:7:1:0:1.

dns1.p03.nsone.net maps to two IP addresses — 198.51.44.3 and 2620:4d:4000:6259:7:3:0:1.

dns2.p03.nsone.net maps to two IP addresses — 198.51.45.3 and 2a00:edc0:6259:7:3::2.

dns3.p03.nsone.net maps to two IP addresses — 198.51.44.67 and 2620:4d:4000:6259:7:3:0:3.

dns4.p03.nsone.net maps to two IP addresses — 198.51.45.67 and 2a00:edc0:6259:7:3::4.