cloudconstructionsd.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`cloudconstructionsd.com`

DNSSEC	⚠️ Not signed
A	216.150.1.1^{🇨🇦 Amazon216.150.1.0/24 EC2 Prefix}
NS	`ns05.domaincontrol.com` ⭐
		A	2603:5:2160::3^{🇺🇸 GODADDY-DNS2603:5:2160::/44}
			PTR	`ns05.domaincontrol.com`
		A	97.74.102.3^{🇺🇸 GODADDY-DNS97.74.102.0/23}
			PTR	`ns05.domaincontrol.com`
NS	`ns06.domaincontrol.com`
		A	2603:5:2260::3^{🇺🇸 GODADDY-DNS2603:5:2260::/44}
			PTR	`ns06.domaincontrol.com`
		A	173.201.70.3^{🇺🇸 GODADDY-DNS173.201.70.0/23}
			PTR	`ns06.domaincontrol.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c19::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bk-in-f26.1e100.net`
		A	64.233.180.26^{🇺🇸 Google64.233.180.0/24}
			PTR	`on-in-f26.1e100.net`
			PTR	`pe-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽²⁰⁾
		A	2800:3f0:4003:c14::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.26^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽³⁰⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`aspmx2.googlemail.com`⁽⁴⁰⁾
		A	2800:3f0:4003:c14::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.26^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f26.1e100.net`
MX	`aspmx3.googlemail.com`⁽⁵⁰⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
TXT	`NETORGFT4808932.onmicrosoft.com`
TXT	`v=spf1 include:spf.protection.outlook.com -all`
TXT	`google-site-verification=KZeuoAs3B2V-Livwqmj39tbsN9gteug1ytDM9D4bKK0`
SOA	`ns05.domaincontrol.com`dns@jomax.net 2026-06-22 #3

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

Same first word

cloudconstructionsd.com

Previous names

Next names

DNS History

16 records (8 active, 8 former)

●NSns05.domaincontrol.com2019-02-18 → 2026-10-01 · 2 obs

● 2019-02-18 20:26:06
● 2026-10-01 10:38:40

●NSns06.domaincontrol.com2019-02-18 → 2026-10-01 · 2 obs

● 2019-02-18 20:26:06
● 2026-10-01 10:38:40

●MXalt1.aspmx.l.google.com2019-02-18 → 2026-10-01 · 2 obs

● 2019-02-18 20:26:06
● 2026-10-01 10:38:40

●MXalt2.aspmx.l.google.com2019-02-18 → 2026-10-01 · 2 obs

● 2019-02-18 20:26:06
● 2026-10-01 10:38:40

●MXaspmx.l.google.com2019-02-18 → 2026-10-01 · 2 obs

● 2019-02-18 20:26:06
● 2026-10-01 10:38:40

●MXaspmx2.googlemail.com2019-02-18 → 2026-10-01 · 2 obs

● 2019-02-18 20:26:06
● 2026-10-01 10:38:40

●MXaspmx3.googlemail.com2019-02-18 → 2026-10-01 · 2 obs

● 2019-02-18 20:26:06
● 2026-10-01 10:38:40

○A184.168.221.362019-02-18 → 2019-02-18 · 3 obs

● 2019-02-18 20:26:06
○ 2026-08-31 05:57:10
○ 2026-10-01 10:38:40

●A216.150.1.12026-08-31 → 2026-10-01 · 3 obs

○ 2019-02-18 20:26:06
● 2026-08-31 05:57:10
● 2026-10-01 10:38:40

○A50.63.202.322019-02-18 → 2019-02-18 · 3 obs

● 2019-02-18 20:26:06
○ 2026-08-31 05:57:10
○ 2026-10-01 10:38:40

○A50.63.202.372019-02-18 → 2019-02-18 · 3 obs

● 2019-02-18 20:26:06
○ 2026-08-31 05:57:10
○ 2026-10-01 10:38:40

○A50.63.202.382019-02-18 → 2019-02-18 · 3 obs

● 2019-02-18 20:26:06
○ 2026-08-31 05:57:10
○ 2026-10-01 10:38:40

○A50.63.202.452019-02-18 → 2019-02-18 · 3 obs

● 2019-02-18 20:26:06
○ 2026-08-31 05:57:10
○ 2026-10-01 10:38:40

○A50.63.202.552019-02-18 → 2019-02-18 · 3 obs

● 2019-02-18 20:26:06
○ 2026-08-31 05:57:10
○ 2026-10-01 10:38:40

○A50.63.202.582019-02-18 → 2019-02-18 · 3 obs

● 2019-02-18 20:26:06
○ 2026-08-31 05:57:10
○ 2026-10-01 10:38:40

○A50.63.202.592019-02-18 → 2019-02-18 · 3 obs

● 2019-02-18 20:26:06
○ 2026-08-31 05:57:10
○ 2026-10-01 10:38:40

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
cloudconstructionsd.com	ns05.domaincontrol.com, ns06.domaincontrol.com	4 records

✅ Authoritative Response

Server:173.201.70.3

NS records: ns05.domaincontrol.com, ns06.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for cloudconstructionsd.com (unsigned zone)

⏱️ Timing

Total: 235ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`216.150.1.1`
NS	2	`ns05.domaincontrol.com, ns06.domaincontrol.com`
MX	5	`aspmx.l.google.com (pri: 10), alt1.aspmx.l.google.com (pri: 20)...`
TXT	3	`NETORGFT4808932.onmicrosoft.com, v=spf1 include:spf.protection.outlook.co...`
SOA	1	`ns05.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns05.domaincontrol.com, ns05.domaincontrol.com, ns06.domaincontrol.com...)

Analysis

IP Addresses

cloudconstructionsd.com resolves to one IP address: 216.150.1.1.

ellytic.ae, leenova.fr, americanminingnews.com and two other host names share IP numbers with cloudconstructionsd.com.

Name Servers

cloudconstructionsd.com is served by two delegated name servers, ns05.domaincontrol.com and ns06.domaincontrol.com.

cloudconstructionsd.com uses the same name servers as several other domains — among them phoenix-criminal-defense.com, glendalechase.com, theejunglelook.com and two more.

Each of the two host names carries two IP addresses: ns05.domaincontrol.com points to 97.74.102.3 and 2603:5:2160::3, and ns06.domaincontrol.com points to 173.201.70.3 and 2603:5:2260::3.

Mail Servers

cloudconstructionsd.com has five mail servers, which are aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.

cloudconstructionsd.com has at least partial mail server overlap with other domains such as instalned.com, thevillageacupuncture.com.au, thecompassprojecttherapy.com and two more.

These mail servers commonly co-occur with mail servers alt1.aspmx.l.google.com, alt2.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.

Hostnames that resolve to two IP addresses:

aspmx2.googlemail.com maps to two IP addresses — 192.178.234.26 and 2800:3f0:4003:c14::1a.

aspmx3.googlemail.com maps to two IP addresses — 172.253.116.27 and 2a00:1450:400b:c02::1a.

aspmx.l.google.com maps to two IP addresses — 64.233.180.26 and 2607:f8b0:4004:c19::1a.

alt1.aspmx.l.google.com maps to two IP addresses — 192.178.234.26 and 2800:3f0:4003:c14::1a.

alt2.aspmx.l.google.com maps to two IP addresses — 172.253.116.27 and 2a00:1450:400b:c02::1a.

These two host names — aspmx2.googlemail.com and alt1.aspmx.l.google.com — each point to 2800:3f0:4003:c14::1a IP addresses.

These two host names — aspmx2.googlemail.com and alt1.aspmx.l.google.com — each point to 192.178.234.26 IP addresses.

These two host names — aspmx3.googlemail.com and alt2.aspmx.l.google.com — each point to 2a00:1450:400b:c02::1a IP addresses.

These two host names — aspmx3.googlemail.com and alt2.aspmx.l.google.com — each point to 172.253.116.27 IP addresses.