`telegram-join134.rest`

DNSSEC	⚠️ Not signed
A	216.120.147.200
NS	`ns100.webnic.cc` ⭐
		A	54.177.52.27^{🇺🇸 Amazon54.176.0.0/15 EC2 SFO prefix}
			PTR	`ec2-54-177-52-27.us-west-1.compute.amazonaws.com`
NS	`ns101.webnic.cc`
		A	54.177.52.27^{🇺🇸 Amazon54.176.0.0/15 EC2 SFO prefix}
			PTR	`ec2-54-177-52-27.us-west-1.compute.amazonaws.com`
SOA	`ns100.webnic.cc`technical@webnic.cc 2025-08-05 #1

`rest`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns01.trs-dns.com` ⭐
	NS	`ns.trs-dns.com`
	NS	`ns01.trs-dns.net`
	NS	`ns10.trs-dns.info`
	NS	`ns10.trs-dns.org`
	SOA	`ns.trs-dns.com`trs-ops@tucows.com serial=1778586952

⚠️ On DNS blocklist: tif

Same first word

telegram-join134.rest

DNS History

7 records (3 active, 4 former)

○NSalexa.ns.cloudflare.com2026-03-31 → 2026-04-11 · 4 obs

● 2026-03-31 07:24:06
● 2026-04-11 03:07:16
○ 2026-05-09 02:48:02
○ 2026-05-12 12:04:50

○NScarmelo.ns.cloudflare.com2026-03-31 → 2026-04-11 · 4 obs

● 2026-03-31 07:24:06
● 2026-04-11 03:07:16
○ 2026-05-09 02:48:02
○ 2026-05-12 12:04:50

●NSns100.webnic.cc2026-05-09 → 2026-05-12 · 3 obs

○ 2026-04-11 03:07:16
● 2026-05-09 02:48:02
● 2026-05-12 12:04:50

●NSns101.webnic.cc2026-05-09 → 2026-05-12 · 3 obs

○ 2026-04-11 03:07:16
● 2026-05-09 02:48:02
● 2026-05-12 12:04:50

○A104.21.29.1572026-03-31 → 2026-04-11 · 4 obs

● 2026-03-31 07:24:06
● 2026-04-11 03:07:16
○ 2026-05-09 02:48:02
○ 2026-05-12 12:04:50

○A172.67.149.1112026-03-31 → 2026-04-11 · 4 obs

● 2026-03-31 07:24:06
● 2026-04-11 03:07:16
○ 2026-05-09 02:48:02
○ 2026-05-12 12:04:50

●A216.120.147.2002026-05-09 → 2026-05-12 · 3 obs

○ 2026-04-11 03:07:16
● 2026-05-09 02:48:02
● 2026-05-12 12:04:50

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
rest	ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info	8 records
telegram-join134.rest	ns101.webnic.cc, ns100.webnic.cc	-

✅ Authoritative Response

Server:54.177.52.27

NS records: ns101.webnic.cc, ns100.webnic.cc

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for telegram-join134.rest (unsigned zone)

⏱️ Timing

Total: 668ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`216.120.147.200`
NS	2	`ns100.webnic.cc, ns101.webnic.cc`
SOA	1	`ns100.webnic.cc technical.webnic.cc`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns10.trs-dns.info, ns10.trs-dns.org, ns01.trs-dns.net...)

Analysis

IP Addresses

telegram-join134.rest resolves to one IP number: 216.120.147.200.

other host names including supremeservice.top, mail.mystar-msc.com, www.762ead7259f49767e99492785d8c175b.top, webmail.smoothstar.net and kuoan.com share IP numbers with telegram-join134.rest.

Name Servers

telegram-join134.rest is delegated to two name servers ns100.webnic.cc and ns101.webnic.cc.

telegram-join134.rest shares the same name server setup as other domains, for instance complaintsguest64123.com, rigafarm.com, krajoweprzesylki.shop, apps-pc-windows.com and aviatormoney.sbs.

Host names with a single IP:

ns100.webnic.cc points to 54.177.52.27.

ns101.webnic.cc points to 54.177.52.27.

Host names pointing to 54.177.52.27: ns100.webnic.cc and ns101.webnic.cc.

telegram-join134.rest - robtex.com