malovetsky.ru - dns.ninja

`malovetsky.ru`

DNSSEC	⚠️ Not signed
NS	`ns1.reg.ru` ⭐
		A	2a00:f940:9::1:1^{🇷🇺 AS-REGRU2a00:f940:9::/48 Reg.Ru Hosting}
		A	2a00:f940:9::2:1^{🇷🇺 AS-REGRU2a00:f940:9::/48 Reg.Ru Hosting}
		A	176.99.13.11^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	176.99.13.13^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	176.99.13.15^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	176.99.13.17^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	194.58.117.11^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	194.58.117.13^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	194.58.117.15^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
		A	194.58.117.17^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
NS	`ns2.reg.ru`
		A	2a00:f940:9::1:2^{🇷🇺 AS-REGRU2a00:f940:9::/48 Reg.Ru Hosting}
		A	2a00:f940:9::2:2^{🇷🇺 AS-REGRU2a00:f940:9::/48 Reg.Ru Hosting}
		A	176.99.13.12^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	176.99.13.14^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	176.99.13.16^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	176.99.13.18^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	194.58.117.12^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	194.58.117.14^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	194.58.117.16^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
		A	194.58.117.18^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
MX	`mx.yandex.ru` ⭐
		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	`v=spf1 redirect=_spf.yandex.net`
SOA	`ns1.reg.ru`hostmaster@ns1.reg.ru serial=1785404378

`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.net`hostmaster@ripn.net serial=4069976

Same first word

malovetsky.ru

DNS History

3 records (3 active, 0 former)

●NSns1.reg.ru2026-08-13 → 2026-08-13 · 2 obs

● 2026-08-13 11:24:58
● 2026-08-13 20:15:20

●NSns2.reg.ru2026-08-13 → 2026-08-13 · 2 obs

● 2026-08-13 11:24:58
● 2026-08-13 20:15:20

●MXmx.yandex.ru2026-08-13 → 2026-08-13 · 2 obs

● 2026-08-13 11:24:58
● 2026-08-13 20:15:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
ru	d.dns.ripn.net, a.dns.ripn.net, b.dns.ripn.net, c.tld-servers.ru...	-
malovetsky.ru	ns2.reg.ru, ns1.reg.ru	20 records

✅ Authoritative Response

Server:176.99.13.11

NS records: ns2.reg.ru, ns1.reg.ru

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for malovetsky.ru (unsigned zone)

⏱️ Timing

Total: 1237ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`ns1.reg.ru, ns2.reg.ru`
MX	1	`mx.yandex.ru (pri: 0)`
TXT	1	`v=spf1 redirect=_spf.yandex.net`
SOA	1	`ns1.reg.ru hostmaster.ns1.reg.ru`

📌 Glue Records Collected

Total: 20

Out-of-bailiwick: 20 (ns2.reg.ru, ns2.reg.ru, ns2.reg.ru...)

Analysis

Name Servers

malovetsky.ru has two authoritative name servers — ns1.reg.ru and ns2.reg.ru.

malovetsky.ru has the same name server delegation as a number of other domains, such as dobropark.ru, taobuy.ru, slimcenter.ru and two more.

Host names resolving to 10 IP numbers:

ns1.reg.ru points to 176.99.13.11, 176.99.13.13, 176.99.13.15 and 7 other IP addresses.

ns2.reg.ru points to 176.99.13.12, 176.99.13.14, 176.99.13.16 and 7 other IP addresses.

Mail Servers

malovetsky.ru routes its mail through a single mail server, mx.yandex.ru.

malovetsky.ru has the same mail server arrangement as a number of other domains, for example markerom.ru, lokomoko.ru, kasina.ru and two more.

malovetsky.ru shares at least some of its mail servers with other domains — for example opti.su, kulibin.club, spread-wings.ru and two more.

mx.yandex.ru directs to two IP numbers, 77.88.21.249 and 2a02:6b8::311.