`silocompliancecloud.com`

DNSSEC	⚠️ Not signed
NS	`ns1-03.azure-dns.com` ⭐
		A	2603:1061:0:700::3^{🇺🇸 Microsoft}
			PTR	`ns1-03.azure-dns.com`
		A	13.107.236.3^{🇺🇸 Microsoft}
			PTR	`ns1-03.azure-dns.com`
NS	`ns2-03.azure-dns.net`
		A	2620:1ec:8ec:700::3^{🇺🇸 Microsoft}
			PTR	`ns2-03.azure-dns.net`
		A	150.171.21.3^{🇺🇸 Microsoft}
			PTR	`ns2-03.azure-dns.net`
NS	`ns3-03.azure-dns.org`
		A	2a01:111:4000:700::3^{🇬🇧 Microsoft}
			PTR	`ns3-03.azure-dns.org`
		A	204.14.183.3^{🇺🇸 Microsoft}
			PTR	`ns3-03.azure-dns.org`
NS	`ns4-03.azure-dns.info`
		A	2620:1ec:bda:700::3^{🇺🇸 Microsoft}
			PTR	`ns4-03.azure-dns.info`
		A	208.84.5.3^{🇺🇸 Microsoft}
			PTR	`ns4-03.azure-dns.info`
SOA	`ns1-03.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=1771291435

Same first word

silocompliancecloud.com

DNS History

7 records (4 active, 3 former)

●NSns1-03.azure-dns.com2026-02-20 → 2026-02-20 · 3 obs

○ 2019-04-25 18:05:48
● 2026-02-20 10:34:06
● 2026-02-20 13:23:38

●NSns2-03.azure-dns.net2026-02-20 → 2026-02-20 · 3 obs

○ 2019-04-25 18:05:48
● 2026-02-20 10:34:06
● 2026-02-20 13:23:38

●NSns3-03.azure-dns.org2026-02-20 → 2026-02-20 · 3 obs

○ 2019-04-25 18:05:48
● 2026-02-20 10:34:06
● 2026-02-20 13:23:38

○NSns35.domaincontrol.com2019-04-25 → 2019-04-25 · 3 obs

● 2019-04-25 18:05:48
○ 2026-02-20 10:34:06
○ 2026-02-20 13:23:38

○NSns36.domaincontrol.com2019-04-25 → 2019-04-25 · 3 obs

● 2019-04-25 18:05:48
○ 2026-02-20 10:34:06
○ 2026-02-20 13:23:38

●NSns4-03.azure-dns.info2026-02-20 → 2026-02-20 · 3 obs

○ 2019-04-25 18:05:48
● 2026-02-20 10:34:06
● 2026-02-20 13:23:38

○A184.168.221.632019-04-25 → 2019-04-25 · 3 obs

● 2019-04-25 18:05:48
○ 2026-02-20 10:34:06
○ 2026-02-20 13:23:38

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
silocompliancecloud.com	ns1-03.azure-dns.com, ns2-03.azure-dns.net, ns3-03.azure-dns.org, ns4-03.azure-dns.info	2 records

✅ Authoritative Response

Server: 204.14.183.3

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for silocompliancecloud.com (unsigned zone)

⏱️ Timing

Total: 321ms | Queries: -

📄 Records

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

📌 Glue Records Collected

Total: 2

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

AI analysis

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

silocompliancecloud.com at least partially shares name servers with other domains, for example myntkabinettet.se, floatingforests.org, dae-dev.azure.rabo.cloud, lcepaper.com.tw and hotmailupdateteam.org.

Host names with two IP numbers:

ns1-03.azure-dns.com points to: 2603:1061:0:700::3 and 13.107.236.3

ns4-03.azure-dns.info points to: 2620:1ec:bda:700::3 and 208.84.5.3

ns2-03.azure-dns.net points to: 2620:1ec:8ec:700::3 and 150.171.21.3

ns3-03.azure-dns.org points to: 2a01:111:4000:700::3 and 204.14.183.3

silocompliancecloud.com - robtex.com