telegramwk.top - robtex.com
telegramwk.top
| DNSSEC | ⚠️ Not signed | ||||||
| A | 127.0.0.1 | ||||||
| NS | a9.share-dns.com ⭐ ⚠️ Not in parent delegation | ||||||
| A | 172.64.53.25🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | a.share-dns.com ⚠️ Not in zone NS records | ||||||
| A | 172.64.53.25🇺🇸 Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | b.share-dns.net ⚠️ Not in zone NS records | ||||||
| A | 172.64.52.239🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| NS | b9.share-dns.net ⚠️ Not in parent delegation | ||||||
| A | 172.64.52.239🇺🇸 Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US | ||||||
| SOA | a.share-dns.commaster@share-dns.com serial=1758641261 | ||||||
top
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.zdnscloud.com ⭐ | ||||||
| NS | a.zdnscloud.cn | ||||||
| NS | b.zdnscloud.cn | ||||||
| NS | c.zdnscloud.com | ||||||
| NS | d.zdnscloud.com | ||||||
| NS | e.zdnscloud.cn | ||||||
| NS | f.zdnscloud.cn | ||||||
| NS | i.zdnscloud.cn | ||||||
| NS | j.zdnscloud.com | ||||||
| TXT | 2026-04-26_10:20:02 | ||||||
| SOA | a.zdnscloud.comtd_dns_gtld@knet.cn serial=1395643324 | ||||||
Same first word
telegramwk.top |
DNS History
5 records (5 active, 0 former)
●NSa.share-dns.com2026-03-16 → 2026-04-26 · 2 obs
● 2026-04-26 02:44:10
●NSa9.share-dns.com2026-03-16 → 2026-04-26 · 2 obs
● 2026-04-26 02:44:10
●NSb.share-dns.net2026-03-16 → 2026-04-26 · 2 obs
● 2026-04-26 02:44:10
●NSb9.share-dns.net2026-03-16 → 2026-04-26 · 2 obs
● 2026-04-26 02:44:10
●A127.0.0.12026-03-16 → 2026-04-26 · 2 obs
● 2026-04-26 02:44:10
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| top | d.zdnscloud.com, e.zdnscloud.cn, a.zdnscloud.cn, i.zdnscloud.cn... | 9 records |
| telegramwk.top | a9.share-dns.com, b9.share-dns.net | - |
✅ Authoritative Response
Server:172.64.53.25
NS records: a9.share-dns.com, b9.share-dns.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for telegramwk.top (unsigned zone)
⏱️ Timing
Total: 1251ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 127.0.0.1 |
| NS | 2 | a.share-dns.com, b.share-dns.net |
| SOA | 1 | a.share-dns.com master.share-dns.com |
📌 Glue Records Collected
Total: 9
Out-of-bailiwick: 9 (f.zdnscloud.cn, e.zdnscloud.cn, d.zdnscloud.com...)
Analysis
IP Addresses
telegramwk.top points to a single IP: 127.0.0.1.
Other host names, for instance 161.170.4.static.quadranet.com, rav4sucks.com, mail.g3-software.de, download5m.akamaized.net and localhost.safesearch.com share IP numbers with telegramwk.top.
Name Servers
telegramwk.top's delegation is handled by four name servers: a9.share-dns.com, a.share-dns.com, b9.share-dns.net and b.share-dns.net.
telegramwk.top partially shares name servers with other domains; examples include 36222.org, cc1r.com, youneedhostel.com, tj-xinda.com and dubaipolijke.com.
These name servers are commonly used alongside a12.share-dns.com, b12.share-dns.net, a3.share-dns.com, b3.share-dns.net, a4.share-dns.com, b4.share-dns.net, a1.share-dns.com, b1.share-dns.net, a5.share-dns.com and b5.share-dns.net.
Host names sharing a single IP address:
a9.share-dns.com points to: 172.64.53.25.
a.share-dns.com points to: 172.64.53.25.
b9.share-dns.net points to: 172.64.52.239.
b.share-dns.net points to: 172.64.52.239.
Host names pointing to 172.64.53.25: a9.share-dns.com and a.share-dns.com.
Host names pointing to 172.64.52.239: b9.share-dns.net and b.share-dns.net.