`ingeniousstg.build`

DNSSEC	⚠️ Not signed
NS	`ns-cloud-c1.googledomains.com` ⭐
		A	2001:4860:4802:32::6c^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-c1.googledomains.com`
		A	216.239.32.108^{🇺🇸 Google216.239.32.0/24}
			PTR	`ns-cloud-c1.googledomains.com`
NS	`ns-cloud-c2.googledomains.com`
		A	2001:4860:4802:34::6c^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-c2.googledomains.com`
		A	216.239.34.108^{🇺🇸 Google216.239.34.0/24}
			PTR	`ns-cloud-c2.googledomains.com`
NS	`ns-cloud-c3.googledomains.com`
		A	2001:4860:4802:36::6c^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-c3.googledomains.com`
		A	216.239.36.108^{🇺🇸 Google216.239.36.0/24}
			PTR	`ns-cloud-c3.googledomains.com`
NS	`ns-cloud-c4.googledomains.com`
		A	2001:4860:4802:38::6c^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-c4.googledomains.com`
		A	216.239.38.108^{🇺🇸 Google216.239.38.0/24}
			PTR	`ns-cloud-c4.googledomains.com`
TXT	`jm57s4sv068tdgugb8o9fbcjna`
SOA	`ns-cloud-c1.googledomains.com`cloud-dns-hostmaster@google.com serial=1

`build`

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

Same first word

ingeniousstg.build

DNS History

4 records (4 active, 0 former)

●NSns-cloud-c1.googledomains.com2026-04-29 → 2026-05-09 · 2 obs

● 2026-04-29 10:59:12
● 2026-05-09 18:23:30

●NSns-cloud-c2.googledomains.com2026-04-29 → 2026-05-09 · 2 obs

● 2026-04-29 10:59:12
● 2026-05-09 18:23:30

●NSns-cloud-c3.googledomains.com2026-04-29 → 2026-05-09 · 2 obs

● 2026-04-29 10:59:12
● 2026-05-09 18:23:30

●NSns-cloud-c4.googledomains.com2026-04-29 → 2026-05-09 · 2 obs

● 2026-04-29 10:59:12
● 2026-05-09 18:23:30

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
build	a.nic.build, b.nic.build, c.nic.build, d.nic.build	8 records
ingeniousstg.build	ns-cloud-c3.googledomains.com, ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c4.googledomains.com	-

✅ Authoritative Response

Server:216.239.36.108

NS records: ns-cloud-c3.googledomains.com, ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c4.googledomains.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for ingeniousstg.build (unsigned zone)

⏱️ Timing

Total: 3652ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns-cloud-c2.googledomains.com, ns-cloud-c1.googledomains.com...`
TXT	1	`jm57s4sv068tdgugb8o9fbcjna`
SOA	1	`ns-cloud-c1.googledomains.com cloud-dns-`

📌 Glue Records Collected

Total: 8

In-bailiwick: 8 (a.nic.build, b.nic.build, c.nic.build...)

Analysis

Name Servers

ingeniousstg.build delegates to four name servers: ns-cloud-c1.googledomains.com, ns-cloud-c2.googledomains.com, ns-cloud-c3.googledomains.com and ns-cloud-c4.googledomains.com.

ingeniousstg.build at least partially shares name servers with other domains, including cpgateway.com, us1.weavephone.net, portfoliomanagementsystems.com, ichode.com and mutiarakristal.com.

These name servers are often used with ns1.mirusresearch.com and ns2.mir.us.

Host names with two IP numbers: ns-cloud-c1.googledomains.com points to 2001:4860:4802:32::6c and 216.239.32.108; ns-cloud-c2.googledomains.com points to 2001:4860:4802:34::6c and 216.239.34.108; ns-cloud-c3.googledomains.com points to 2001:4860:4802:36::6c and 216.239.36.108; ns-cloud-c4.googledomains.com points to 2001:4860:4802:38::6c and 216.239.38.108.

ingeniousstg.build - robtex.com