`cloudsociety-ms.net`

DNSSEC	⚠️ Not signed
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=1778533941

Same first word

cloudsociety-ms.com

cloudsociety-ms.net

DNS History

4 records (4 active, 0 former)

●NSns1-05.azure-dns.com2026-02-28 → 2026-05-11 · 2 obs

● 2026-02-28 15:32:32
● 2026-05-11 21:25:44

●NSns2-05.azure-dns.net2026-02-28 → 2026-05-11 · 2 obs

● 2026-02-28 15:32:32
● 2026-05-11 21:25:44

●NSns3-05.azure-dns.org2026-02-28 → 2026-05-11 · 2 obs

● 2026-02-28 15:32:32
● 2026-05-11 21:25:44

●NSns4-05.azure-dns.info2026-02-28 → 2026-05-11 · 2 obs

● 2026-02-28 15:32:32
● 2026-05-11 21:25:44

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
net	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
cloudsociety-ms.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:208.84.5.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 cloudsociety-ms.net (unsigned zone)

⏱️ Timing

Total: 211ms | Queries: -

📄 Records

Type	Count	Sample Data
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

Name Servers

cloudsociety-ms.net's delegation is handled by four name servers: ns1-05.azure-dns.com, ns4-05.azure-dns.info, ns2-05.azure-dns.net and ns3-05.azure-dns.org.

cloudsociety-ms.net partially shares name servers with other domains; examples include bingsearch.co, fppi.eu, gilbertdisplay.com, 152.28.46.in-addr.arpa and interexpress.cl.

Host names with two IPs:

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

cloudsociety-ms.net - robtex.com