`transparentchannel.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=1778614396

WOT: UNKNOWN (50/100)

PTR for

13.163.10.204.in-addr.arpa

Same first word

transparentchannel.com

DNS History

10 records (2 active, 8 former)

○NSdns1.p11.nsone.net2026-04-22 → 2026-04-22 · 3 obs

● 2026-04-22 13:30:10
○ 2026-05-06 12:27:24
○ 2026-05-12 19:48:20

○NSdns2.p19.nsone.net2026-04-22 → 2026-04-22 · 3 obs

● 2026-04-22 13:30:10
○ 2026-05-06 12:27:24
○ 2026-05-12 19:48:20

○NSdns3.p09.nsone.net2026-04-22 → 2026-04-22 · 3 obs

● 2026-04-22 13:30:10
○ 2026-05-06 12:27:24
○ 2026-05-12 19:48:20

○NSdns4.p12.nsone.net2026-04-22 → 2026-04-22 · 3 obs

● 2026-04-22 13:30:10
○ 2026-05-06 12:27:24
○ 2026-05-12 19:48:20

●NSns-cloud-a1.googledomains.com2026-05-06 → 2026-05-12 · 3 obs

○ 2026-04-22 13:30:10
● 2026-05-06 12:27:24
● 2026-05-12 19:48:20

●NSns-cloud-a2.googledomains.com2026-05-06 → 2026-05-12 · 3 obs

○ 2026-04-22 13:30:10
● 2026-05-06 12:27:24
● 2026-05-12 19:48:20

○NSns1.transparentchannel.com2026-04-22 → 2026-04-22 · 3 obs

● 2026-04-22 13:30:10
○ 2026-05-06 12:27:24
○ 2026-05-12 19:48:20

○NSns2.transparentchannel.com2026-04-22 → 2026-04-22 · 3 obs

● 2026-04-22 13:30:10
○ 2026-05-06 12:27:24
○ 2026-05-12 19:48:20

○MXcontact.transparentchannel.com2026-04-22 → 2026-04-22 · 3 obs

● 2026-04-22 13:30:10
○ 2026-05-06 12:27:24
○ 2026-05-12 19:48:20

○A5.135.78.942026-04-22 → 2026-04-22 · 3 obs

● 2026-04-22 13:30:10
○ 2026-05-06 12:27:24
○ 2026-05-12 19:48:20

🔍 DNS Trace

📋 Delegation Chain

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

✅ Authoritative Response

Server:216.239.32.106

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for transparentchannel.com (unsigned zone)

⏱️ Timing

Total: 343ms | 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

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

transparentchannel.com shares the same name server setup as other domains, for example youkaystore.shop, usagroup.info, studweldingsource.com, claudiovideo.com and nexttighten.net.

transparentchannel.com at least partially shares name servers with other domains, for instance eauclairepartners.com, manybeds.com, helpwild.com, flowconstant.com and widgets.dtiserv2.com.

These name servers are often used with ns-cloud-a3.googledomains.com and ns-cloud-a4.googledomains.com.

Host names with two IP numbers:

ns-cloud-a1.googledomains.com points to 2001:4860:4802:32::6a and 216.239.32.106

ns-cloud-a2.googledomains.com points to 2001:4860:4802:34::6a and 216.239.34.106

transparentchannel.com - robtex.com