`vpnconnection.tech`

DNSSEC	⚠️ Not signed
NS	`ns1.timeweb.ru` ⭐
		A	2a03:6f04:dead:bee::1^{🇷🇺 TimeWeb-AS2a03:6f00::/29}
		A	85.193.93.93^{🇵🇱 TimeWeb-AS85.193.93.0/24}
			PTR	`ns1.timeweb.ru`
NS	`ns2.timeweb.ru`
		A	2a03:6f04:dead:bee::2^{🇷🇺 TimeWeb-AS2a03:6f00::/29}
		A	85.193.93.85^{🇵🇱 TimeWeb-AS85.193.93.0/24}
			PTR	`ns2.timeweb.ru`
NS	`ns3.timeweb.org`
		A	2a03:6f07:4::2^{🇷🇺 TimeWeb-AS2a03:6f00::/29}
		A	217.78.234.130^{🇷🇺 TimeWeb-AS217.78.234.0/24}
NS	`ns4.timeweb.org`
		A	2a00:65e0:6:5:232a::2^{🇷🇺 RETNRU-SPB-AS2a00:65e0::/32 CJSC "RetnNet"}
		A	139.45.249.139^{🇷🇺 RETNRU-SPB-AS139.45.248.0/21 RETN-SPB}
			PTR	`gw-139.45.249.139-rt1.km.spb.retn.ru`
MX	`mx1.timeweb.ru` ⭐
		A	2a03:6f00:3::5c35:742f^{🇷🇺 TimeWeb-AS2a03:6f00:3::/48 TIMEWEB-v6-48-3}
			PTR	`mx1.timeweb.ru`
		A	92.53.116.47^{🇷🇺 TimeWeb-AS92.53.116.0/24}
			PTR	`mx1.timeweb.ru`
MX	`mx2.timeweb.ru`⁽²⁰⁾
		A	2a03:6f00:3::5c35:7433^{🇷🇺 TimeWeb-AS2a03:6f00:3::/48 TIMEWEB-v6-48-3}
			PTR	`mx2.timeweb.ru`
		A	92.53.116.51^{🇷🇺 TimeWeb-AS92.53.116.0/24}
			PTR	`mx2.timeweb.ru`
TXT	`v=spf1 include:_spf.timeweb.ru ~all`
SOA	`ns1.timeweb.ru`dns@timeweb.ru serial=42

`tech`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns01.trs-dns.com` ⭐
	NS	`ns.trs-dns.com`
	NS	`ns01.trs-dns.net`
	NS	`ns10.trs-dns.info`
	NS	`ns10.trs-dns.org`
	SOA	`ns.trs-dns.com`trs-ops@tucows.com serial=1785932638

Same first word

vpnconnection.tech

vpnconnection.help

Similar names

connectionvpn.com

DNS History

6 records (6 active, 0 former)

●NSns1.timeweb.ru2026-05-25 → 2026-08-05 · 2 obs

● 2026-05-25 18:47:24
● 2026-08-05 12:26:32

●NSns2.timeweb.ru2026-05-25 → 2026-08-05 · 2 obs

● 2026-05-25 18:47:24
● 2026-08-05 12:26:32

●NSns3.timeweb.org2026-05-25 → 2026-08-05 · 2 obs

● 2026-05-25 18:47:24
● 2026-08-05 12:26:32

●NSns4.timeweb.org2026-05-25 → 2026-08-05 · 2 obs

● 2026-05-25 18:47:24
● 2026-08-05 12:26:32

●MXmx1.timeweb.ru2026-05-25 → 2026-08-05 · 2 obs

● 2026-05-25 18:47:24
● 2026-08-05 12:26:32

●MXmx2.timeweb.ru2026-05-25 → 2026-08-05 · 2 obs

● 2026-05-25 18:47:24
● 2026-08-05 12:26:32

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
tech	ns01.trs-dns.com, ns10.trs-dns.org, ns10.trs-dns.info, ns01.trs-dns.net	-
vpnconnection.tech	ns2.timeweb.ru, ns3.timeweb.org, ns4.timeweb.org, ns1.timeweb.ru	-

✅ Authoritative Response

Server:85.193.93.85

NS records: ns2.timeweb.ru, ns3.timeweb.org, ns4.timeweb.org, ns1.timeweb.ru

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for vpnconnection.tech (unsigned zone)

⏱️ Timing

Total: 3775ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	4	`ns1.timeweb.ru, ns4.timeweb.org...`
MX	2	`mx2.timeweb.ru (pri: 20), mx1.timeweb.ru (pri: 10)`
TXT	1	`v=spf1 include:_spf.timeweb.ru ~all`
SOA	1	`ns1.timeweb.ru dns.timeweb.ru`

Analysis

Name Servers

The domain vpnconnection.tech is delegated to these four name servers: ns3.timeweb.org, ns4.timeweb.org, ns1.timeweb.ru and ns2.timeweb.ru.

vpnconnection.tech has at least partial name server overlap with other domains, such as orasplast.ru, linekom.ru, karwing.ru and two others.

ns3.timeweb.org, ns4.timeweb.org, ns1.timeweb.ru and ns2.timeweb.ru all point to exactly two IP numbers each: ns3.timeweb.org → 217.78.234.130 and 2a03:6f07:4::2; ns4.timeweb.org → 139.45.249.139 and 2a00:65e0:6:5:232a::2; ns1.timeweb.ru → 85.193.93.93 and 2a03:6f04:dead:bee::1; ns2.timeweb.ru → 85.193.93.85 and 2a03:6f04:dead:bee::2.

Mail Servers

The MX records for vpnconnection.tech point to two mail servers: mx1.timeweb.ru and mx2.timeweb.ru.

vpnconnection.tech has the same mail server arrangement as a number of other domains, for example live-site.ru, worldminecraft.ru, mts-cdn.ru and two more.

At least some of vpnconnection.tech's mail servers are shared with other domains, among them t-vid.ru, www.xekler.ru, myrgc.ru and www.vashvaz.ru.

Each of the two host names carries two IP addresses: mx1.timeweb.ru points to 92.53.116.47 and 2a03:6f00:3::5c35:742f, and mx2.timeweb.ru points to 92.53.116.51 and 2a03:6f00:3::5c35:7433.

vpnconnection.tech - robtex.com