`communicationsserverlaunch.net`

DNSSEC	⚠️ Not signed
A	20.70.246.20^{🇦🇺 Microsoft20.64.0.0/10}
A	20.76.201.171^{🇳🇱 Microsoft20.64.0.0/10}
A	20.112.250.133^{🇺🇸 Microsoft20.64.0.0/10}
A	20.231.239.246^{🇺🇸 Microsoft20.192.0.0/10}
A	20.236.44.162^{🇺🇸 Microsoft20.192.0.0/10}
NS	`ns1-05.azure-dns.com` ⭐
		A	2603:1061:0:700::5^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-05.azure-dns.com`
		A	13.107.236.5^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns1-05.azure-dns.com`
NS	`ns2-05.azure-dns.net`
		A	2620:1ec:8ec:700::5^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-05.azure-dns.net`
		A	150.171.21.5^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-05.azure-dns.net`
NS	`ns3-05.azure-dns.org`
		A	2a01:111:4000:700::5^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-05.azure-dns.org`
		A	204.14.183.5^{🇺🇸 Microsoft204.14.180.0/22}
			PTR	`ns3-05.azure-dns.org`
NS	`ns4-05.azure-dns.info`
		A	2620:1ec:bda:700::5^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-05.azure-dns.info`
		A	208.84.5.5^{🇺🇸 Microsoft208.84.0.0/21 MICROSOFT}
			PTR	`ns4-05.azure-dns.info`
SOA	`ns1-05.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

communicationsserverlaunch.net

communicationsserverlaunch.com

DNS History

17 records (9 active, 8 former)

●NSns1-05.azure-dns.com2026-02-28 → 2026-03-17 · 3 obs

○ 2017-12-26 15:32:16
● 2026-02-28 17:46:16
● 2026-03-17 20:23:26

○NSns1.msft.net2015-07-12 → 2017-12-26 · 4 obs

● 2015-07-12 18:17:26
● 2017-12-26 15:32:16
○ 2026-02-28 17:46:16
○ 2026-03-17 20:23:26

●NSns2-05.azure-dns.net2026-02-28 → 2026-03-17 · 3 obs

○ 2017-12-26 15:32:16
● 2026-02-28 17:46:16
● 2026-03-17 20:23:26

○NSns2.msft.net2015-07-12 → 2017-12-26 · 4 obs

● 2015-07-12 18:17:26
● 2017-12-26 15:32:16
○ 2026-02-28 17:46:16
○ 2026-03-17 20:23:26

●NSns3-05.azure-dns.org2026-02-28 → 2026-03-17 · 3 obs

○ 2017-12-26 15:32:16
● 2026-02-28 17:46:16
● 2026-03-17 20:23:26

○NSns3.msft.net2015-07-12 → 2017-12-26 · 4 obs

● 2015-07-12 18:17:26
● 2017-12-26 15:32:16
○ 2026-02-28 17:46:16
○ 2026-03-17 20:23:26

●NSns4-05.azure-dns.info2026-02-28 → 2026-03-17 · 3 obs

○ 2017-12-26 15:32:16
● 2026-02-28 17:46:16
● 2026-03-17 20:23:26

○NSns4.msft.net2015-07-12 → 2017-12-26 · 4 obs

● 2015-07-12 18:17:26
● 2017-12-26 15:32:16
○ 2026-02-28 17:46:16
○ 2026-03-17 20:23:26

●A20.112.250.1332026-02-28 → 2026-03-17 · 3 obs

○ 2017-12-26 15:32:16
● 2026-02-28 17:46:16
● 2026-03-17 20:23:26

●A20.231.239.2462026-02-28 → 2026-03-17 · 3 obs

○ 2017-12-26 15:32:16
● 2026-02-28 17:46:16
● 2026-03-17 20:23:26

●A20.236.44.1622026-02-28 → 2026-03-17 · 3 obs

○ 2017-12-26 15:32:16
● 2026-02-28 17:46:16
● 2026-03-17 20:23:26

●A20.70.246.202026-02-28 → 2026-03-17 · 3 obs

○ 2017-12-26 15:32:16
● 2026-02-28 17:46:16
● 2026-03-17 20:23:26

●A20.76.201.1712026-02-28 → 2026-03-17 · 3 obs

○ 2017-12-26 15:32:16
● 2026-02-28 17:46:16
● 2026-03-17 20:23:26

○A40.84.199.2332017-01-02 → 2017-12-26 · 5 obs

○ 2016-04-22 08:30:30
● 2017-01-02 15:19:32
● 2017-12-26 15:32:16
○ 2026-02-28 17:46:16
○ 2026-03-17 20:23:26

○A52.178.167.1092017-01-02 → 2017-12-26 · 5 obs

○ 2016-04-22 08:30:30
● 2017-01-02 15:19:32
● 2017-12-26 15:32:16
○ 2026-02-28 17:46:16
○ 2026-03-17 20:23:26

○A64.4.6.1002015-07-12 → 2016-04-22 · 4 obs

● 2015-07-12 18:17:26
● 2016-04-22 08:30:30
○ 2017-01-02 15:19:32
○ 2026-03-17 20:23:26

○A65.55.39.102015-07-12 → 2016-04-22 · 4 obs

● 2015-07-12 18:17:26
● 2016-04-22 08:30:30
○ 2017-01-02 15:19:32
○ 2026-03-17 20:23:26

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	c.gtld-servers.net, a.gtld-servers.net, k.gtld-servers.net, m.gtld-servers.net...	-
communicationsserverlaunch.net	ns1-05.azure-dns.com, ns2-05.azure-dns.net, ns3-05.azure-dns.org, ns4-05.azure-dns.info	2 records

✅ Authoritative Response

Server: 13.107.236.5

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for communicationsserverlaunch.net (unsigned zone)

⏱️ Timing

Total: 750ms | Queries: -

📄 Records

Type	Count	Sample Data
A	5	`20.76.201.171, 20.112.250.133...`
NS	4	`ns1-05.azure-dns.com, ns2-05.azure-dns.net...`
SOA	1	`ns1-05.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

Five IP numbers are pointed to by communicationsserverlaunch.net: 20.70.246.20, 20.76.201.171, 20.112.250.133, 20.231.239.246 and 20.236.44.162.

other host names including bingyahoonetwork.co.in, microsoftstudiosblog.com, rare.net, skypecasting.dk and windows.com.cn share IP numbers with communicationsserverlaunch.net.

Name Servers

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

communicationsserverlaunch.net at least partially shares name servers with other domains, for instance sd72.bc.ca, isvcentral.com, ctmna-apps.net, setnoise.com and onnephroflow.com.

Host names with two IP numbers:

ns1-05.azure-dns.com points to 2603:1061:0:700::5 and 13.107.236.5; ns4-05.azure-dns.info points to 2620:1ec:bda:700::5 and 208.84.5.5; ns2-05.azure-dns.net points to 2620:1ec:8ec:700::5 and 150.171.21.5; ns3-05.azure-dns.org points to 2a01:111:4000:700::5 and 204.14.183.5.

communicationsserverlaunch.net - robtex.com