🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`structurecloud.com`

DNSSEC	⚠️ Not signed
NS	`ns1-34.azure-dns.com` ⭐
		A	2603:1061:0:10::22^{🇺🇸 Microsoft2603:1000::/25 MICROSOFT}
			PTR	`ns1-34.azure-dns.com`
		A	150.171.10.34^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns1-34.azure-dns.com`
NS	`ns2-34.azure-dns.net`
		A	2620:1ec:8ec:10::22^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns2-34.azure-dns.net`
		A	150.171.16.34^{🇺🇸 Microsoft150.171.0.0/16 MICROSOFT}
			PTR	`ns2-34.azure-dns.net`
NS	`ns3-34.azure-dns.org`
		A	2a01:111:4000:10::22^{🇬🇧 Microsoft2a01:111:4000::/36}
			PTR	`ns3-34.azure-dns.org`
		A	13.107.222.34^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns3-34.azure-dns.org`
NS	`ns4-34.azure-dns.info`
		A	2620:1ec:bda:10::22^{🇺🇸 Microsoft2620:1ec::/36 MICROSOFT}
			PTR	`ns4-34.azure-dns.info`
		A	13.107.206.34^{🇺🇸 Microsoft13.104.0.0/14 MICROSOFT}
			PTR	`ns4-34.azure-dns.info`
MX	`structurecloud-com.mail.protection.outlook.com` ⭐
		A	2a01:111:f403:c902::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-sj2pr05cu00300.inbound.protection.outlook.com`
		A	2a01:111:f403:c91d::^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-mw2pr04cu00100.inbound.protection.outlook.com`
		A	2a01:111:f403:c91d::2^{🇺🇸 Microsoft2a01:111:f000::/36}
			PTR	`mail-mw6pr05cu00102.inbound.protection.outlook.com`
		A	2a01:111:f403:c95d::8^{🇬🇧 Microsoft2a01:111:f000::/36}
			PTR	`mail-ph8pr21cu00200.inbound.protection.outlook.com`
		A	52.101.9.84^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-mn0pr04cu00204.inbound.protection.outlook.com`
		A	52.101.9.90^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-bl3pr02cu00102.inbound.protection.outlook.com`
		A	52.101.41.3^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
		A	52.101.41.122^{🇺🇸 Microsoft52.96.0.0/12 MICROSOFT}
			PTR	`mail-byapr02cu00302.inbound.protection.outlook.com`
TXT	`MS=ms93268586`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
SOA	`ns1-34.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=1794632781

Same first word

structurecloud.co

structurecloud.org

structurecloud.ai

structurecloud.com

Similar names

cloudstructure.co

culturedcourts.com

cloudstructure.com

cloudstructure.de

cloudstructure.ai

Previous names

Next names

DNS History

10 records (5 active, 5 former)

●NSns1-34.azure-dns.com2026-09-30 → 2026-11-14 · 3 obs

○ 2017-09-02 23:49:34
● 2026-09-30 20:48:44
● 2026-11-14 05:22:30

○NSns1.sedoparking.com2015-06-13 → 2017-09-02 · 4 obs

● 2015-06-13 03:52:50
● 2017-09-02 23:49:34
○ 2026-09-30 20:48:44
○ 2026-11-14 05:22:30

●NSns2-34.azure-dns.net2026-09-30 → 2026-11-14 · 3 obs

○ 2017-09-02 23:49:34
● 2026-09-30 20:48:44
● 2026-11-14 05:22:30

○NSns2.sedoparking.com2015-06-13 → 2017-09-02 · 4 obs

● 2015-06-13 03:52:50
● 2017-09-02 23:49:34
○ 2026-09-30 20:48:44
○ 2026-11-14 05:22:30

●NSns3-34.azure-dns.org2026-09-30 → 2026-11-14 · 3 obs

○ 2017-09-02 23:49:34
● 2026-09-30 20:48:44
● 2026-11-14 05:22:30

●NSns4-34.azure-dns.info2026-09-30 → 2026-11-14 · 3 obs

○ 2017-09-02 23:49:34
● 2026-09-30 20:48:44
● 2026-11-14 05:22:30

○MXlocalhost2016-12-03 → 2017-09-02 · 5 obs

○ 2016-04-07 10:59:34
● 2016-12-03 15:11:06
● 2017-09-02 23:49:34
○ 2026-09-30 20:48:44
○ 2026-11-14 05:22:30

○MXmail.nickstel.com2015-06-13 → 2016-04-07 · 4 obs

● 2015-06-13 03:52:50
● 2016-04-07 10:59:34
○ 2016-12-03 15:11:06
○ 2026-11-14 05:22:30

●MXstructurecloud-com.mail.protection.outlook.com2026-09-30 → 2026-11-14 · 3 obs

○ 2017-09-02 23:49:34
● 2026-09-30 20:48:44
● 2026-11-14 05:22:30

○A72.52.4.1192015-06-13 → 2017-09-02 · 4 obs

● 2015-06-13 03:52:50
● 2017-09-02 23:49:34
○ 2026-09-30 20:48:44
○ 2026-11-14 05:22:30

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, h.gtld-servers.net, k.gtld-servers.net, j.gtld-servers.net...	-
structurecloud.com	ns4-34.azure-dns.info, ns1-34.azure-dns.com, ns2-34.azure-dns.net, ns3-34.azure-dns.org	2 records

✅ Authoritative Response

Server:13.107.222.34

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

Root DNSKEY fetch failed: Error: connect EADDRNOTAVAIL 198.41.0.4:53 - Local (0.0.0.0:0)

⏱️ Timing

Total: 1268ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1-34.azure-dns.com, ns2-34.azure-dns.net...`
MX	1	`structurecloud-com.mail.protection.outlo`
TXT	2	`MS=ms93268586, v=spf1 include:spf.protection.outlook.co`
SOA	1	`ns1-34.azure-dns.com azuredns-hostmaster`

📌 Glue Records Collected

Total: 2

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

Analysis

Name Servers

The authoritative name servers for structurecloud.com are ns1-34.azure-dns.com, ns4-34.azure-dns.info, ns2-34.azure-dns.net and ns3-34.azure-dns.org.

There is at least partial name server overlap between structurecloud.com and other domains — norwalkrab.com, jamstudio.be, mlbrandportal.com and two more among them.

These name servers are routinely deployed together with the name servers ns4-38.azure-dns.info.

All four hostnames — ns1-34.azure-dns.com, ns4-34.azure-dns.info, ns2-34.azure-dns.net and ns3-34.azure-dns.org — resolve to two IP numbers apiece: ns1-34.azure-dns.com to 150.171.10.34 and 2603:1061:0:10::22; ns4-34.azure-dns.info to 13.107.206.34 and 2620:1ec:bda:10::22; ns2-34.azure-dns.net to 150.171.16.34 and 2620:1ec:8ec:10::22; ns3-34.azure-dns.org to 13.107.222.34 and 2a01:111:4000:10::22.

Mail Servers

Mail for structurecloud.com is handled by a single mail server, structurecloud-com.mail.protection.outlook.com.

structurecloud-com.mail.protection.outlook.com resolves to 8 IP addresses — 52.101.9.84, 52.101.9.90, 52.101.41.3 and 5 others.

structurecloud.com - robtex.com