`servicesconnector.net`

DNSSEC	⚠️ Not signed
NS	`ns1-06.azure-dns.com` ⭐
		A	2603:1061:0:700::6^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-06.azure-dns.com`
		A	13.107.236.6^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-06.azure-dns.com`
NS	`ns2-06.azure-dns.net`
		A	2620:1ec:8ec:700::6^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-06.azure-dns.net`
		A	150.171.21.6^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-06.azure-dns.net`
NS	`ns3-06.azure-dns.org`
		A	2a01:111:4000:700::6^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-06.azure-dns.org`
		A	204.14.183.6^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-06.azure-dns.org`
NS	`ns4-06.azure-dns.info`
		A	2620:1ec:bda:700::6^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-06.azure-dns.info`
		A	208.84.5.6^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-06.azure-dns.info`
SOA	`ns1-06.azure-dns.com`azuredns-hostmaster@microsoft.com serial=1

`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=1771291465

Same first word

servicesconnector.net

servicesconnector.com

servicesconnector.org

Similar names

controversciences.s3.amazonaws.com

DNS History

8 records (4 active, 4 former)

●NSns1-06.azure-dns.com2026-02-28 → 2026-03-23 · 3 obs

○ 2018-08-03 03:22:40
● 2026-02-28 16:28:46
● 2026-03-23 23:58:56

○NSns1.msft.net2015-07-12 → 2018-08-03 · 4 obs

● 2015-07-12 02:34:36
● 2018-08-03 03:22:40
○ 2026-02-28 16:28:46
○ 2026-03-23 23:58:56

●NSns2-06.azure-dns.net2026-02-28 → 2026-03-23 · 3 obs

○ 2018-08-03 03:22:40
● 2026-02-28 16:28:46
● 2026-03-23 23:58:56

○NSns2.msft.net2015-07-12 → 2018-08-03 · 4 obs

● 2015-07-12 02:34:36
● 2018-08-03 03:22:40
○ 2026-02-28 16:28:46
○ 2026-03-23 23:58:56

●NSns3-06.azure-dns.org2026-02-28 → 2026-03-23 · 3 obs

○ 2018-08-03 03:22:40
● 2026-02-28 16:28:46
● 2026-03-23 23:58:56

○NSns3.msft.net2015-07-12 → 2018-08-03 · 4 obs

● 2015-07-12 02:34:36
● 2018-08-03 03:22:40
○ 2026-02-28 16:28:46
○ 2026-03-23 23:58:56

●NSns4-06.azure-dns.info2026-02-28 → 2026-03-23 · 3 obs

○ 2018-08-03 03:22:40
● 2026-02-28 16:28:46
● 2026-03-23 23:58:56

○NSns4.msft.net2015-07-12 → 2018-08-03 · 4 obs

● 2015-07-12 02:34:36
● 2018-08-03 03:22:40
○ 2026-02-28 16:28:46
○ 2026-03-23 23:58:56

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	c.gtld-servers.net, j.gtld-servers.net, b.gtld-servers.net, f.gtld-servers.net...	-
servicesconnector.net	ns1-06.azure-dns.com, ns2-06.azure-dns.net, ns3-06.azure-dns.org, ns4-06.azure-dns.info	2 records

✅ Authoritative Response

Server:204.14.183.6

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for servicesconnector.net (unsigned zone)

⏱️ Timing

Total: 757ms | Queries: -

📄 Records

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

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns2-06.azure-dns.net, ns2-06.azure-dns.net)

Analysis

Name Servers

servicesconnector.net delegates to four name servers: ns1-06.azure-dns.com, ns4-06.azure-dns.info, ns2-06.azure-dns.net and ns3-06.azure-dns.org.

servicesconnector.net at least partially shares name servers with other domains, for instance gigamon.com.br, gillette.com.gt, emsdemo57.com, ioestetista.it and rogersootf.com.

Host names with two IP numbers: ns1-06.azure-dns.com points to 2603:1061:0:700::6 and 13.107.236.6; ns4-06.azure-dns.info points to 2620:1ec:bda:700::6 and 208.84.5.6; ns2-06.azure-dns.net points to 2620:1ec:8ec:700::6 and 150.171.21.6; ns3-06.azure-dns.org points to 2a01:111:4000:700::6 and 204.14.183.6.

servicesconnector.net - robtex.com