why-telegram.com - robtex.com

why-telegram.com

DNSSEC⚠️ Not signed
A43.128.142.70πŸ‡°πŸ‡· TENCENT-NET-AP-CN43.128.128.0/19 ACEVILLE PTE.LTD. 16 COLLYER QUAY 18-29 INCOME AT RAFFLES
NSa8.share-dns.com ⭐ ⚠️ Not in parent delegation
A172.64.53.25πŸ‡ΊπŸ‡Έ Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRip-172-64-53-25.defastlink.net
NSa.share-dns.com ⚠️ Not in zone NS records
A172.64.53.25πŸ‡ΊπŸ‡Έ Cloudflare172.64.53.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRip-172-64-53-25.defastlink.net
NSb.share-dns.net ⚠️ Not in zone NS records
A172.64.52.239πŸ‡ΊπŸ‡Έ Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRip-172-64-52-239.defastlink.net
NSb8.share-dns.net ⚠️ Not in parent delegation
A172.64.52.239πŸ‡ΊπŸ‡Έ Cloudflare172.64.52.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRip-172-64-52-239.defastlink.net
SOAa.share-dns.commaster@share-dns.com serial=1746433459

com

⚠️ On DNS blocklist: tif

Same first word

DNS History

5 records (5 active, 0 former)

NSa.share-dns.coma8.share-dns.comb.share-dns.netb8.share-dns.netA43.128.142.70
●NSa.share-dns.com2026-02-18 β†’ 2026-03-24 Β· 2 obs
● 2026-02-18 01:49:16
● 2026-03-24 01:20:54
●NSa8.share-dns.com2026-02-18 β†’ 2026-03-24 Β· 2 obs
● 2026-02-18 01:49:16
● 2026-03-24 01:20:54
●NSb.share-dns.net2026-02-18 β†’ 2026-03-24 Β· 2 obs
● 2026-02-18 01:49:16
● 2026-03-24 01:20:54
●NSb8.share-dns.net2026-02-18 β†’ 2026-03-24 Β· 2 obs
● 2026-02-18 01:49:16
● 2026-03-24 01:20:54
●A43.128.142.702026-02-18 β†’ 2026-03-24 Β· 2 obs
● 2026-02-18 01:49:16
● 2026-03-24 01:20:54

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
why-telegram.comb8.share-dns.net, a8.share-dns.com1 record

βœ… Authoritative Response

Server:172.64.52.239

NS records: b8.share-dns.net, a8.share-dns.com

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for why-telegram.com (unsigned zone)

⏱️ Timing

Total: 1223ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A143.128.142.70
NS2a.share-dns.com, b.share-dns.net
SOA1a.share-dns.com master.share-dns.com

πŸ“Œ Glue Records Collected

Total: 1

Out-of-bailiwick: 1 (a8.share-dns.com)

Analysis

IP Addresses

why-telegram.com maps to IP address 43.128.142.70.

Other host names, for instance zzz-telegram.com, telegram-nm.org, telegram-icu.com, ck-telegren.org and telegram-sast.com share IP numbers with why-telegram.com.

Name Servers

why-telegram.com is delegated to four name servers: a8.share-dns.com, a.share-dns.com, b8.share-dns.net and b.share-dns.net.

why-telegram.com at least partially shares name servers with other domains such as 1314yb.com, subjectgame.com, qco2o.com, ccshyx.com and tianxg.com.

These name servers are often used together with a11.share-dns.com, b11.share-dns.net, a9.share-dns.com, b9.share-dns.net, a6.share-dns.com, b6.share-dns.net, a2.share-dns.com, b2.share-dns.net, a4.share-dns.com and b4.share-dns.net.

Hostnames with a single IP

a8.share-dns.com resolves to 172.64.53.25

a.share-dns.com resolves to 172.64.53.25

b8.share-dns.net resolves to 172.64.52.239

b.share-dns.net resolves to 172.64.52.239

Hostnames pointing to 172.64.53.25: a8.share-dns.com and a.share-dns.com

Hostnames pointing to 172.64.52.239: b8.share-dns.net and b.share-dns.net