spatialflow.in - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`spatialflow.in`

DNSSEC	🔒 Signed (DS record present)
A	216.198.79.1^{Amazon216.198.79.0/24 EC2 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}
MX	`smtp.google.com` ⭐
		A	2a00:1450:4013:c16::1a^{🇳🇱 Google2a00:1450:4013::/48}
			PTR	`ea-in-f26.1e100.net`
		A	2a00:1450:4013:c20::1a^{🇳🇱 Google2a00:1450:4013::/48}
			PTR	`yugrqvu-in-f26.1e100.net`
		A	2a00:1450:4013:c22::1a^{🇳🇱 Google2a00:1450:4013::/48}
			PTR	`yugrqfv-in-f26.1e100.net`
		A	2a00:1450:4013:c22::1b^{🇳🇱 Google2a00:1450:4013::/48}
			PTR	`yugrqfv-in-f27.1e100.net`
		A	108.177.127.26^{🇺🇸 Google108.177.127.0/24}
			PTR	`el-in-f26.1e100.net`
		A	108.177.127.27^{🇺🇸 Google108.177.127.0/24}
			PTR	`el-in-f27.1e100.net`
		A	142.251.31.27^{🇺🇸 Google142.251.31.0/24}
			PTR	`eq-in-f27.1e100.net`
		A	172.217.218.26^{🇺🇸 Google172.217.218.0/24}
			PTR	`en-in-f26.1e100.net`
		A	172.217.218.27^{🇺🇸 Google172.217.218.0/24}
			PTR	`en-in-f27.1e100.net`
TXT	`google-site-verification=z-2bFSatkZqSMsNJwDs_7xlubv43y05Ot4xZFa82Ipk`
SOA	`launch1.spaceship.net`support@spaceship.com serial=1782240235

`in`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns.trs-dns.com` ⭐
	NS	`ns1.registry.in`
	NS	`ns2.registry.in`
	NS	`ns3.registry.in`
	NS	`ns4.registry.in`
	SOA	`ns.trs-dns.com`trs-ops@tucows.com serial=1794205854

Same first word

spatialflow.app

spatialflow.net

spatialflow.ai

spatialflow.in

spatialflow.io

spatialflow.com

spatialflow.co

Similar names

spatialwolf.com

flowspatial.xyz

lapistolafw.com

tailflopaws.co.uk

spatialwolf.xyz

flowspatial.com

DNS History

4 records (4 active, 0 former)

●NSlaunch1.spaceship.net2026-09-04 → 2026-11-09 · 2 obs

● 2026-09-04 12:34:04
● 2026-11-09 07:16:50

●NSlaunch2.spaceship.net2026-09-04 → 2026-11-09 · 2 obs

● 2026-09-04 12:34:04
● 2026-11-09 07:16:50

●MXsmtp.google.com2026-09-04 → 2026-11-09 · 2 obs

● 2026-09-04 12:34:04
● 2026-11-09 07:16:50

●A216.198.79.12026-09-04 → 2026-11-09 · 2 obs

● 2026-09-04 12:34:04
● 2026-11-09 07:16:50

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
in	ns1.registry.in, ns2.registry.in, ns3.registry.in, ns4.registry.in	8 records
spatialflow.in	launch1.spaceship.net, launch2.spaceship.net	-

✅ Authoritative Response

Server:162.159.27.32

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

🔒 DNSSEC Status

❌ Bogus (DNSSEC validation failed)

No DNSKEY for spatialflow.in

⏱️ Timing

Total: 4179ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`launch1.spaceship.net, launch2.spaceship.net`
MX	1	`smtp.google.com (pri: 1)`

📌 Glue Records Collected

Total: 8

In-bailiwick: 8 (ns1.registry.in, ns2.registry.in, ns3.registry.in...)

Analysis

IP Addresses

spatialflow.in points to one IP number: 216.198.79.1.

Name Servers

DNS delegation for spatialflow.in points to two name servers: launch1.spaceship.net and launch2.spaceship.net.

launch1.spaceship.net directs to 162.159.26.38 and 2400:cb00:2049:1::a29f:1a26. launch2.spaceship.net directs to 162.159.27.32 and 2400:cb00:2049:1::a29f:1b20. Each host name carries two IP addresses.

Mail Servers

spatialflow.in routes its mail through a single mail server, smtp.google.com.

smtp.google.com directs to 9 IP numbers, including 108.177.127.26, 108.177.127.27 and 142.251.31.27, along with 6 other.