🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`visualdata.pro`

DNSSEC	⚠️ Not signed
A	2a00:f940:2:2:1:1:0:172^{🇷🇺 AS-REGRU2a00:f940:2::/48 Reg.Ru Hosting Route}
A	31.31.196.214^{🇷🇺 AS-REGRU31.31.196.0/24 Reg.Ru}
NS	`server172.hosting.reg.ru` ⭐
		A	31.31.196.214^{🇷🇺 AS-REGRU31.31.196.0/24 Reg.Ru}
			PTR	`server172.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	`mx1.hosting.reg.ru` ⭐
		A	31.31.194.240^{🇷🇺 AS-REGRU31.31.194.0/24 Reg.Ru}
			PTR	`relay.hosting.reg.ru`
		A	31.31.194.241^{🇷🇺 AS-REGRU31.31.194.0/24 Reg.Ru}
			PTR	`relay.hosting.reg.ru`
MX	`mx2.hosting.reg.ru`⁽²⁰⁾
		A	31.31.194.240^{🇷🇺 AS-REGRU31.31.194.0/24 Reg.Ru}
			PTR	`relay.hosting.reg.ru`
		A	31.31.194.241^{🇷🇺 AS-REGRU31.31.194.0/24 Reg.Ru}
			PTR	`relay.hosting.reg.ru`
TXT	`v=spf1 ip4:31.31.196.214 a mx include:_spf.hosting.reg.ru ~all`
SOA	`server172.hosting.reg.ru`support@reg.ru 2025-04-05 #8

`pro`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a0.pro.afilias-nst.info` ⭐
	NS	`a2.pro.afilias-nst.info`
	NS	`b0.pro.afilias-nst.org`
	NS	`b2.pro.afilias-nst.org`
	NS	`c0.pro.afilias-nst.info`
	NS	`d0.pro.afilias-nst.org`
	SOA	`a0.pro.afilias-nst.info`hostmaster@donuts.email serial=1790519289

Same first word

Similar names

Previous names

Next names

DNS History

9 records (7 active, 2 former)

○NSfirstvds_ru2016-12-10 → 2017-08-19 · 4 obs

● 2016-12-10 14:51:28
● 2017-08-19 21:19:38
○ 2026-08-17 20:10:08
○ 2026-09-27 14:44:02

●NSns1.hosting.reg.ru2026-08-17 → 2026-09-27 · 3 obs

○ 2017-08-19 21:19:38
● 2026-08-17 20:10:08
● 2026-09-27 14:44:02

●NSns2.hosting.reg.ru2026-08-17 → 2026-09-27 · 3 obs

○ 2017-08-19 21:19:38
● 2026-08-17 20:10:08
● 2026-09-27 14:44:02

●NSserver172.hosting.reg.ru2026-08-17 → 2026-09-27 · 3 obs

○ 2017-08-19 21:19:38
● 2026-08-17 20:10:08
● 2026-09-27 14:44:02

●MXmx1.hosting.reg.ru2026-08-17 → 2026-09-27 · 2 obs

● 2026-08-17 20:10:08
● 2026-09-27 14:44:02

●MXmx2.hosting.reg.ru2026-08-17 → 2026-09-27 · 2 obs

● 2026-08-17 20:10:08
● 2026-09-27 14:44:02

●A2a00:f940:2:2:1:1:0:1722026-08-17 → 2026-09-27 · 3 obs

○ 2017-08-19 21:19:38
● 2026-08-17 20:10:08
● 2026-09-27 14:44:02

●A31.31.196.2142026-08-17 → 2026-09-27 · 3 obs

○ 2017-08-19 21:19:38
● 2026-08-17 20:10:08
● 2026-09-27 14:44:02

○A82.146.40.892016-12-10 → 2017-08-19 · 4 obs

● 2016-12-10 14:51:28
● 2017-08-19 21:19:38
○ 2026-08-17 20:10:08
○ 2026-09-27 14:44:02

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
pro	a0.pro.afilias-nst.info, d0.pro.afilias-nst.org, b2.pro.afilias-nst.org, b0.pro.afilias-nst.org...	12 records
visualdata.pro	ns2.hosting.reg.ru, ns1.hosting.reg.ru	-

✅ Authoritative Response

Server:31.31.194.245

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for visualdata.pro (unsigned zone)

⏱️ Timing

Total: 2189ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`31.31.196.214`
AAAA	1	`2a00:f940:2:2:1:1:0:172`
NS	2	`ns1.hosting.reg.ru, ns2.hosting.reg.ru`
MX	2	`mx2.hosting.reg.ru (pri: 20), mx1.hosting.reg.ru (pri: 10)`
TXT	1	`v=spf1 ip4:31.31.196.214 a mx include:_s`
SOA	1	`server172.hosting.reg.ru support.reg.ru`

📌 Glue Records Collected

Total: 12

Out-of-bailiwick: 12 (a0.pro.afilias-nst.info, a0.pro.afilias-nst.info, d0.pro.afilias-nst.org...)

Analysis

IP Addresses

visualdata.pro has two IP addresses: 31.31.196.214 and 2a00:f940:2:2:1:1:0:172

trufanovlaw.ru, xn--80aaecm0byanu.xn--p1ai, reahimed.com plus two other host names have IP numbers in common with visualdata.pro.

Name Servers

visualdata.pro carries NS records delegating to ns1.hosting.reg.ru, ns2.hosting.reg.ru and server172.hosting.reg.ru.

The name servers of visualdata.pro overlap at least partially with those of other domains — among them dropy-kukly-2.ru, eni.moscow, brus-doma.ru and two more.

These name servers commonly appear in delegations together with server256.hosting.reg.ru, server266.hosting.reg.ru, server268.hosting.reg.ru and 4 other.

Hosts with 14 IP addresses each:

ns1.hosting.reg.ru resolves to 31.31.194.245, 31.31.194.251 and 31.31.196.37 among others, with 11 other IP addresses in total.

ns2.hosting.reg.ru resolves to 31.31.194.244, 31.31.196.34 and 31.31.196.53 among others, with 11 other IP addresses in total.

Host names resolving to a single IP address:

The hostname server172.hosting.reg.ru resolves to 31.31.196.214.

Mail Servers

visualdata.pro uses two mail servers, mx1.hosting.reg.ru and mx2.hosting.reg.ru.

The mail server setup of visualdata.pro matches that of other domains such as 1uchebny.ru, vet-ritual-ptz.ru, sompec.ru and two others.

visualdata.pro has mail servers in common with other domains — germoizol.ru being one example.

mx1.hosting.reg.ru and mx2.hosting.reg.ru each point to two IP numbers — 31.31.194.240 and 31.31.194.241 — making both hosts identical in their DNS resolution.

mx1.hosting.reg.ru along with mx2.hosting.reg.ru each resolve to 31.31.194.240 IP addresses.

mx1.hosting.reg.ru along with mx2.hosting.reg.ru each resolve to 31.31.194.241 IP addresses.

visualdata.pro - dns.ninja

visualdata.pro

pro

Same first word

Similar names

Previous names

Next names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

IP Addresses

Name Servers

Mail Servers

`visualdata.pro`

`pro`