🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`spatialcomputing.co`

DNSSEC	⚠️ Not signed
A	44.232.173.249^{🇺🇸 Amazon44.224.0.0/11 EC2 PDX prefix}
		PTR	`ec2-44-232-173-249.us-west-2.compute.amazonaws.com`
A	52.40.42.113^{🇺🇸 Amazon52.40.0.0/14 EC2 PDX prefix}
NS	`launch1.spaceship.net` ⭐
		A	2400:cb00:2049:1::a29f:1a26^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.26.38^{Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`launch2.spaceship.net`
		A	2400:cb00:2049:1::a29f:1b20^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.27.32^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
SOA	`launch1.spaceship.net`support@spaceship.com serial=1788683646

`co`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns0.centralnic.net` ⭐
	NS	`a.registrydns.co`
	NS	`b.registrydns.co`
	NS	`c.registrydns.co`
	NS	`d.registrydns.co`
	SOA	`ns0.centralnic.net`hostmaster@centralnic.net serial=1759751458

Same first word

Previous names

Next names

DNS History

8 records (4 active, 4 former)

●NSlaunch1.spaceship.net2026-09-06 → 2026-09-06 · 3 obs

○ 2026-08-31 11:20:08
● 2026-09-06 15:22:28
● 2026-09-06 15:22:32

●NSlaunch2.spaceship.net2026-09-06 → 2026-09-06 · 3 obs

○ 2026-08-31 11:20:08
● 2026-09-06 15:22:28
● 2026-09-06 15:22:32

○NSns1.afternic.com2026-08-31 → 2026-08-31 · 3 obs

● 2026-08-31 11:20:08
○ 2026-09-06 15:22:28
○ 2026-09-06 15:22:32

○NSns2.afternic.com2026-08-31 → 2026-08-31 · 3 obs

● 2026-08-31 11:20:08
○ 2026-09-06 15:22:28
○ 2026-09-06 15:22:32

○A13.248.169.482026-08-31 → 2026-08-31 · 3 obs

● 2026-08-31 11:20:08
○ 2026-09-06 15:22:28
○ 2026-09-06 15:22:32

●A44.232.173.2492026-09-06 → 2026-09-06 · 3 obs

○ 2026-08-31 11:20:08
● 2026-09-06 15:22:28
● 2026-09-06 15:22:32

●A52.40.42.1132026-09-06 → 2026-09-06 · 3 obs

○ 2026-08-31 11:20:08
● 2026-09-06 15:22:28
● 2026-09-06 15:22:32

○A76.223.54.1462026-08-31 → 2026-08-31 · 3 obs

● 2026-08-31 11:20:08
○ 2026-09-06 15:22:28
○ 2026-09-06 15:22:32

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
co	a.registrydns.co, b.registrydns.co, c.registrydns.co, d.registrydns.co	-
spatialcomputing.co	launch1.spaceship.net, launch2.spaceship.net	-

✅ Authoritative Response

Server:162.159.27.32

NS records: launch1.spaceship.net, launch2.spaceship.net

🔒 DNSSEC Status

🔐 Secure (DNSSEC validated)

Chain of trust verified from root to domain

⏱️ Timing

Total: 880ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`52.40.42.113, 44.232.173.249`
NS	2	`launch2.spaceship.net, launch1.spaceship.net`
SOA	1	`launch1.spaceship.net support.spaceship.`

Analysis

IP Addresses

spatialcomputing.co points to the IP addresses 44.232.173.249 and 52.40.42.113

betswork.xyz, firdaus.ai, bl.com.es and two other host names share IP numbers with spatialcomputing.co.

Name Servers

spatialcomputing.co uses two name servers for its delegation: launch1.spaceship.net and launch2.spaceship.net.

spatialcomputing.co uses the same name servers as several other domains — among them superintelligencebank.com, geekmill.org, friesnation.com and two more.

Some name servers delegated to spatialcomputing.co are also used by other domains, notably postingpilot.com and textbookexchangenetwork.com.

The two host names launch1.spaceship.net and launch2.spaceship.net each have a pair of IP addresses: launch1.spaceship.net has 162.159.26.38 and 2400:cb00:2049:1::a29f:1a26, and launch2.spaceship.net has 162.159.27.32 and 2400:cb00:2049:1::a29f:1b20.

spatialcomputing.co - robtex.com