`secureconnect.pro`

DNSSEC	⚠️ Not signed
A	212.108.82.186^{🇬🇧 HOSTKEY-AS212.108.82.0/24}
		PTR	`www.secureconnect.pro`
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`
SOA	`ns1.reg.ru`hostmaster@ns1.reg.ru serial=1780727612

`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=1786109153

⚠️ On DNS blocklist: tif

Same first word

Similar names

connectsecure.info

connectsecure.com

cereusconnect.com

connectsecure.me

connectsecure.net

DNS History

3 records (3 active, 0 former)

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

● 2026-07-26 23:49:00
● 2026-08-07 13:38:46

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

● 2026-07-26 23:49:00
● 2026-08-07 13:38:46

●A212.108.82.1862026-07-26 → 2026-08-07 · 2 obs

● 2026-07-26 23:49:00
● 2026-08-07 13:38:46

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
pro	a0.pro.afilias-nst.info, a2.pro.afilias-nst.info, b0.pro.afilias-nst.org, b2.pro.afilias-nst.org...	-
secureconnect.pro	ns2.reg.ru, ns1.reg.ru	-

✅ Authoritative Response

Server:176.99.13.11

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for secureconnect.pro (unsigned zone)

⏱️ Timing

Total: 766ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`212.108.82.186`
NS	2	`ns1.reg.ru, ns2.reg.ru`
SOA	1	`ns1.reg.ru hostmaster.ns1.reg.ru`

Analysis

IP Addresses

secureconnect.pro directs to one IP number, which is 212.108.82.186.

Name Servers

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

secureconnect.pro has the same name server delegation as a number of other domains, such as gsmart.info, sokolenko.ru, prodano.pro 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.

secureconnect.pro - robtex.com