sever33.ru - robtex.com

sever33.ru

DNSSEC⚠️ Not signed
A188.246.224.63🇷🇺 SELECTEL188.246.224.0/24 -NET
NSdns1.yandex.net ⭐
A2a02:6b8::213🇷🇺 TELETECH2a02:6b8::/32 Yandex network
PTRdns1.yandex.net
A213.180.204.213🇷🇺 TELETECH213.180.192.0/19 Yandex network
PTRdns1.yandex.net
NSdns2.yandex.net
A2a02:6b8:0:1::213🇷🇺 TELETECH2a02:6b8::/32 Yandex network
PTRdns2.yandex.net
A93.158.134.213🇷🇺 TELETECH93.158.128.0/18 Yandex enterprise network
PTRdns2.yandex.net
MXmx.yandex.net ⭐
A2a02:6b8::311🇷🇺 TELETECH2a02:6b8::/32 Yandex network
PTRmxfront.stable.qloud-b.yandex.net
A77.88.21.249🇷🇺 TELETECH77.88.0.0/18 Yandex enterprise network
PTRmxfront.stable.qloud-b.yandex.net
TXTv=spf1 ip4:188.246.224.63 include:_spf.yandex.net ~all
SOAdns1.yandex.netdns-hosting@yandex.ru serial=76

ru

DNSSEC🔒 Signed (DS record present)
NSa.dns.ripn.net ⭐
NSb.dns.ripn.net
NSd.dns.ripn.net
NSe.dns.ripn.net
NSf.dns.ripn.net
SOAa.dns.ripn.nethostmaster@ripn.net serial=4068147

Subdomains

crm.sever33.ru

Same first word

sever33.ru

DNS History

17 records (4 active, 13 former)

20162017201820192020202120222023202420252026NSdns1.yandex.netdns2.yandex.netns1.beget.prons1.beget.runs1.timeweb.runs2.beget.prons2.beget.runs2.timeweb.runs3.timeweb.orgns4.timeweb.orgMXmx.yandex.netmx.yandex.ruA188.246.224.63176.122.73.1982a03:6f00:1::5c35:7e485.101.153.8992.53.126.72
●NSdns1.yandex.net2015-08-04 → 2026-03-23 · 6 obs
● 2015-08-04 08:56:14
● 2015-12-05 06:05:16
○ 2016-03-04 19:07:00
○ 2017-09-03 09:37:52
● 2026-03-23 13:58:12
● 2026-03-23 21:53:08
●NSdns2.yandex.net2015-08-04 → 2026-03-23 · 6 obs
● 2015-08-04 08:56:14
● 2015-12-05 06:05:16
○ 2016-03-04 19:07:00
○ 2017-09-03 09:37:52
● 2026-03-23 13:58:12
● 2026-03-23 21:53:08
○NSns1.beget.pro2016-03-04 → 2016-06-26 · 5 obs
○ 2015-12-05 06:05:16
● 2016-03-04 19:07:00
● 2016-06-26 17:54:54
○ 2017-09-03 09:37:52
○ 2026-03-23 21:53:08
○NSns1.beget.ru2016-03-04 → 2016-06-26 · 5 obs
○ 2015-12-05 06:05:16
● 2016-03-04 19:07:00
● 2016-06-26 17:54:54
○ 2017-09-03 09:37:52
○ 2026-03-23 21:53:08
○NSns1.timeweb.ru2017-09-03 → 2017-09-03 · 4 obs
○ 2016-06-26 17:54:54
● 2017-09-03 09:37:52
○ 2026-03-23 13:58:12
○ 2026-03-23 21:53:08
○NSns2.beget.pro2016-03-04 → 2016-06-26 · 5 obs
○ 2015-12-05 06:05:16
● 2016-03-04 19:07:00
● 2016-06-26 17:54:54
○ 2017-09-03 09:37:52
○ 2026-03-23 21:53:08
○NSns2.beget.ru2016-03-04 → 2016-06-26 · 5 obs
○ 2015-12-05 06:05:16
● 2016-03-04 19:07:00
● 2016-06-26 17:54:54
○ 2017-09-03 09:37:52
○ 2026-03-23 21:53:08
○NSns2.timeweb.ru2017-09-03 → 2017-09-03 · 4 obs
○ 2016-06-26 17:54:54
● 2017-09-03 09:37:52
○ 2026-03-23 13:58:12
○ 2026-03-23 21:53:08
○NSns3.timeweb.org2017-09-03 → 2017-09-03 · 4 obs
○ 2016-06-26 17:54:54
● 2017-09-03 09:37:52
○ 2026-03-23 13:58:12
○ 2026-03-23 21:53:08
○NSns4.timeweb.org2017-09-03 → 2017-09-03 · 4 obs
○ 2016-06-26 17:54:54
● 2017-09-03 09:37:52
○ 2026-03-23 13:58:12
○ 2026-03-23 21:53:08
●MXmx.yandex.net2015-08-04 → 2026-03-23 · 6 obs
● 2015-08-04 08:56:14
● 2015-12-05 06:05:16
○ 2016-03-04 19:07:00
○ 2017-09-03 09:37:52
● 2026-03-23 13:58:12
● 2026-03-23 21:53:08
○MXmx.yandex.ru2016-03-04 → 2017-09-03 · 5 obs
○ 2015-12-05 06:05:16
● 2016-03-04 19:07:00
● 2017-09-03 09:37:52
○ 2026-03-23 13:58:12
○ 2026-03-23 21:53:08
○A176.122.73.1982015-08-04 → 2015-12-05 · 4 obs
● 2015-08-04 08:56:14
● 2015-12-05 06:05:16
○ 2016-03-04 19:07:00
○ 2026-03-23 21:53:08
●A188.246.224.632026-03-23 → 2026-03-23 · 3 obs
○ 2017-09-03 09:37:52
● 2026-03-23 13:58:12
● 2026-03-23 21:53:08
○A2a03:6f00:1::5c35:7e482017-09-03 → 2017-09-03 · 4 obs
○ 2016-06-26 17:54:54
● 2017-09-03 09:37:52
○ 2026-03-23 13:58:12
○ 2026-03-23 21:53:08
○A5.101.153.892016-03-04 → 2016-06-26 · 5 obs
○ 2015-12-05 06:05:16
● 2016-03-04 19:07:00
● 2016-06-26 17:54:54
○ 2017-09-03 09:37:52
○ 2026-03-23 21:53:08
○A92.53.126.722017-09-03 → 2017-09-03 · 4 obs
○ 2016-06-26 17:54:54
● 2017-09-03 09:37:52
○ 2026-03-23 13:58:12
○ 2026-03-23 21:53:08

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
rua.dns.ripn.net, f.dns.ripn.net, b.dns.ripn.net, d.dns.ripn.net...-
sever33.rudns1.yandex.net, dns2.yandex.net-

✅ Authoritative Response

Server:93.158.134.213

NS records: dns1.yandex.net, dns2.yandex.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for sever33.ru (unsigned zone)

⏱️ Timing

Total: 1478ms | Queries: -

📄 Records

TypeCountSample Data
A1188.246.224.63
NS2dns2.yandex.net, dns1.yandex.net
MX1mx.yandex.net (pri: 10)
TXT1v=spf1 ip4:188.246.224.63 include:_spf.y
SOA1dns1.yandex.net dns-hosting.yandex.ru

Analysis

Hierarchy

sever33.ru is the parent of crm.sever33.ru.

IP Addresses

sever33.ru points to a single IP number: 188.246.224.63.

Other host names, for instance odyssey.moscow, share IP numbers with sever33.ru.

Name Servers

sever33.ru is delegated to two name servers: dns1.yandex.net and dns2.yandex.net.

sever33.ru shares the same name server setup as other domains, for example dictator.pro, uash.ru, stnalog.ru, digitalproducts.ru and refemail.com.

sever33.ru at least partially shares name servers with other domains, for instance klincomp.ru, dpoets.ru, zhulen.ru, lekprice.ru and skawer.ru.

These name servers are often used with dns1.yandex.ru and dns2.yandex.ru.

Host names with two IP numbers:

dns1.yandex.net points to 2a02:6b8::213 and 213.180.204.213

dns2.yandex.net points to 2a02:6b8:0:1::213 and 93.158.134.213

Mail Servers

sever33.ru is handled by a single mail server, mx.yandex.net.

sever33.ru shares the same mail server setup as other domains, for instance kamenka.me, bahceci.eu, barissonmez.com, dxracer-online.ru and allcantrip.ru.

sever33.ru shares mail servers with other domains at least partially, including td-1.com, propozitsiya.com, smart-era.com, oval.az and abs52.ru.

Host mx.yandex.net resolves to two IPs: 2a02:6b8::311 and 77.88.21.249.