trivalleycomputer.com - dns.ninja

`trivalleycomputer.com`

DNSSEC	⚠️ Not signed
NS	`ns-cloud-a1.googledomains.com` ⚠️ Not in zone NS records
		A	2001:4860:4802:32::6a^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-a1.googledomains.com`
		A	216.239.32.106^{🇺🇸 Google216.239.32.0/24}
			PTR	`ns-cloud-a1.googledomains.com`
NS	`ns-cloud-a2.googledomains.com` ⚠️ Not in zone NS records
		A	2001:4860:4802:34::6a^{🇺🇸 Google2001:4860::/32}
			PTR	`ns-cloud-a2.googledomains.com`
		A	216.239.34.106^{🇺🇸 Google216.239.34.0/24}
			PTR	`ns-cloud-a2.googledomains.com`

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

Same first word

trivalleycomputer.com

DNS History

22 records (2 active, 20 former)

●NSns-cloud-a1.googledomains.com2026-02-17 → 2026-06-29 · 3 obs

○ 2019-04-07 19:45:32
● 2026-02-17 19:08:44
● 2026-06-29 20:31:24

●NSns-cloud-a2.googledomains.com2026-02-17 → 2026-06-29 · 3 obs

○ 2019-04-07 19:45:32
● 2026-02-17 19:08:44
● 2026-06-29 20:31:24

○NSns.buydomains.com2008-03-17 → 2008-03-17 · 3 obs

● 2008-03-17 19:54:30
○ 2015-08-03 09:39:48
○ 2026-06-29 20:31:24

○NSns1.namebrightdns.com2015-08-03 → 2017-02-17 · 8 obs

○ 2008-03-17 19:54:30
● 2015-08-03 09:39:48
○ 2015-11-18 11:29:40
○ 2016-03-03 06:15:26
● 2016-06-19 20:03:38
● 2017-02-17 03:26:48
○ 2019-04-07 19:45:32
○ 2026-06-29 20:31:24

○NSns2.namebrightdns.com2015-08-03 → 2017-02-17 · 8 obs

○ 2008-03-17 19:54:30
● 2015-08-03 09:39:48
○ 2015-11-18 11:29:40
○ 2016-03-03 06:15:26
● 2016-06-19 20:03:38
● 2017-02-17 03:26:48
○ 2019-04-07 19:45:32
○ 2026-06-29 20:31:24

○NSnsg1.namebrightdns.com2015-11-18 → 2019-04-07 · 8 obs

○ 2015-08-03 09:39:48
● 2015-11-18 11:29:40
● 2016-03-03 06:15:26
○ 2016-06-19 20:03:38
○ 2017-02-17 03:26:48
● 2019-04-07 19:45:32
○ 2026-02-17 19:08:44
○ 2026-06-29 20:31:24

○NSnsg2.namebrightdns.com2015-11-18 → 2019-04-07 · 8 obs

○ 2015-08-03 09:39:48
● 2015-11-18 11:29:40
● 2016-03-03 06:15:26
○ 2016-06-19 20:03:38
○ 2017-02-17 03:26:48
● 2019-04-07 19:45:32
○ 2026-02-17 19:08:44
○ 2026-06-29 20:31:24

○NSthis-domain-for-sale.com2008-03-17 → 2008-03-17 · 3 obs

● 2008-03-17 19:54:30
○ 2015-08-03 09:39:48
○ 2026-06-29 20:31:24

○MXanmail.namebrightmail.com2015-08-03 → 2015-08-03 · 4 obs

○ 2008-03-17 19:54:30
● 2015-08-03 09:39:48
○ 2015-11-18 11:29:40
○ 2026-06-29 20:31:24

○MXdev.null2008-03-17 → 2008-03-17 · 3 obs

● 2008-03-17 19:54:30
○ 2015-08-03 09:39:48
○ 2026-06-29 20:31:24

○A208.254.26.1322008-03-17 → 2008-03-17 · 3 obs

● 2008-03-17 19:54:30
○ 2015-08-03 09:39:48
○ 2026-06-29 20:31:24

○A34.199.151.1632017-02-17 → 2017-02-17 · 4 obs

○ 2016-06-19 20:03:38
● 2017-02-17 03:26:48
○ 2019-04-07 19:45:32
○ 2026-06-29 20:31:24

○A52.0.96.242016-03-03 → 2016-03-03 · 4 obs

○ 2015-11-18 11:29:40
● 2016-03-03 06:15:26
○ 2016-06-19 20:03:38
○ 2026-06-29 20:31:24

○A52.20.154.32017-02-17 → 2017-02-17 · 4 obs

○ 2016-06-19 20:03:38
● 2017-02-17 03:26:48
○ 2019-04-07 19:45:32
○ 2026-06-29 20:31:24

○A52.200.243.1232016-06-19 → 2016-06-19 · 4 obs

○ 2016-03-03 06:15:26
● 2016-06-19 20:03:38
○ 2017-02-17 03:26:48
○ 2026-06-29 20:31:24

○A52.71.117.992016-03-03 → 2016-03-03 · 4 obs

○ 2015-11-18 11:29:40
● 2016-03-03 06:15:26
○ 2016-06-19 20:03:38
○ 2026-06-29 20:31:24

○A54.152.144.2432016-06-19 → 2016-06-19 · 4 obs

○ 2016-03-03 06:15:26
● 2016-06-19 20:03:38
○ 2017-02-17 03:26:48
○ 2026-06-29 20:31:24

○A54.174.31.2542015-08-03 → 2015-11-18 · 5 obs

○ 2008-03-17 19:54:30
● 2015-08-03 09:39:48
● 2015-11-18 11:29:40
○ 2016-03-03 06:15:26
○ 2026-06-29 20:31:24

○A54.208.74.2152015-08-03 → 2015-11-18 · 5 obs

○ 2008-03-17 19:54:30
● 2015-08-03 09:39:48
● 2015-11-18 11:29:40
○ 2016-03-03 06:15:26
○ 2026-06-29 20:31:24

○CNAMEhdredirect-lb-399551664.us-east-1.elb.amazonaws.com2015-08-03 → 2016-06-19 · 5 obs

○ 2008-03-17 19:54:30
● 2015-08-03 09:39:48
● 2016-06-19 20:03:38
○ 2017-02-17 03:26:48
○ 2026-06-29 20:31:24

○CNAMEhdredirect-lb3-890977680.us-east-1.elb.amazonaws.com2017-02-17 → 2017-02-17 · 4 obs

○ 2016-06-19 20:03:38
● 2017-02-17 03:26:48
○ 2019-04-07 19:45:32
○ 2026-06-29 20:31:24

○CNAMEhdredirect-lb5-1afb6e2973825a56.elb.us-east-1.amazonaws.com2019-04-07 → 2019-04-07 · 4 obs

○ 2017-02-17 03:26:48
● 2019-04-07 19:45:32
○ 2026-02-17 19:08:44
○ 2026-06-29 20:31:24

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
trivalleycomputer.com	ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com	4 records

✅ Authoritative Response

Server:216.239.34.106

NS records: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for trivalleycomputer.com (unsigned zone)

⏱️ Timing

Total: 284ms | Queries: -

📄 Records

Type	Count	Sample Data

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns-cloud-a1.googledomains.com, ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com...)

Analysis

Name Servers

trivalleycomputer.com is delegated to two name servers: ns-cloud-a1.googledomains.com and ns-cloud-a2.googledomains.com.

trivalleycomputer.com shares its NS records with other domains, for example oldlouisville.net, soldfor.us, mulfhunter.com and two others.

trivalleycomputer.com partially shares its NS delegation with several other domains, including lauradrumgoole.com, steepexp.com, xumaq.com and two others.

These name servers are regularly seen alongside ns-cloud-a3.googledomains.com and ns-cloud-a4.googledomains.com as name servers.

ns-cloud-a1.googledomains.com and ns-cloud-a2.googledomains.com each resolve to two IP addresses: ns-cloud-a1.googledomains.com points to 216.239.32.106 and 2001:4860:4802:32::6a, while ns-cloud-a2.googledomains.com points to 216.239.34.106 and 2001:4860:4802:34::6a.