telegrambot.pro - dns.ninja
telegrambot.pro
pro
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a0.pro.afilias-nst.info ⭐ | ||||||
| NS | a2.pro.afilias-nst.info | ||||||
| NS | b0.pro.afilias-nst.org | ||||||
| NS | b2.pro.afilias-nst.org | ||||||
| NS | c0.pro.afilias-nst.info | ||||||
| NS | d0.pro.afilias-nst.org | ||||||
| SOA | a0.pro.afilias-nst.infohostmaster@donuts.email serial=1785633626 | ||||||
Same first word
telegrambot.com |
telegrambot.pro |
telegrambot.agency |
telegrambot.net |
telegrambot.co |
telegrambot.space |
telegrambot.website |
telegrambot.biz |
telegrambot.icu |
Similar names
DNS History
15 records (7 active, 8 former)
○NSdns7.parkpage.foundationapi.com2026-03-13 → 2026-03-30 · 5 obs
● 2026-03-13 02:01:24
● 2026-03-30 02:57:18
○ 2026-07-23 10:54:58
○ 2026-08-02 01:25:32
○NSdns8.parkpage.foundationapi.com2026-03-13 → 2026-03-30 · 5 obs
● 2026-03-13 02:01:24
● 2026-03-30 02:57:18
○ 2026-07-23 10:54:58
○ 2026-08-02 01:25:32
●NSns1.beget.com2026-02-21 → 2026-08-02 · 7 obs
● 2026-02-21 12:04:16
● 2026-03-09 01:31:10
○ 2026-03-13 02:01:24
○ 2026-03-30 02:57:18
● 2026-07-23 10:54:58
● 2026-08-02 01:25:32
●NSns1.beget.pro2026-02-21 → 2026-08-02 · 7 obs
● 2026-02-21 12:04:16
● 2026-03-09 01:31:10
○ 2026-03-13 02:01:24
○ 2026-03-30 02:57:18
● 2026-07-23 10:54:58
● 2026-08-02 01:25:32
○NSns1.verification-hold.suspended-domain.com2026-03-13 → 2026-03-30 · 5 obs
● 2026-03-13 02:01:24
● 2026-03-30 02:57:18
○ 2026-07-23 10:54:58
○ 2026-08-02 01:25:32
○NSns2.4tek.ru2016-12-10 → 2017-07-08 · 4 obs
● 2017-07-08 03:31:50
○ 2026-02-21 12:04:16
○ 2026-08-02 01:25:32
●NSns2.beget.com2026-02-21 → 2026-08-02 · 7 obs
● 2026-02-21 12:04:16
● 2026-03-09 01:31:10
○ 2026-03-13 02:01:24
○ 2026-03-30 02:57:18
● 2026-07-23 10:54:58
● 2026-08-02 01:25:32
●NSns2.beget.pro2026-02-21 → 2026-08-02 · 7 obs
● 2026-02-21 12:04:16
● 2026-03-09 01:31:10
○ 2026-03-13 02:01:24
○ 2026-03-30 02:57:18
● 2026-07-23 10:54:58
● 2026-08-02 01:25:32
○NSns3.4tek.ru2016-12-10 → 2017-07-08 · 4 obs
● 2017-07-08 03:31:50
○ 2026-02-21 12:04:16
○ 2026-08-02 01:25:32
○MXmail.4tek.ru2016-12-10 → 2017-07-08 · 4 obs
● 2017-07-08 03:31:50
○ 2026-02-21 12:04:16
○ 2026-08-02 01:25:32
●MXmx1.beget.com2026-02-21 → 2026-08-02 · 7 obs
● 2026-02-21 12:04:16
● 2026-03-09 01:31:10
○ 2026-03-13 02:01:24
○ 2026-03-30 02:57:18
● 2026-07-23 10:54:58
● 2026-08-02 01:25:32
●MXmx2.beget.com2026-02-21 → 2026-08-02 · 7 obs
● 2026-02-21 12:04:16
● 2026-03-09 01:31:10
○ 2026-03-13 02:01:24
○ 2026-03-30 02:57:18
● 2026-07-23 10:54:58
● 2026-08-02 01:25:32
○A144.76.68.1822016-12-10 → 2017-07-08 · 4 obs
● 2017-07-08 03:31:50
○ 2026-02-21 12:04:16
○ 2026-08-02 01:25:32
○A15.197.240.202026-03-13 → 2026-03-30 · 5 obs
● 2026-03-13 02:01:24
● 2026-03-30 02:57:18
○ 2026-07-23 10:54:58
○ 2026-08-02 01:25:32
●A62.217.180.752026-02-21 → 2026-08-02 · 7 obs
● 2026-02-21 12:04:16
● 2026-03-09 01:31:10
○ 2026-03-13 02:01:24
○ 2026-03-30 02:57:18
● 2026-07-23 10:54:58
● 2026-08-02 01:25:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| pro | a0.pro.afilias-nst.info, b2.pro.afilias-nst.org, c0.pro.afilias-nst.info, a2.pro.afilias-nst.info... | 12 records |
| telegrambot.pro | ns2.beget.pro, ns1.beget.pro, ns1.beget.com, ns2.beget.com | 2 records |
✅ Authoritative Response
Server:185.50.27.12
NS records: ns2.beget.pro, ns1.beget.pro, ns1.beget.com, ns2.beget.com
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for telegrambot.pro (unsigned zone)
⏱️ Timing
Total: 1907ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 62.217.180.75 |
| NS | 4 | ns2.beget.pro, ns1.beget.pro... |
| MX | 2 | mx1.beget.com (pri: 10), mx2.beget.com (pri: 20) |
| TXT | 1 | v=spf1 redirect=beget.com |
| SOA | 1 | ns1.beget.com hostmaster.beget.com |
📌 Glue Records Collected
Total: 14
Out-of-bailiwick: 14 (d0.pro.afilias-nst.org, c0.pro.afilias-nst.info, b2.pro.afilias-nst.org...)
Analysis
IP Addresses
telegrambot.pro directs to one IP number, which is 62.217.180.75.
Among the host names that share IP numbers with telegrambot.pro are promo.mrm.ru, www.gidmo.ru, drmazay.ru and two others.
Name Servers
The domain telegrambot.pro is delegated to these four name servers: ns1.beget.com, ns2.beget.com, ns1.beget.pro and ns2.beget.pro.
At least some of telegrambot.pro's name servers are shared with other domains, for example windstarcruises.ru, butirka.ru, 3nrg.ru and two more.
These name servers tend to be deployed in combination with the name servers ns1.beget.ru and ns2.beget.ru.
ns1.beget.com, ns2.beget.com, ns1.beget.pro and ns2.beget.pro each point to exactly one IP address. ns1.beget.com directs to 93.92.81.0, ns2.beget.com directs to 185.50.27.12, ns1.beget.pro directs to 93.92.81.0 and ns2.beget.pro directs to 185.50.27.12. Two pairs share an IP: ns1.beget.com and ns1.beget.pro share 93.92.81.0, and ns2.beget.com and ns2.beget.pro share 185.50.27.12.
ns1.beget.com and ns1.beget.pro each have 93.92.81.0 IP addresses.
ns2.beget.com and ns2.beget.pro each have 185.50.27.12 IP addresses.
Mail Servers
The MX records for telegrambot.pro point to two mail servers: mx1.beget.com and mx2.beget.com.
telegrambot.pro has the same mail server arrangement as a number of other domains, for example event-prof.ru, www.metalgorstal.ru, muzclips.ru and two more.
The hosts mx1.beget.com and mx2.beget.com each resolve to four IP addresses: mx1.beget.com points to 5.101.158.67, 5.101.158.68, 185.78.30.95 and 185.78.30.126 while mx2.beget.com points to 185.78.30.48, 185.78.30.71, 185.78.30.95 and 185.78.30.126.
mx1.beget.com and mx2.beget.com each have 185.78.30.95 IP addresses.
mx1.beget.com and mx2.beget.com each have 185.78.30.126 IP addresses.