🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`couldcloud.com`

DNSSEC	⚠️ Not signed
A	2600:1f18:4ae:c605:dd5d:b838:5816:d7fb^{🇺🇸 Amazon2600:1f18::/35 AMAZON EC2 IAD prefix}
A	2600:1f18:4ae:c606:78d4:4260:db4e:aeee^{🇺🇸 Amazon2600:1f18::/35 AMAZON EC2 IAD prefix}
A	13.223.25.84^{🇺🇸 Amazon13.216.0.0/13 EC2 IAD prefix}
A	54.243.117.197^{🇺🇸 Amazon54.242.0.0/15 EC2 IAD prefix}
NS	`ns1.namebrightdns.com` ⭐
		A	34.229.15.31^{🇺🇸 Amazon34.224.0.0/12 EC2 Region prefix}
			PTR	`ec2-34-229-15-31.compute-1.amazonaws.com`
		A	54.87.15.152^{🇺🇸 Amazon54.87.0.0/16 EC2 IAD prefix}
			PTR	`ec2-54-87-15-152.compute-1.amazonaws.com`
NS	`nsg1.namebrightdns.com`
		A	2600:1f18:683a:ae1a:b7f8:9db8:e2c0:ea4d^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:683a:ae1b:3678:5912:58b4:f1bb^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:683a:ae1b:972d:ba8c:15bd:1fc4^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:683a:ae1b:c591:a60:8296:4c8d^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	13.221.70.139^{🇺🇸 Amazon13.216.0.0/13 EC2 IAD prefix}
			PTR	`ec2-13-221-70-139.compute-1.amazonaws.com`
		A	52.90.122.106^{🇺🇸 Amazon52.90.0.0/15 EC2 IAD prefix}
			PTR	`ec2-52-90-122-106.compute-1.amazonaws.com`
		A	54.91.117.97^{🇺🇸 Amazon54.90.0.0/15 EC2 IAD prefix}
			PTR	`ec2-54-91-117-97.compute-1.amazonaws.com`
		A	54.224.169.73^{🇺🇸 Amazon54.224.0.0/15 EC2 IAD prefix}
			PTR	`ec2-54-224-169-73.compute-1.amazonaws.com`
NS	`nsg2.namebrightdns.com`
		A	2600:1f18:683a:ae1a:4cc0:5acf:aad1:572a^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:683a:ae1a:bf98:4592:dea7:ef46^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	2600:1f18:683a:ae1b:44ba:1b15:cef8:e750^{🇺🇸 Amazon2600:1f18:6000::/35 AMAZON EC2 IAD prefix}
		A	3.81.217.152^{🇺🇸 Amazon3.80.0.0/12 EC2 IAD prefix}
			PTR	`ec2-3-81-217-152.compute-1.amazonaws.com`
		A	54.82.105.15^{🇺🇸 Amazon54.80.0.0/14 EC2 IAD prefix}
			PTR	`ec2-54-82-105-15.compute-1.amazonaws.com`
		A	54.209.221.205^{🇺🇸 Amazon54.208.0.0/15 EC2 IAD prefix}
			PTR	`ec2-54-209-221-205.compute-1.amazonaws.com`
TXT	`v=spf1 -all`
TXT	`afternic-verification-G9G3tM8T8EwEizzPzjGJWF`
SOA	`ns1.namebrightdns.com`dns@namebright.com 2026-10-06 #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=1791277874

Same first word

couldcloud.com

couldcloud.xyz

Similar names

Previous names

Next names

DNS History

8 records (7 active, 1 former)

●NSns1.namebrightdns.com2026-09-28 → 2026-10-06 · 2 obs

● 2026-09-28 19:34:28
● 2026-10-06 09:35:54

●NSnsg1.namebrightdns.com2026-09-28 → 2026-10-06 · 2 obs

● 2026-09-28 19:34:28
● 2026-10-06 09:35:54

●NSnsg2.namebrightdns.com2026-09-28 → 2026-10-06 · 2 obs

● 2026-09-28 19:34:28
● 2026-10-06 09:35:54

○A107.179.19.482017-12-31 → 2017-12-31 · 3 obs

● 2017-12-31 04:34:16
○ 2026-09-28 19:34:28
○ 2026-10-06 09:35:54

●A13.223.25.842026-09-28 → 2026-10-06 · 3 obs

○ 2017-12-31 04:34:16
● 2026-09-28 19:34:28
● 2026-10-06 09:35:54

●A2600:1f18:4ae:c605:dd5d:b838:5816:d7fb2026-09-28 → 2026-10-06 · 3 obs

○ 2017-12-31 04:34:16
● 2026-09-28 19:34:28
● 2026-10-06 09:35:54

●A2600:1f18:4ae:c606:78d4:4260:db4e:aeee2026-09-28 → 2026-10-06 · 3 obs

○ 2017-12-31 04:34:16
● 2026-09-28 19:34:28
● 2026-10-06 09:35:54

●A54.243.117.1972026-09-28 → 2026-10-06 · 3 obs

○ 2017-12-31 04:34:16
● 2026-09-28 19:34:28
● 2026-10-06 09:35:54

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	g.gtld-servers.net, h.gtld-servers.net, b.gtld-servers.net, j.gtld-servers.net...	-
couldcloud.com	nsg1.namebrightdns.com, nsg2.namebrightdns.com	14 records

✅ Authoritative Response

Server:13.221.70.139

NS records: nsg1.namebrightdns.com, nsg2.namebrightdns.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for couldcloud.com (unsigned zone)

⏱️ Timing

Total: 208ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`54.243.117.197, 13.223.25.84`
AAAA	2	`2600:1f18:4ae:c606:78d4:4260:db4e:aeee, 2600:1f18:4ae:c605:dd5d:b838:5816:d7fb`
NS	2	`nsg1.namebrightdns.com, nsg2.namebrightdns.com`
TXT	2	`afternic-verification-G9G3tM8T8EwEizzPzj, v=spf1 -all`
SOA	1	`ns1.namebrightdns.com dns.namebright.com`

📌 Glue Records Collected

Total: 14

Out-of-bailiwick: 14 (nsg1.namebrightdns.com, nsg1.namebrightdns.com, nsg1.namebrightdns.com...)

Analysis

IP Addresses

couldcloud.com has four IP addresses: 13.223.25.84, 54.243.117.197, 2600:1f18:4ae:c605:dd5d:b838:5816:d7fb and 2600:1f18:4ae:c606:78d4:4260:db4e:aeee.

hairltd.com, www.plexmail.com, olivestay.com plus two other host names have IP numbers in common with couldcloud.com.

Name Servers

couldcloud.com is served by three name servers: ns1.namebrightdns.com, nsg1.namebrightdns.com and nsg2.namebrightdns.com.

couldcloud.com shares at least some of its name servers with other domains, including alimile.com, biomedllc.com, recallcare.com and two others.

These name servers are frequently paired with the name servers ns2.namebrightdns.com, domain-for-sale.hugedomainsdns.com and forsale.hugedomainsdns.com.

Hosts with 8 IP addresses each:

nsg1.namebrightdns.com maps to 13.221.70.139, 52.90.122.106, 54.91.117.97 and 5 additional IP addresses.

Hosts with 6 IP addresses each:

nsg2.namebrightdns.com maps to 3.81.217.152, 54.82.105.15, 54.209.221.205 and 3 additional IP addresses.

Host names pointing to two IP addresses:

The A records for ns1.namebrightdns.com return 34.229.15.31 and 54.87.15.152.

couldcloud.com - robtex.com

couldcloud.com

com

Same first word

Similar names

Previous names

Next names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

IP Addresses

Name Servers

`couldcloud.com`

`com`