telegramsf.top - robtex.com
telegramsf.top
| DNSSEC | ⚠️ Not signed | ||||||
| A | 127.0.0.1 | ||||||
| NS | a3.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 | ||||||
| PTR | ip-172-64-53-25.defastlink.net | ||||||
| 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 | ||||||
| PTR | ip-172-64-53-25.defastlink.net | ||||||
| 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 | ||||||
| PTR | ip-172-64-52-239.defastlink.net | ||||||
| NS | b3.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 | ||||||
| PTR | ip-172-64-52-239.defastlink.net | ||||||
| SOA | a.share-dns.commaster@share-dns.com serial=1758641260 | ||||||
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 | f.zdnscloud.cn | ||||||
| NS | g.zdnscloud.com | ||||||
| NS | i.zdnscloud.cn | ||||||
| NS | j.zdnscloud.com | ||||||
| TXT | 2026-03-15_12:30:03 | ||||||
| SOA | a.zdnscloud.comtd_dns_gtld@knet.cn serial=1395268745 | ||||||
Same first word
telegramsf.top |
Similar names
DNS History
5 records (5 active, 0 former)
●NSa.share-dns.com2026-03-08 → 2026-03-23 · 2 obs
● 2026-03-23 23:31:32
●NSa3.share-dns.com2026-03-08 → 2026-03-23 · 2 obs
● 2026-03-23 23:31:32
●NSb.share-dns.net2026-03-08 → 2026-03-23 · 2 obs
● 2026-03-23 23:31:32
●NSb3.share-dns.net2026-03-08 → 2026-03-23 · 2 obs
● 2026-03-23 23:31:32
●A127.0.0.12026-03-08 → 2026-03-23 · 2 obs
● 2026-03-23 23:31:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| top | g.zdnscloud.com, b.zdnscloud.cn, d.zdnscloud.com, i.zdnscloud.cn... | 8 records |
| telegramsf.top | a3.share-dns.com, b3.share-dns.net | - |
✅ Authoritative Response
Server:172.64.53.25
NS records: a3.share-dns.com, b3.share-dns.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for telegramsf.top (unsigned zone)
⏱️ Timing
Total: 948ms | 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: 8
Out-of-bailiwick: 8 (g.zdnscloud.com, f.zdnscloud.cn, d.zdnscloud.com...)
Analysis
IP Addresses
telegramsf.top points to a single IP: 127.0.0.1.
Other host names, for instance mobile-server.de, 115.203.static.quadranet.com, mail.nsn.fr, 10.171.97.66.in-addr.arpa and www.sababy.com share IP numbers with telegramsf.top.
Name Servers
telegramsf.top's delegation is handled by four name servers: a3.share-dns.com, a.share-dns.com, b3.share-dns.net and b.share-dns.net.
telegramsf.top partially shares name servers with other domains; examples include ylpcz.com, henanjlz.com, yanhlsm.com, diennuocnhanh247.com and atwckky.vip.
These name servers are commonly used alongside a6.share-dns.com, b6.share-dns.net, a10.share-dns.com, b10.share-dns.net, a9.share-dns.com, b9.share-dns.net, a7.share-dns.com, b7.share-dns.net, a2.share-dns.com and b2.share-dns.net.
Host names sharing a single IP address:
a3.share-dns.com points to: 172.64.53.25.
a.share-dns.com points to: 172.64.53.25.
b3.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: a3.share-dns.com and a.share-dns.com.
Host names pointing to 172.64.52.239: b3.share-dns.net and b.share-dns.net.