toconnect.ru - dns.ninja

`toconnect.ru`

DNSSEC	⚠️ Not signed
NS	`ns1.snparking.ru` ⭐ ⚠️ Not in parent delegation
		A	37.221.193.103^{🇩🇪 netcup-AS37.221.192.0/22}
			PTR	`v22016063652435391.goodsrv.de`
		A	194.63.142.195^{🇷🇺 I-SERVERS-NORTH-EU194.63.142.0/24}
			PTR	`ns1.snparking.ru`
NS	`ns2.snparking.ru` ⚠️ Not in parent delegation
		A	5.45.106.252^{🇩🇪 netcup-AS5.45.104.0/22}
			PTR	`v22016113652440052.goodsrv.de`
		A	62.122.170.168^{🇺🇸 SERVEREL-AS62.122.168.0/21}
			PTR	`62.122.170.168.serverel.net`
NS	`ns3.domains.ru` ⚠️ Not in zone NS records
		A	37.221.193.103^{🇩🇪 netcup-AS37.221.192.0/22}
			PTR	`v22016063652435391.goodsrv.de`
		A	194.63.142.195^{🇷🇺 I-SERVERS-NORTH-EU194.63.142.0/24}
			PTR	`ns1.snparking.ru`
NS	`ns4.domains.ru` ⚠️ Not in zone NS records
		A	5.45.106.252^{🇩🇪 netcup-AS5.45.104.0/22}
			PTR	`v22016113652440052.goodsrv.de`
		A	62.122.170.168^{🇺🇸 SERVEREL-AS62.122.168.0/21}
			PTR	`62.122.170.168.serverel.net`
SOA	`ns1.snparking.ru`hostmaster@toconnect.ru 2022-03-30 #58

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

Same first word

toconnect.eu

toconnect.net

toconnect.co.uk

toconnect.ink

toconnect.ch

toconnect.info

toconnect.nl

toconnect.com

toconnect.ru

Similar names

DNS History

15 records (4 active, 11 former)

●NSns1.snparking.ru2017-01-09 → 2026-08-13 · 6 obs

○ 2016-04-30 12:04:28
● 2017-01-09 17:34:38
● 2020-01-14 01:31:16
○ 2026-02-27 17:24:42
● 2026-03-24 11:30:42
● 2026-08-13 07:37:20

●NSns2.snparking.ru2017-01-09 → 2026-08-13 · 11 obs

○ 2016-04-30 12:04:28
● 2017-01-09 17:34:38
● 2020-01-14 01:31:16
○ 2026-02-27 17:24:42
● 2026-03-24 11:30:42
● 2026-05-09 01:12:22
○ 2026-06-22 18:30:10
● 2026-07-05 06:28:26
○ 2026-08-06 01:33:52
● 2026-08-13 07:37:18
● 2026-08-13 07:37:20

●NSns3.domains.ru2026-05-09 → 2026-08-13 · 3 obs

○ 2026-03-31 20:35:34
● 2026-05-09 01:12:22
● 2026-08-13 07:37:20

○NSns3.salenames.ru2015-07-06 → 2026-03-31 · 8 obs

● 2015-07-06 19:15:22
● 2016-04-30 12:04:28
○ 2017-01-09 17:34:38
○ 2026-02-27 17:24:42
● 2026-03-24 11:30:42
● 2026-03-31 20:35:34
○ 2026-05-09 01:12:22
○ 2026-08-13 07:37:20

●NSns4.domains.ru2026-05-09 → 2026-08-13 · 3 obs

○ 2026-03-31 20:35:34
● 2026-05-09 01:12:22
● 2026-08-13 07:37:20

○NSns4.salenames.ru2015-07-06 → 2026-03-31 · 8 obs

● 2015-07-06 19:15:22
● 2016-04-30 12:04:28
○ 2017-01-09 17:34:38
○ 2026-02-27 17:24:42
● 2026-03-24 11:30:42
● 2026-03-31 20:35:34
○ 2026-05-09 01:12:22
○ 2026-08-13 07:37:20

○NSsnparking.com2017-01-09 → 2017-01-09 · 4 obs

○ 2016-04-30 12:04:28
● 2017-01-09 17:34:38
○ 2020-01-14 01:31:16
○ 2026-08-13 07:37:20

○MX148.240.4.322015-07-06 → 2015-07-06 · 3 obs

● 2015-07-06 19:15:22
○ 2015-12-08 22:59:40
○ 2026-08-13 07:37:20

○MXmx3.snbox.ru2020-01-14 → 2020-01-14 · 4 obs

○ 2017-01-09 17:34:38
● 2020-01-14 01:31:16
○ 2026-02-27 17:24:42
○ 2026-08-13 07:37:20

○MXvoid.blackhole.mx2015-12-08 → 2026-05-09 · 10 obs

○ 2015-07-06 19:15:22
● 2015-12-08 22:59:40
● 2016-04-30 12:04:28
○ 2017-01-09 17:34:38
○ 2026-02-27 17:24:42
● 2026-03-24 11:30:42
○ 2026-03-31 20:35:34
● 2026-05-09 01:12:22
○ 2026-08-06 01:33:52
○ 2026-08-13 07:37:20

○A109.206.190.542015-12-08 → 2015-12-08 · 4 obs

○ 2015-07-06 19:15:22
● 2015-12-08 22:59:40
○ 2016-04-30 12:04:28
○ 2026-08-13 07:37:20

○A52.50.65.322020-01-14 → 2020-01-14 · 4 obs

○ 2017-01-09 17:34:38
● 2020-01-14 01:31:16
○ 2026-02-27 17:24:42
○ 2026-08-13 07:37:20

○A62.122.170.1712026-03-24 → 2026-07-05 · 8 obs

○ 2026-02-27 17:24:42
● 2026-03-24 11:30:42
○ 2026-03-31 20:35:34
● 2026-05-09 01:12:22
○ 2026-06-22 18:30:10
● 2026-07-05 06:28:26
○ 2026-08-06 01:33:52
○ 2026-08-13 07:37:20

○A91.195.240.1352017-01-09 → 2017-01-09 · 4 obs

○ 2016-04-30 12:04:28
● 2017-01-09 17:34:38
○ 2020-01-14 01:31:16
○ 2026-08-13 07:37:20

○A91.195.241.862015-07-06 → 2016-04-30 · 5 obs

● 2015-07-06 19:15:22
○ 2015-12-08 22:59:40
● 2016-04-30 12:04:28
○ 2017-01-09 17:34:38
○ 2026-08-13 07:37:20

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
ru	f.dns.ripn.net, c.tld-servers.ru, a.dns.ripn.net, b.dns.ripn.net...	-
toconnect.ru	ns3.domains.ru, ns4.domains.ru	-

✅ Authoritative Response

Server:62.122.170.168

NS records: ns3.domains.ru, ns4.domains.ru

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for toconnect.ru (unsigned zone)

⏱️ Timing

Total: 905ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`ns1.snparking.ru, ns2.snparking.ru`
MX	1	`void.blackhole.mx (pri: 0)`
SOA	1	`ns1.snparking.ru hostmaster.toconnect.ru`

Analysis

Name Servers

Four name servers handle the delegation for toconnect.ru: ns3.domains.ru, ns4.domains.ru, ns1.snparking.ru and ns2.snparking.ru.

There is at least partial name server overlap between toconnect.ru and other domains — akof.ru, acrf.ru, tektribe.ru and two more among them.

These name servers regularly appear alongside ns2.privateperson.ru, ns1.privateperson.ru, ns3.salenames.ru and 5 other name servers in NS record sets.

The four hosts ns3.domains.ru, ns4.domains.ru, ns1.snparking.ru and ns2.snparking.ru each point to two IP numbers. ns3.domains.ru directs to 37.221.193.103 and 194.63.142.195; ns4.domains.ru directs to 5.45.106.252 and 62.122.170.168; ns1.snparking.ru directs to 37.221.193.103 and 194.63.142.195; ns2.snparking.ru directs to 5.45.106.252 and 62.122.170.168.

ns3.domains.ru and ns1.snparking.ru each have 37.221.193.103 IP addresses.

ns3.domains.ru and ns1.snparking.ru each have 194.63.142.195 IP addresses.

ns4.domains.ru and ns2.snparking.ru each have 5.45.106.252 IP addresses.

ns4.domains.ru and ns2.snparking.ru each have 62.122.170.168 IP addresses.