telegram2.com - robtex.com
telegram2.com
com
| DNSSEC | π Signed (DS record present) | ||||||
| NS | a.gtld-servers.net β | ||||||
| NS | b.gtld-servers.net | ||||||
| NS | c.gtld-servers.net | ||||||
| NS | d.gtld-servers.net | ||||||
| NS | e.gtld-servers.net | ||||||
| NS | f.gtld-servers.net | ||||||
| NS | g.gtld-servers.net | ||||||
| NS | h.gtld-servers.net | ||||||
| NS | i.gtld-servers.net | ||||||
| NS | j.gtld-servers.net | ||||||
| NS | k.gtld-servers.net | ||||||
| NS | l.gtld-servers.net | ||||||
| NS | m.gtld-servers.net | ||||||
| SOA | a.gtld-servers.netnstld@verisign-grs.com serial=1774413007 | ||||||
Subdomains
www.telegram2.com |
Same first word
telegram2.app |
telegram2.com |
DNS History
10 records (6 active, 4 former)
βNSns1.name.com2026-02-17 β 2026-03-25 Β· 3 obs
β 2026-02-17 16:18:22
β 2026-03-25 04:32:46
βNSns1.telegram2.com2019-12-15 β 2019-12-15 Β· 3 obs
β 2026-02-17 16:18:22
β 2026-03-25 04:32:46
βNSns1cnb.name.com2026-02-17 β 2026-03-25 Β· 3 obs
β 2026-02-17 16:18:22
β 2026-03-25 04:32:46
βNSns2.telegram2.com2019-12-15 β 2019-12-15 Β· 3 obs
β 2026-02-17 16:18:22
β 2026-03-25 04:32:46
βNSns2knz.name.com2026-02-17 β 2026-03-25 Β· 3 obs
β 2026-02-17 16:18:22
β 2026-03-25 04:32:46
βNSns3cna.name.com2026-02-17 β 2026-03-25 Β· 3 obs
β 2026-02-17 16:18:22
β 2026-03-25 04:32:46
βNSns4fmw.name.com2026-02-17 β 2026-03-25 Β· 3 obs
β 2026-02-17 16:18:22
β 2026-03-25 04:32:46
βMXmail.telegram2.com2019-12-15 β 2019-12-15 Β· 3 obs
β 2026-02-17 16:18:22
β 2026-03-25 04:32:46
βA178.63.204.1412019-12-15 β 2019-12-15 Β· 3 obs
β 2026-02-17 16:18:22
β 2026-03-25 04:32:46
βA43.135.35.1762026-02-17 β 2026-03-25 Β· 3 obs
β 2026-02-17 16:18:22
β 2026-03-25 04:32:46
π DNS Trace
π Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| telegram2.com | ns2knz.name.com, ns4fmw.name.com, ns3cna.name.com, ns1cnb.name.com | 8 records |
β Authoritative Response
Server:163.114.217.17
NS records: ns2knz.name.com, ns4fmw.name.com, ns3cna.name.com, ns1cnb.name.com
π DNSSEC Status
β οΈ Insecure (no DNSSEC)
No DS record for telegram2.com (unsigned zone)
β±οΈ Timing
Total: 100ms | Queries: -
π Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 43.135.35.176 |
| NS | 4 | ns2knz.name.com, ns4fmw.name.com... |
| SOA | 1 | ns1.name.com hostmaster.nsone.net |
π Glue Records Collected
Total: 8
Out-of-bailiwick: 8 (ns2knz.name.com, ns2knz.name.com, ns4fmw.name.com...)
Analysis
Hierarchy
The parent of www.telegram2.com is telegram2.com.
IP Addresses
telegram2.com points to a single IP address: 43.135.35.176.
Other host names, for example telegram22.com, www.telegram22.com and www.telegram2.com share IPs with telegram2.com.
Name Servers
telegram2.com is delegated to five name servers: ns1.name.com, ns1cnb.name.com, ns2knz.name.com, ns3cna.name.com and ns4fmw.name.com.
telegram2.com at least partially shares name servers with other domains, for example doorga.com, llocspe(0x74697473).com, dailymotion.today, orichi.net and itmenaan.com.
these name servers are commonly used with the following name servers: ns2bkr.name.com, ns4bht.name.com, ns4hny.name.com, ns2dky.name.com, ns2ckr.name.com, ns3bfm.name.com, ns4clq.name.com, ns4fqz.name.com, ns2dhj.name.com and ns2fwz.name.com.
Host names with two IP numbers:
ns1.name.com points to: 2a00:edc0:107::1 and 163.114.216.17
ns1cnb.name.com points to: 2a00:edc0:107::1 and 163.114.216.17
ns2knz.name.com points to: 2402:cf80:107::1 and 163.114.216.49
ns3cna.name.com points to: 2a00:edc0:107::49 and 163.114.217.17
ns4fmw.name.com points to: 2402:cf80:107::49 and 163.114.217.49
Hosts pointing to 2a00:edc0:107::1: ns1.name.com and ns1cnb.name.com
Hosts pointing to 163.114.216.17: ns1.name.com and ns1cnb.name.com