`mydemandconnection.com`

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

Same first word

mydemandconnection.com

DNS History

6 records (4 active, 2 former)

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

○ 2020-02-19 19:50:38
● 2026-07-01 01:15:30
● 2026-07-19 07:52:58

○NSns1.techdata.com2008-03-15 → 2020-02-19 · 4 obs

● 2008-03-15 13:40:52
● 2020-02-19 19:50:38
○ 2026-07-01 01:15:30
○ 2026-07-19 07:52:58

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

○ 2020-02-19 19:50:38
● 2026-07-01 01:15:30
● 2026-07-19 07:52:58

○NSns2.techdata.com2008-03-15 → 2020-02-19 · 4 obs

● 2008-03-15 13:40:52
● 2020-02-19 19:50:38
○ 2026-07-01 01:15:30
○ 2026-07-19 07:52:58

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

○ 2020-02-19 19:50:38
● 2026-07-01 01:15:30
● 2026-07-19 07:52:58

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

○ 2020-02-19 19:50:38
● 2026-07-01 01:15:30
● 2026-07-19 07:52:58

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, m.gtld-servers.net, h.gtld-servers.net, g.gtld-servers.net...	-
mydemandconnection.com	ns1-09.azure-dns.com, ns2-09.azure-dns.net, ns3-09.azure-dns.org, ns4-09.azure-dns.info	2 records

✅ Authoritative Response

Server:208.84.5.9

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for mydemandconnection.com (unsigned zone)

⏱️ Timing

Total: 199ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1-09.azure-dns.com, ns2-09.azure-dns.net...`
TXT	1	`v=spf1 -all`
SOA	1	`ns1-09.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

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

Analysis

Name Servers

The NS records for mydemandconnection.com point to four name servers: ns1-09.azure-dns.com, ns4-09.azure-dns.info, ns2-09.azure-dns.net and ns3-09.azure-dns.org.

mydemandconnection.com shares at least some of its name servers with other domains, including 208.172.in-addr.arpa, bingrebates.com, nnidsi.com and two others.

The host names ns1-09.azure-dns.com, ns4-09.azure-dns.info, ns2-09.azure-dns.net and ns3-09.azure-dns.org each resolve to two IP addresses: ns1-09.azure-dns.com resolves to 13.107.236.9 and 2603:1061:0:700::9; ns4-09.azure-dns.info resolves to 208.84.5.9 and 2620:1ec:bda:700::9; ns2-09.azure-dns.net resolves to 150.171.21.9 and 2620:1ec:8ec:700::9; ns3-09.azure-dns.org resolves to 204.14.183.9 and 2a01:111:4000:700::9.

mydemandconnection.com - robtex.com