`infinitereach.com`

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

Same first word

infinitereach.com

DNS History

10 records (4 active, 6 former)

●NSns1-04.azure-dns.com2026-03-28 → 2026-03-28 · 2 obs

○ 2017-02-17 19:33:48
● 2026-03-28 05:33:30

●NSns2-04.azure-dns.net2026-03-28 → 2026-03-28 · 2 obs

○ 2017-02-17 19:33:48
● 2026-03-28 05:33:30

●NSns3-04.azure-dns.org2026-03-28 → 2026-03-28 · 2 obs

○ 2017-02-17 19:33:48
● 2026-03-28 05:33:30

●NSns4-04.azure-dns.info2026-03-28 → 2026-03-28 · 2 obs

○ 2017-02-17 19:33:48
● 2026-03-28 05:33:30

○NSns43.domaincontrol.com2015-08-02 → 2017-02-17 · 3 obs

● 2015-08-02 10:18:00
● 2017-02-17 19:33:48
○ 2026-03-28 05:33:30

○NSns44.domaincontrol.com2015-08-02 → 2017-02-17 · 3 obs

● 2015-08-02 10:18:00
● 2017-02-17 19:33:48
○ 2026-03-28 05:33:30

○MXinfinitereach-com.mail.protection.outlook.com2015-08-02 → 2017-02-17 · 3 obs

● 2015-08-02 10:18:00
● 2017-02-17 19:33:48
○ 2026-03-28 05:33:30

○A15.197.148.332026-03-28 → 2026-03-28 · 1 obs

○ 2026-03-28 05:33:30

○A160.153.73.2332015-08-02 → 2017-02-17 · 3 obs

● 2015-08-02 10:18:00
● 2017-02-17 19:33:48
○ 2026-03-28 05:33:30

○A3.33.130.1902026-03-28 → 2026-03-28 · 1 obs

○ 2026-03-28 05:33:30

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	j.gtld-servers.net, h.gtld-servers.net, c.gtld-servers.net, f.gtld-servers.net...	-
infinitereach.com	ns1-04.azure-dns.com, ns2-04.azure-dns.net, ns3-04.azure-dns.org, ns4-04.azure-dns.info	2 records

✅ Authoritative Response

Server:150.171.21.4

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for infinitereach.com (unsigned zone)

⏱️ Timing

Total: 80ms | Queries: -

📄 Records

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

📌 Glue Records Collected

Total: 2

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

Analysis

Name Servers

infinitereach.com is delegated to four name servers: ns1-04.azure-dns.com, ns4-04.azure-dns.info, ns2-04.azure-dns.net and ns3-04.azure-dns.org.

infinitereach.com at least partially shares name servers with other domains, for instance al(0x666170)eople.co.cr, valalimentos.com.br, tinglesa.com, microsoftvsteamservices.com and passiria.net.

Host names with two IP numbers:

Host name ns1-04.azure-dns.com points to: 2603:1061:0:700::4 and 13.107.236.4.

Host name ns4-04.azure-dns.info points to: 2620:1ec:bda:700::4 and 208.84.5.4.

Host name ns2-04.azure-dns.net points to: 2620:1ec:8ec:700::4 and 150.171.21.4.

Host name ns3-04.azure-dns.org points to: 2a01:111:4000:700::4 and 204.14.183.4.

infinitereach.com - robtex.com