aplgo.top - robtex.com
aplgo.top
top
| DNSSEC | 🔒 Signed (DS record present) | ||||||
| NS | a.zdnscloud.com ⭐ | ||||||
| NS | a.zdnscloud.cn | ||||||
| NS | b.zdnscloud.cn | ||||||
| NS | c.zdnscloud.com | ||||||
| NS | d.zdnscloud.com | ||||||
| NS | e.zdnscloud.cn | ||||||
| NS | f.zdnscloud.cn | ||||||
| NS | i.zdnscloud.cn | ||||||
| NS | j.zdnscloud.com | ||||||
| TXT | 2026-07-27_19:15:01 | ||||||
| SOA | a.zdnscloud.comtd_dns_gtld@knet.cn serial=1396576482 | ||||||
Previously MX for
aplgo.top |
Same first word
Similar names
DNS History
11 records (7 active, 4 former)
●NSns1.beget.com2026-06-14 → 2026-07-27 · 3 obs
● 2026-06-14 13:13:20
● 2026-07-27 11:24:32
●NSns1.beget.pro2026-06-14 → 2026-07-27 · 3 obs
● 2026-06-14 13:13:20
● 2026-07-27 11:24:32
○NSns1.fozzy.com2018-08-03 → 2018-08-03 · 3 obs
○ 2026-06-14 13:13:20
○ 2026-07-27 11:24:32
●NSns2.beget.com2026-06-14 → 2026-07-27 · 3 obs
● 2026-06-14 13:13:20
● 2026-07-27 11:24:32
●NSns2.beget.pro2026-06-14 → 2026-07-27 · 3 obs
● 2026-06-14 13:13:20
● 2026-07-27 11:24:32
○NSns2.fozzy.com2018-08-03 → 2018-08-03 · 3 obs
○ 2026-06-14 13:13:20
○ 2026-07-27 11:24:32
○MXaplgo.top2018-08-03 → 2018-08-03 · 3 obs
○ 2026-06-14 13:13:20
○ 2026-07-27 11:24:32
●MXmx1.beget.com2026-06-14 → 2026-07-27 · 3 obs
● 2026-06-14 13:13:20
● 2026-07-27 11:24:32
●MXmx2.beget.com2026-06-14 → 2026-07-27 · 3 obs
● 2026-06-14 13:13:20
● 2026-07-27 11:24:32
●A45.130.41.1612026-06-14 → 2026-07-27 · 3 obs
● 2026-06-14 13:13:20
● 2026-07-27 11:24:32
○A88.212.220.62018-08-03 → 2018-08-03 · 3 obs
○ 2026-06-14 13:13:20
○ 2026-07-27 11:24:32
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| top | f.zdnscloud.cn, e.zdnscloud.cn, a.zdnscloud.cn, i.zdnscloud.cn... | - |
| aplgo.top | ns1.beget.com, ns1.beget.pro, ns2.beget.com, ns2.beget.pro | - |
✅ Authoritative Response
Server:185.50.27.12
NS records: ns1.beget.com, ns1.beget.pro, ns2.beget.com, ns2.beget.pro
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for aplgo.top (unsigned zone)
⏱️ Timing
Total: 1507ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 45.130.41.161 |
| NS | 4 | ns2.beget.pro, ns1.beget.pro... |
| MX | 2 | mx2.beget.com (pri: 20), mx1.beget.com (pri: 10) |
| TXT | 1 | v=spf1 redirect=beget.com |
| SOA | 1 | ns1.beget.com hostmaster.beget.com |
Analysis
IP Addresses
aplgo.top has exactly one IP address — 45.130.41.161.
www.7th-sky.ru, xn----7sbafngvmgii2a6d7f8b.xn--p1ai, al-zamil.ru plus two other host names have IP numbers in common with aplgo.top.
Name Servers
Four name servers handle the delegation for aplgo.top: ns1.beget.com, ns2.beget.com, ns1.beget.pro and ns2.beget.pro.
aplgo.top shares at least some of its name servers with other domains, including sibsvai.ru, permafisha.ru, rdb-chr.ru and two others.
These name servers are frequently paired with the name servers ns1.beget.ru and ns2.beget.ru.
The four host names ns1.beget.com, ns2.beget.com, ns1.beget.pro and ns2.beget.pro each resolve to a single IP address. ns1.beget.com and ns1.beget.pro both point to 93.92.81.0, while ns2.beget.com and ns2.beget.pro both point to 185.50.27.12.
Both ns1.beget.com and ns1.beget.pro resolve to 93.92.81.0 IP addresses each.
Both ns2.beget.com and ns2.beget.pro resolve to 185.50.27.12 IP addresses each.
Mail Servers
aplgo.top uses two mail servers, mx1.beget.com and mx2.beget.com.
The mail server setup of aplgo.top matches that of other domains such as 7trade.ru, auto(0x787878).ru, vender-climat.ru and two others.
aplgo.top shares at least some of its mail servers with other domains, such as riac34.ru and dadv.ru.
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.
Both mx1.beget.com and mx2.beget.com resolve to 185.78.30.95 IP addresses each.
Both mx1.beget.com and mx2.beget.com resolve to 185.78.30.126 IP addresses each.