maxprotocol.ru - dns.ninja
maxprotocol.ru
| DNSSEC | ⚠️ Not signed | ||||||
| A | 157.180.118.165🇩🇪 Hetzner157.180.0.0/17 HETZNER-DC | ||||||
| PTR | static.165.118.180.157.clients.your-server.de | ||||||
| NS | ns1.yandexcloud.net ⭐ | ||||||
| A | 2a0d:d6c1:0:1a::1b4🇷🇺 YandexCloud2a0d:d6c1::/32 | ||||||
| PTR | ns1.yandexcloud.net | ||||||
| A | 84.201.185.208🇷🇺 YandexCloud84.201.184.0/22 Yandex Cloud | ||||||
| PTR | ns1.yandexcloud.net | ||||||
| NS | ns2.yandexcloud.net | ||||||
| A | 2a0d:d6c1:0:1a::2c9🇷🇺 YandexCloud2a0d:d6c1::/32 | ||||||
| PTR | ns2.yandexcloud.net | ||||||
| A | 84.201.189.229🇷🇺 YandexCloud84.201.188.0/23 Yandex Cloud | ||||||
| PTR | ns2.yandexcloud.net | ||||||
| MX | mx.yandex.net ⭐ | ||||||
| A | 2a02:6b8::311🇷🇺 TELETECH2a02:6b8::/32 Yandex network | ||||||
| PTR | mxfront.stable.qloud-b.yandex.net | ||||||
| A | 77.88.21.249🇷🇺 TELETECH77.88.0.0/18 Yandex enterprise network | ||||||
| PTR | mxfront.stable.qloud-b.yandex.net | ||||||
| TXT | google-site-verification=F8QAheUrqZh7x24oUVvkneRkx6DrpDVwD-mP60EqLYA | ||||||
| TXT | v=spf1 redirect=_spf.yandex.net | ||||||
| SOA | ns1.yandexcloud.netmx@cloud.yandex.net serial=1 | ||||||
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=4069853 | ||||||
Same first word
maxprotocol.ru |
DNS History
7 records (4 active, 3 former)
○NShelium.ns.hetzner.de2026-05-17 → 2026-05-17 · 2 obs
○ 2026-08-03 14:04:02
○NShydrogen.ns.hetzner.com2026-05-17 → 2026-05-17 · 2 obs
○ 2026-08-03 14:04:02
●NSns1.yandexcloud.net2026-08-03 → 2026-08-03 · 2 obs
● 2026-08-03 14:04:02
●NSns2.yandexcloud.net2026-08-03 → 2026-08-03 · 2 obs
● 2026-08-03 14:04:02
○NSoxygen.ns.hetzner.com2026-05-17 → 2026-05-17 · 2 obs
○ 2026-08-03 14:04:02
●MXmx.yandex.net2026-05-17 → 2026-08-03 · 2 obs
● 2026-08-03 14:04:02
●A157.180.118.1652026-05-17 → 2026-08-03 · 2 obs
● 2026-08-03 14:04:02
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| ru | a.dns.ripn.net, b.dns.ripn.net, c.tld-servers.ru, d.dns.ripn.net... | - |
| maxprotocol.ru | ns1.yandexcloud.net, ns2.yandexcloud.net | - |
✅ Authoritative Response
Server:84.201.185.208
NS records: ns1.yandexcloud.net, ns2.yandexcloud.net
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for maxprotocol.ru (unsigned zone)
⏱️ Timing
Total: 1453ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 157.180.118.165 |
| NS | 2 | ns1.yandexcloud.net, ns2.yandexcloud.net |
| MX | 1 | mx.yandex.net (pri: 10) |
| TXT | 2 | google-site-verification=F8QAheUrqZh7x24, v=spf1 redirect=_spf.yandex.net |
| SOA | 1 | ns1.yandexcloud.net mx.cloud.yandex.net |
Analysis
IP Addresses
maxprotocol.ru points to a single IP number: 157.180.118.165.
Name Servers
maxprotocol.ru uses two name servers for its delegation: ns1.yandexcloud.net and ns2.yandexcloud.net.
maxprotocol.ru shares its name server setup with other domains, including micord.ru, bot-to.ru, myplanet.info and two others.
At least some of maxprotocol.ru's name servers are also used by other domains, among them bork.hk.
The two host names ns1.yandexcloud.net and ns2.yandexcloud.net each have a pair of IP addresses: ns1.yandexcloud.net has 84.201.185.208 and 2a0d:d6c1:0:1a::1b4, and ns2.yandexcloud.net has 84.201.189.229 and 2a0d:d6c1:0:1a::2c9.
Mail Servers
maxprotocol.ru has one mail server: mx.yandex.net.
maxprotocol.ru shares the same mail server setup as other domains, including tiptopit.ru, krps.info, at-om.ru and two others.
maxprotocol.ru partially shares its mail servers with other domains, satanrise.org and crysmalab.com being examples.
The host mx.yandex.net resolves to 77.88.21.249 and 2a02:6b8::311 — two IP addresses.