api-telegram.online - robtex.com
api-telegram.online
| DNSSEC | ⚠️ Not signed | ||||||
| NS | ns1.r01.ru ⭐ | ||||||
| A | 31.177.80.41🇷🇺 RU-CENTER31.177.80.0/24 -NETWORK | ||||||
| PTR | ns1.r01.ru | ||||||
| NS | ns2.r01.ru | ||||||
| A | 31.177.76.41🇷🇺 RU-CENTER31.177.76.0/24 RU-SERVICE-NETWORK | ||||||
| PTR | ns2.r01.ru | ||||||
| SOA | ns1.r01.rusupport@r01.ru 2026-04-24 #0 | ||||||
online
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | ns01.trs-dns.com ⭐ | ||||||
| NS | ns.trs-dns.com | ||||||
| NS | ns01.trs-dns.net | ||||||
| NS | ns10.trs-dns.info | ||||||
| NS | ns10.trs-dns.org | ||||||
| SOA | ns.trs-dns.comtrs-ops@tucows.com serial=1785164910 | ||||||
Same first word
api-telegram.online |
api-telegram.ru |
Similar names
DNS History
2 records (2 active, 0 former)
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| online | ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info | - |
| api-telegram.online | ns2.r01.ru, ns1.r01.ru | - |
✅ Authoritative Response
Server:31.177.76.41
NS records: ns2.r01.ru, ns1.r01.ru
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for api-telegram.online (unsigned zone)
⏱️ Timing
Total: 1082ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 2 | ns1.r01.ru, ns2.r01.ru |
| SOA | 1 | ns1.r01.ru support.r01.ru |
Analysis
Name Servers
The NS records for api-telegram.online delegate to ns1.r01.ru and ns2.r01.ru.
api-telegram.online uses the same name servers as several other domains — among them botanical-art.ru, ru-window.ru, mbs-dev.ru and two more.
api-telegram.online and other domains like pamir-spb.ru share at least a portion of their name servers.
ns1.r01.ru and ns2.r01.ru each resolve to one IP number: ns1.r01.ru points to 31.177.80.41 and ns2.r01.ru points to 31.177.76.41.