telegram-api.ru - robtex.com
telegram-api.ru
ru
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.dns.ripn.net ⭐ | ||||||
| NS | b.dns.ripn.net | ||||||
| NS | c.tld-servers.ru | ||||||
| NS | d.dns.ripn.net | ||||||
| NS | e.dns.ripn.net | ||||||
| NS | f.dns.ripn.net | ||||||
| SOA | a.dns.ripn.nethostmaster@ripn.net serial=4069767 | ||||||
Subdomains
www.telegram-api.ru |
Same first word
Similar names
DNS History
3 records (3 active, 0 former)
●A194.31.174.2532026-05-13 → 2026-07-27 · 2 obs
● 2026-07-27 13:46:44
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| ru | a.dns.ripn.net, b.dns.ripn.net, d.dns.ripn.net, e.dns.ripn.net... | - |
| telegram-api.ru | ns1.reg.ru, ns2.reg.ru | 20 records |
✅ Authoritative Response
Server:176.99.13.12
NS records: ns1.reg.ru, ns2.reg.ru
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for telegram-api.ru (unsigned zone)
⏱️ Timing
Total: 648ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 194.31.174.253 |
| NS | 2 | ns1.reg.ru, ns2.reg.ru |
| SOA | 1 | ns1.reg.ru hostmaster.ns1.reg.ru |
📌 Glue Records Collected
Total: 20
Out-of-bailiwick: 20 (ns2.reg.ru, ns2.reg.ru, ns2.reg.ru...)
Analysis
Hierarchy
The domain www.telegram-api.ru falls under the parent telegram-api.ru.
IP Addresses
telegram-api.ru resolves to one IP address: 194.31.174.253.
Other host names, such as www.telegram-api.ru, share IP numbers with telegram-api.ru.
Name Servers
telegram-api.ru is delegated to two name servers: ns1.reg.ru and ns2.reg.ru.
telegram-api.ru uses the same name servers as several other domains — among them 2aps.ru, woodparts.ru, avto69.ru and two more.
At least some of telegram-api.ru's name servers are shared with other domains, for example qpage.ru and bril.ru.
These name servers tend to be deployed in combination with the name servers ns1.agava.net.ru and ns2.agava.net.ru.
Hostnames that resolve to 10 IP addresses:
ns1.reg.ru resolves to 176.99.13.11, 176.99.13.13, 176.99.13.15 and 7 other IP addresses.
ns2.reg.ru resolves to 176.99.13.12, 176.99.13.14, 176.99.13.16 and 7 other IP addresses.