`dev-bitrix13.sn32.ru`

DNSSEC	⚠️ Not signed
A	185.63.188.243^{🇷🇺 RU-JSCIOT185.63.188.0/22}
		PTR	`xander2.example.com`
NS	`sn32.ru` ⭐
		A	185.63.188.243^{🇷🇺 RU-JSCIOT185.63.188.0/22}
			PTR	`xander2.example.com`
NS	`ns1.sn32.ru` ⚠️ Not in parent delegation
		A	185.63.188.243^{🇷🇺 RU-JSCIOT185.63.188.0/22}
			PTR	`xander2.example.com`
NS	`ns2.sn32.ru` ⚠️ Not in parent delegation
		A	185.63.189.2^{🇷🇺 RU-JSCIOT185.63.188.0/22}
			PTR	`sn32.ru`
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	`v=spf1 ip4:185.63.188.243 a mx ~all`
SOA	`sn32.ru`a3@yansk.ru 2017-06-29 #5

`sn32.ru`

	DNSSEC	⚠️ Not signed
	A	185.63.188.243^{🇷🇺 RU-JSCIOT185.63.188.0/22}
	NS	`sn32.ru` ⭐
	NS	`ns1.sn32.ru`
	NS	`ns2.sn32.ru`
	MX	`mail.sn32.ru` ⭐
	TXT	`v=spf1 ip4:185.63.188.243 a mx ~all`
	SOA	`sn32.ru`root@example.com 2016-02-06 #78

DNS History

6 records (5 active, 1 former)

●NSns1.sn32.ru2026-02-15 → 2026-04-24 · 2 obs

● 2026-02-15 03:57:04
● 2026-04-24 15:33:54

●NSns2.sn32.ru2026-02-15 → 2026-04-24 · 2 obs

● 2026-02-15 03:57:04
● 2026-04-24 15:33:54

●NSsn32.ru2026-02-15 → 2026-04-24 · 2 obs

● 2026-02-15 03:57:04
● 2026-04-24 15:33:54

●MXmx.yandex.net2026-02-15 → 2026-04-24 · 2 obs

● 2026-02-15 03:57:04
● 2026-04-24 15:33:54

●A185.63.188.2432026-02-15 → 2026-04-24 · 3 obs

○ 2017-05-29 11:14:10
● 2026-02-15 03:57:04
● 2026-04-24 15:33:54

○A185.63.189.22017-05-25 → 2017-05-29 · 4 obs

● 2017-05-25 12:16:32
● 2017-05-29 11:14:10
○ 2026-02-15 03:57:04
○ 2026-04-24 15:33:54

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
ru	f.dns.ripn.net, a.dns.ripn.net, b.dns.ripn.net, d.dns.ripn.net...	-
sn32.ru	ns1.sn32.ru, ns2.sn32.ru	2 records

✅ Authoritative Response

Server:185.63.189.2

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for sn32.ru (unsigned zone)

⏱️ Timing

Total: 730ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`185.63.188.243`
NS	2	`ns2.sn32.ru, ns1.sn32.ru`
MX	1	`mx.yandex.net (pri: 10)`
TXT	1	`v=spf1 ip4:185.63.188.243 a mx ~all`
SOA	1	`sn32.ru a3.yansk.ru`

📌 Glue Records Collected

Total: 2

In-bailiwick: 2 (ns2.sn32.ru, ns1.sn32.ru)

Analysis

IP Addresses

dev-bitrix13.sn32.ru points to a single IP: 185.63.188.243.

Other host names, for instance centrrodniki32.ru, nbf32.ru, www.centrrodniki32.ru, paintball32.ru and sn32.ru share IP numbers with dev-bitrix13.sn32.ru.

Name Servers

dev-bitrix13.sn32.ru is delegated to three name servers: sn32.ru, ns1.sn32.ru and ns2.sn32.ru.

dev-bitrix13.sn32.ru partially shares name servers with other domains; examples include nix32.ru, pirolider.ru, lker.ru, kmtt32.ru and centrrodniki32.ru.

These name servers are often used with the name servers ns1.ns00.ru and ns2.ns00.ru.

Host names with one IP number: sn32.ru points to: 185.63.188.243; ns1.sn32.ru points to: 185.63.188.243; ns2.sn32.ru points to: 185.63.189.2. Host names that point to 185.63.188.243: sn32.ru and ns1.sn32.ru.

Mail Servers

dev-bitrix13.sn32.ru is handled by a single mail server, mx.yandex.net.

dev-bitrix13.sn32.ru has the same mail server setup as other domains, including lexfort.ru, www.amedia-spb.ru, lahta-center.info, uranka.ru and tibet4u.ru.

dev-bitrix13.sn32.ru shares some mail servers with other domains, for example khaosat.com, www.triumph-org.ru and maxfad.ru.

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

dev-bitrix13.sn32.ru - robtex.com