`telegram-connect.org`

DNSSEC	⚠️ Not signed
NS	`ns1.bluehost.com` ⭐
		A	162.159.24.80^{Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.bluehost.com`
NS	`ns2.bluehost.com`
		A	162.159.25.175^{Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.bluehost.com`
SOA	`ns1.bluehost.com`root@box5526.bluehost.com 2024-11-07 #27

`org`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a0.org.afilias-nst.info` ⭐ ⚠️ Not in parent delegation
	NS	`a2.org.afilias-nst.info` ⚠️ Not in parent delegation
	NS	`b0.org.afilias-nst.org`
	NS	`b2.org.afilias-nst.org`
	NS	`c0.org.afilias-nst.info` ⚠️ Not in parent delegation
	NS	`d0.org.afilias-nst.org`
	SOA	`a0.org.afilias-nst.info`hostmaster@donuts.email serial=1774642367

⚠️ On DNS blocklist: tif

telegram-connect.org

2 records (2 active, 0 former)

●NSns1.bluehost.com2026-03-05 → 2026-03-27 · 2 obs

● 2026-03-05 13:19:02
● 2026-03-27 20:24:44

●NSns2.bluehost.com2026-03-05 → 2026-03-27 · 2 obs

● 2026-03-05 13:19:02
● 2026-03-27 20:24:44

Zone	Nameservers	Glue
org	b0.org.afilias-nst.org, b2.org.afilias-nst.org, d0.org.afilias-nst.org	-
telegram-connect.org	ns2.bluehost.com, ns1.bluehost.com	-

Server:162.159.25.175

NS records: ns2.bluehost.com, ns1.bluehost.com

⚠️ Insecure (no DNSSEC)

No DS record for telegram-connect.org (unsigned zone)

Total: 606ms | Queries: -

Type	Count	Sample Data
NS	2	`ns2.bluehost.com, ns1.bluehost.com`
SOA	1	`ns1.bluehost.com root.box5526.bluehost.c`

telegram-connect.org is delegated to two name servers: ns1.bluehost.com and ns2.bluehost.com.

telegram-connect.org uses the same name server setup as other domains such as whatthevetsaid.com, kcarnold.net, fnu.ebl.mybluehost.me, fixmyvape.com and ranchogallina.com.

telegram-connect.org shares name servers with other domains at least partially, for example qysmt.com.

Host names with one IP number: