telegram.org.ru - robtex.com
telegram.org.ru
org.ru
| DNSSEC | ⚠️ Not signed | ||||||
| A | 194.226.41.15🇷🇺 MSK-IX_Services194.226.41.0/24 | ||||||
| NS | a.dns-servers.net.ru ⭐ ⚠️ Not in parent delegation | ||||||
| NS | b.dns-servers.net.ru ⚠️ Not in parent delegation | ||||||
| NS | d.dns-servers.net.ru ⚠️ Not in parent delegation | ||||||
| NS | e.dns-servers.net.ru ⚠️ Not in parent delegation | ||||||
| NS | f.dns-servers.net.ru ⚠️ Not in parent delegation | ||||||
| SOA | a.dns-servers.net.ruhostmaster@ripn.net serial=2274053601 | ||||||
rank #12994 in the tld
WOT: SAFE (61/100)
WOT: SAFE (66/100)
📈 Tranco rank: #3,471
Subdomains
Same first word
Similar names
DNS History
10 records (4 active, 6 former)
●NSadrian.ns.cloudflare.com2026-02-18 → 2026-03-21 · 3 obs
● 2026-02-18 10:35:06
● 2026-03-21 01:10:10
○NSdns.fastdns24.com2016-12-05 → 2017-05-20 · 4 obs
● 2017-05-20 03:29:58
○ 2026-02-18 10:35:06
○ 2026-03-21 01:10:10
○NSdns2.fastdns24.org2016-12-05 → 2017-05-20 · 4 obs
● 2017-05-20 03:29:58
○ 2026-02-18 10:35:06
○ 2026-03-21 01:10:10
○NSdns3.fastdns24.eu2016-12-05 → 2017-05-20 · 4 obs
● 2017-05-20 03:29:58
○ 2026-02-18 10:35:06
○ 2026-03-21 01:10:10
○NSdns4.fastdns24.link2016-12-05 → 2017-05-20 · 4 obs
● 2017-05-20 03:29:58
○ 2026-02-18 10:35:06
○ 2026-03-21 01:10:10
●NSken.ns.cloudflare.com2026-02-18 → 2026-03-21 · 3 obs
● 2026-02-18 10:35:06
● 2026-03-21 01:10:10
○MXmail.telegram.org.ru2016-12-05 → 2017-05-20 · 4 obs
● 2017-05-20 03:29:58
○ 2026-02-18 10:35:06
○ 2026-03-21 01:10:10
●MXmx.yandex.net2026-02-18 → 2026-03-21 · 3 obs
● 2026-02-18 10:35:06
● 2026-03-21 01:10:10
○A5.45.114.752016-12-05 → 2017-05-20 · 4 obs
● 2017-05-20 03:29:58
○ 2026-02-18 10:35:06
○ 2026-03-21 01:10:10
●A5.45.120.1282026-02-18 → 2026-03-21 · 3 obs
● 2026-02-18 10:35:06
● 2026-03-21 01:10:10
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| ru | a.dns.ripn.net, d.dns.ripn.net, f.dns.ripn.net, b.dns.ripn.net... | - |
| telegram.org.ru | adrian.ns.cloudflare.com, ken.ns.cloudflare.com | - |
✅ Authoritative Response
Server: 108.162.192.57
NS records: adrian.ns.cloudflare.com, ken.ns.cloudflare.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for telegram.org.ru (unsigned zone)
⏱️ Timing
Total: 919ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 5.45.120.128 |
| NS | 2 | adrian.ns.cloudflare.com, ken.ns.cloudflare.com |
| MX | 1 | mx.yandex.net (pri: 10) |
| TXT | 2 | google-site-verification=GtnHLkj_wvXjrZq, v=spf1 include:_spf.yandex.net ~all |
| SOA | 1 | adrian.ns.cloudflare.com dns.cloudflare. |
Analysis
Hierarchy
telegram.org.ru is the parent of mail.telegram.org.ru and www.telegram.org.ru.
IP Addresses
telegram.org.ru points to an IP address: 5.45.120.128.
Other host names, for instance mail.telegram.org.ru and www.telegram.org.ru, share IP numbers with telegram.org.ru.
Name Servers
Two name servers adrian.ns.cloudflare.com and ken.ns.cloudflare.com handle the delegation for telegram.org.ru.
telegram.org.ru shares the same name server setup as other domains, for instance evervictory-it.com, altaperformanceweb.com.br, bloomberry.nl, polkadotplant.com and add-groups.com.
telegram.org.ru at least partially shares name servers with other domains, for instance hankio.com, xmhybz.com, javachatpodcast.com, aochalongvillaandspa.com and yoakimbridge.com.
These name servers are commonly used alongside tim.ns.cloudflare.com, lisa.ns.cloudflare.com and steven.ns.cloudflare.com.
Six IP addresses per host:
adrian.ns.cloudflare.com points to 2606:4700:50::adf5:3a39, 2803:f800:50::6ca2:c039, 2a06:98c1:50::ac40:2039, 108.162.192.57, 172.64.32.57 and 173.245.58.57; ken.ns.cloudflare.com points to 2606:4700:58::adf5:3b7f, 2803:f800:50::6ca2:c17f, 2a06:98c1:50::ac40:217f, 108.162.193.127, 172.64.33.127 and 173.245.59.127
Mail Servers
telegram.org.ru is handled by a single mail server, mx.yandex.net.
telegram.org.ru uses the same mail server setup as other domains, for instance bamboo.dance, tilbagevise.ru, elermen.com, tr-api.com and fitness2.ru.
telegram.org.ru shares some mail servers with other domains, for example enerpac-russia.com, net-ra.ru and litvinova-astrolog.ru.
mx.yandex.net resolves to two IPs: 2a02:6b8::311 and 77.88.21.249.