`kriptomed.ru`

DNSSEC	⚠️ Not signed
A	2a00:f940:2:2:1:3:0:251^{🇷🇺 AS-REGRU2a00:f940:2::/48 Reg.Ru Hosting Route}
A	31.31.196.121^{🇷🇺 AS-REGRU31.31.196.0/24 Reg.Ru}
NS	`vip251.hosting.reg.ru` ⭐
		A	31.31.196.121^{🇷🇺 AS-REGRU31.31.196.0/24 Reg.Ru}
			PTR	`vip251.hosting.reg.ru`
NS	`ns1.hosting.reg.ru`
		A	31.31.194.245^{🇷🇺 AS-REGRU31.31.194.0/24 Reg.Ru}
			PTR	`ns1.hosting.reg.ru`
		A	31.31.194.251^{🇷🇺 AS-REGRU31.31.194.0/24 Reg.Ru}
			PTR	`ns17-1.hosting.reg.ru`
		A	31.31.196.37^{🇷🇺 AS-REGRU31.31.196.0/24 Reg.Ru}
			PTR	`ns18-2.hosting.reg.ru`
		A	31.31.196.52^{🇷🇺 AS-REGRU31.31.196.0/24 Reg.Ru}
			PTR	`ns1.hosting.reg.ru`
		A	31.31.196.61^{🇷🇺 AS-REGRU31.31.196.0/24 Reg.Ru}
			PTR	`ns30-2.hosting.reg.ru`
		A	31.31.196.180^{🇷🇺 AS-REGRU31.31.196.0/24 Reg.Ru}
			PTR	`ns31-1.hosting.reg.ru`
		A	31.31.198.177^{🇷🇺 AS-REGRU31.31.198.0/24 Reg.Ru}
			PTR	`ns2.hosting.reg.ru`
		A	37.140.192.20^{🇷🇺 AS-REGRU37.140.192.0/24 Reg.Ru}
			PTR	`ns29-1.hosting.reg.ru`
		A	37.140.192.93^{🇷🇺 AS-REGRU37.140.192.0/24 Reg.Ru}
			PTR	`ns32-1.hosting.reg.ru`
		A	37.140.193.121^{🇷🇺 AS-REGRU37.140.193.0/24 Reg.Ru}
			PTR	`ns2.hosting.reg.ru`
		A	37.140.196.144^{🇷🇺 AS-REGRU37.140.196.0/24 Reg.Ru}
			PTR	`ns37-1.hosting.reg.ru`
		A	194.58.91.38^{🇷🇺 AS-REGRU194.58.91.0/24 Reg.Ru}
			PTR	`ns38-1.hosting.reg.ru`
		A	194.67.73.6^{🇷🇺 AS-REGRU194.67.73.0/24 Reg.Ru-M9}
			PTR	`ns33-1.hosting.reg.ru`
		A	194.67.73.9^{🇷🇺 AS-REGRU194.67.73.0/24 Reg.Ru-M9}
			PTR	`ns34-2.hosting.reg.ru`
NS	`ns2.hosting.reg.ru`
		A	31.31.194.244^{🇷🇺 AS-REGRU31.31.194.0/24 Reg.Ru}
			PTR	`ns1.hosting.reg.ru`
		A	31.31.196.34^{🇷🇺 AS-REGRU31.31.196.0/24 Reg.Ru}
			PTR	`ns17-2.hosting.reg.ru`
		A	31.31.196.53^{🇷🇺 AS-REGRU31.31.196.0/24 Reg.Ru}
			PTR	`ns1.hosting.reg.ru`
		A	31.31.196.71^{🇷🇺 AS-REGRU31.31.196.0/24 Reg.Ru}
			PTR	`ns32-2.hosting.reg.ru`
		A	31.31.198.161^{🇷🇺 AS-REGRU31.31.198.0/24 Reg.Ru}
			PTR	`ns29-2.hosting.reg.ru`
		A	31.31.198.178^{🇷🇺 AS-REGRU31.31.198.0/24 Reg.Ru}
			PTR	`ns2.hosting.reg.ru`
		A	37.140.192.31^{🇷🇺 AS-REGRU37.140.192.0/24 Reg.Ru}
			PTR	`ns37-2.hosting.reg.ru`
		A	37.140.192.55^{🇷🇺 AS-REGRU37.140.192.0/24 Reg.Ru}
			PTR	`ns30-1.hosting.reg.ru`
		A	37.140.192.58^{🇷🇺 AS-REGRU37.140.192.0/24 Reg.Ru}
			PTR	`ns18-1.hosting.reg.ru`
		A	37.140.192.160^{🇷🇺 AS-REGRU37.140.192.0/24 Reg.Ru}
			PTR	`ns31-2.hosting.reg.ru`
		A	37.140.193.120^{🇷🇺 AS-REGRU37.140.193.0/24 Reg.Ru}
			PTR	`ns2.hosting.reg.ru`
		A	37.140.194.37^{🇷🇺 AS-REGRU37.140.194.0/24 Reg.Ru}
			PTR	`ns38-2.hosting.reg.ru`
		A	194.67.73.7^{🇷🇺 AS-REGRU194.67.73.0/24 Reg.Ru-M9}
			PTR	`ns33-2.hosting.reg.ru`
		A	194.67.73.8^{🇷🇺 AS-REGRU194.67.73.0/24 Reg.Ru-M9}
			PTR	`ns34-1.hosting.reg.ru`
MX	`mx01.lancloud.ru` ⭐
		A	45.84.86.41^{🇷🇺 RU-LANCLOUD-AS0145.84.84.0/22}
			PTR	`mx01.lancloud.ru`
MX	`mx02.lancloud.ru` ⭐
		A	45.84.86.42^{🇷🇺 RU-LANCLOUD-AS0145.84.84.0/22}
			PTR	`mx02.lancloud.ru`
MX	`mx03.lancloud.ru` ⭐
		A	45.84.86.43^{🇷🇺 RU-LANCLOUD-AS0145.84.84.0/22}
			PTR	`mx03.lancloud.ru`
MX	`mx04.lancloud.ru` ⭐
		A	45.84.86.44^{🇷🇺 RU-LANCLOUD-AS0145.84.84.0/22}
			PTR	`mx04.lancloud.ru`
TXT	`_globalsign-domain-verification=sW7EZnw9MfoHrcxxQDlMrLZ0lAUMzJBIaptnXL_XdL`
TXT	`v=spf1 ip4:31.31.196.121 ip4:45.84.86.81 ip4:92.53.116.149 a include:_spf.hos...`
SOA	`vip251.hosting.reg.ru`support@reg.ru 2024-06-21 #12

`ru`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.dns.ripn.net` ⭐
	NS	`b.dns.ripn.net`
	NS	`d.dns.ripn.net`
	NS	`e.dns.ripn.net`
	NS	`f.dns.ripn.net`
	SOA	`a.dns.ripn.net`hostmaster@ripn.net serial=4068302

Same first word

kriptomed.ru

DNS History

21 records (9 active, 12 former)

○NShosting1.telekom.ru2015-06-13 → 2016-06-20 · 4 obs

● 2015-06-13 04:54:08
● 2016-06-20 19:29:58
○ 2017-04-10 03:11:16
○ 2026-03-28 04:41:30

●NSns1.hosting.reg.ru2026-03-24 → 2026-03-28 · 3 obs

○ 2017-04-10 03:11:16
● 2026-03-24 21:54:46
● 2026-03-28 04:41:30

○NSns1.timeweb.ru2017-04-10 → 2017-04-10 · 4 obs

○ 2016-06-20 19:29:58
● 2017-04-10 03:11:16
○ 2026-03-24 21:54:46
○ 2026-03-28 04:41:30

●NSns2.hosting.reg.ru2026-03-24 → 2026-03-28 · 3 obs

○ 2017-04-10 03:11:16
● 2026-03-24 21:54:46
● 2026-03-28 04:41:30

○NSns2.telekom.ru2015-06-13 → 2016-06-20 · 4 obs

● 2015-06-13 04:54:08
● 2016-06-20 19:29:58
○ 2017-04-10 03:11:16
○ 2026-03-28 04:41:30

○NSns2.timeweb.ru2017-04-10 → 2017-04-10 · 4 obs

○ 2016-06-20 19:29:58
● 2017-04-10 03:11:16
○ 2026-03-24 21:54:46
○ 2026-03-28 04:41:30

○NSns3.timeweb.org2017-04-10 → 2017-04-10 · 4 obs

○ 2016-06-20 19:29:58
● 2017-04-10 03:11:16
○ 2026-03-24 21:54:46
○ 2026-03-28 04:41:30

○NSns4.timeweb.org2017-04-10 → 2017-04-10 · 4 obs

○ 2016-06-20 19:29:58
● 2017-04-10 03:11:16
○ 2026-03-24 21:54:46
○ 2026-03-28 04:41:30

●NSvip251.hosting.reg.ru2026-03-24 → 2026-03-28 · 3 obs

○ 2017-04-10 03:11:16
● 2026-03-24 21:54:46
● 2026-03-28 04:41:30

○MXmail.kriptomed.ru2015-06-13 → 2016-06-20 · 4 obs

● 2015-06-13 04:54:08
● 2016-06-20 19:29:58
○ 2017-04-10 03:11:16
○ 2026-03-28 04:41:30

●MXmx01.lancloud.ru2026-03-24 → 2026-03-28 · 3 obs

○ 2017-04-10 03:11:16
● 2026-03-24 21:54:46
● 2026-03-28 04:41:30

●MXmx02.lancloud.ru2026-03-24 → 2026-03-28 · 3 obs

○ 2017-04-10 03:11:16
● 2026-03-24 21:54:46
● 2026-03-28 04:41:30

●MXmx03.lancloud.ru2026-03-24 → 2026-03-28 · 3 obs

○ 2017-04-10 03:11:16
● 2026-03-24 21:54:46
● 2026-03-28 04:41:30

●MXmx04.lancloud.ru2026-03-24 → 2026-03-28 · 3 obs

○ 2017-04-10 03:11:16
● 2026-03-24 21:54:46
● 2026-03-28 04:41:30

○MXmx1.timeweb.ru2017-04-10 → 2017-04-10 · 4 obs

○ 2016-06-20 19:29:58
● 2017-04-10 03:11:16
○ 2026-03-24 21:54:46
○ 2026-03-28 04:41:30

○MXmx2.timeweb.ru2017-04-10 → 2017-04-10 · 4 obs

○ 2016-06-20 19:29:58
● 2017-04-10 03:11:16
○ 2026-03-24 21:54:46
○ 2026-03-28 04:41:30

○A212.114.13.1632015-06-13 → 2016-06-20 · 4 obs

● 2015-06-13 04:54:08
● 2016-06-20 19:29:58
○ 2017-04-10 03:11:16
○ 2026-03-28 04:41:30

●A2a00:f940:2:2:1:3:0:2512026-03-24 → 2026-03-28 · 3 obs

○ 2017-04-10 03:11:16
● 2026-03-24 21:54:46
● 2026-03-28 04:41:30

○A2a03:6f00:1::5c35:7e162017-04-10 → 2017-04-10 · 4 obs

○ 2016-06-20 19:29:58
● 2017-04-10 03:11:16
○ 2026-03-24 21:54:46
○ 2026-03-28 04:41:30

●A31.31.196.1212026-03-24 → 2026-03-28 · 3 obs

○ 2017-04-10 03:11:16
● 2026-03-24 21:54:46
● 2026-03-28 04:41:30

○A92.53.96.562017-04-10 → 2017-04-10 · 4 obs

○ 2016-06-20 19:29:58
● 2017-04-10 03:11:16
○ 2026-03-24 21:54:46
○ 2026-03-28 04:41:30

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
ru	a.dns.ripn.net, b.dns.ripn.net, d.dns.ripn.net, e.dns.ripn.net...	-
kriptomed.ru	ns1.hosting.reg.ru, ns2.hosting.reg.ru	-

✅ Authoritative Response

Server:31.31.194.244

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for kriptomed.ru (unsigned zone)

⏱️ Timing

Total: 2035ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`31.31.196.121`
AAAA	1	`2a00:f940:2:2:1:3:0:251`
NS	2	`ns1.hosting.reg.ru, ns2.hosting.reg.ru`
MX	4	`mx04.lancloud.ru (pri: 10), mx03.lancloud.ru (pri: 10)...`
TXT	2	`_globalsign-domain-verification=sW7EZnw9, v=spf1 ip4:31.31.196.121 ip4:45.84.86.81`
SOA	1	`vip251.hosting.reg.ru support.reg.ru`

Analysis

IP Addresses

Two IP numbers are pointed to by kriptomed.ru: 2a00:f940:2:2:1:3:0:251 and 31.31.196.121.

other host names include tetrafish.ru, devochki.pro, aprcenter.ru, mail.freycouture.com and www.megaprint.ru; they share IP numbers with kriptomed.ru.

Name Servers

kriptomed.ru is delegated to three name servers ns1.hosting.reg.ru, ns2.hosting.reg.ru and vip251.hosting.reg.ru.

kriptomed.ru at least partially shares name servers with other domains, for instance tehastor.ru, pesokkzn.ru, xn--80aggamacmmm9ap9f.xn--p1ai, logeek.ru and mx.sogdianatur.ru.

These name servers are commonly used with server256.hosting.reg.ru, server152.hosting.reg.ru, server107.hosting.reg.ru, server279.hosting.reg.ru and server5.hosting.reg.ru.

Fourteen IPs:

ns1.hosting.reg.ru points to: 31.31.194.245, 31.31.194.251, 31.31.196.37, 31.31.196.52, 31.31.196.61, 31.31.196.180, 31.31.198.177, 37.140.192.20, 37.140.192.93, 37.140.193.121, 37.140.196.144, 194.58.91.38, 194.67.73.6 and 194.67.73.9.

ns2.hosting.reg.ru points to: 31.31.194.244, 31.31.196.34, 31.31.196.53, 31.31.196.71, 31.31.198.161, 31.31.198.178, 37.140.192.31, 37.140.192.55, 37.140.192.58, 37.140.192.160, 37.140.193.120, 37.140.194.37, 194.67.73.7 and 194.67.73.8.

One IP:

vip251.hosting.reg.ru points to: 31.31.196.121.

Mail Servers

kriptomed.ru is handled by four mail servers: mx01.lancloud.ru, mx02.lancloud.ru, mx03.lancloud.ru and mx04.lancloud.ru.

kriptomed.ru shares at least partially some mail servers with other domains, for instance www.mte.ru, bungur.ru, ifdk.com, poseidongroup.ru and fruktovayalavka.ru.

Host names with one IP number: mx01.lancloud.ru points to: 45.84.86.41; mx02.lancloud.ru points to: 45.84.86.42; mx03.lancloud.ru points to: 45.84.86.43; mx04.lancloud.ru points to: 45.84.86.44.

kriptomed.ru - robtex.com

kriptomed.ru

ru

Same first word

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

Analysis

IP Addresses

Name Servers

Mail Servers

`kriptomed.ru`

`ru`