`zaagtech.ru`

DNSSEC	⚠️ Not signed
A	45.130.41.250^{🇷🇺 BEGET-AS45.130.41.0/24 BEGET.RU}
		PTR	`ssl.bebop.beget.com`
NS	`ns1.beget.com` ⭐
		A	5.101.159.11^{🇷🇺 BEGET-AS5.101.159.0/24 Geo location BEGET.RU}
			PTR	`ns1.beget.com`
NS	`ns1.beget.pro`
		A	5.101.159.11^{🇷🇺 BEGET-AS5.101.159.0/24 Geo location BEGET.RU}
			PTR	`ns1.beget.com`
NS	`ns1.beget.ru` ⚠️ Not in parent delegation
		A	5.101.159.11^{🇷🇺 BEGET-AS5.101.159.0/24 Geo location BEGET.RU}
			PTR	`ns1.beget.com`
NS	`ns2.beget.com`
		A	185.50.27.12^{🇷🇺 BEGET-AS185.50.27.0/24 BEGET.RU}
			PTR	`ns2.beget.com`
NS	`ns2.beget.pro`
		A	185.50.27.12^{🇷🇺 BEGET-AS185.50.27.0/24 BEGET.RU}
			PTR	`ns2.beget.com`
NS	`ns2.beget.ru` ⚠️ Not in parent delegation
		A	185.50.27.12^{🇷🇺 BEGET-AS185.50.27.0/24 BEGET.RU}
			PTR	`ns2.beget.com`
MX	`mx.yandex.net` ⭐
		A	2a02:6b8::311^{🇷🇺 TELETECH2a02:6b8::/32 Yandex network}
			PTR	`mxfront.stable.qloud-b.yandex.net`
		A	77.88.21.249^{🇷🇺 TELETECH77.88.0.0/18 Yandex enterprise network}
			PTR	`mxfront.stable.qloud-b.yandex.net`
TXT	`v=spf1 redirect=beget.com`
SOA	`ns1.beget.com`hostmaster@beget.com serial=1751119354

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

Same first word

zaagtech.ru

DNS History

16 records (8 active, 8 former)

●NSns1.beget.com2026-03-17 → 2026-04-27 · 3 obs

○ 2019-03-20 10:08:10
● 2026-03-17 10:50:14
● 2026-04-27 18:28:44

●NSns1.beget.pro2026-03-17 → 2026-04-27 · 3 obs

○ 2019-03-20 10:08:10
● 2026-03-17 10:50:14
● 2026-04-27 18:28:44

●NSns1.beget.ru2026-03-17 → 2026-04-27 · 3 obs

○ 2019-03-20 10:08:10
● 2026-03-17 10:50:14
● 2026-04-27 18:28:44

○NSns1.sprinthost.ru2019-03-20 → 2019-03-20 · 4 obs

○ 2017-02-01 14:47:02
● 2019-03-20 10:08:10
○ 2026-03-17 10:50:14
○ 2026-04-27 18:28:44

●NSns2.beget.com2026-03-17 → 2026-04-27 · 3 obs

○ 2019-03-20 10:08:10
● 2026-03-17 10:50:14
● 2026-04-27 18:28:44

●NSns2.beget.pro2026-03-17 → 2026-04-27 · 3 obs

○ 2019-03-20 10:08:10
● 2026-03-17 10:50:14
● 2026-04-27 18:28:44

●NSns2.beget.ru2026-03-17 → 2026-04-27 · 3 obs

○ 2019-03-20 10:08:10
● 2026-03-17 10:50:14
● 2026-04-27 18:28:44

○NSns2.sprinthost.ru2019-03-20 → 2019-03-20 · 4 obs

○ 2017-02-01 14:47:02
● 2019-03-20 10:08:10
○ 2026-03-17 10:50:14
○ 2026-04-27 18:28:44

○NSstatuspage1.nic.ru2016-01-24 → 2017-02-01 · 4 obs

● 2016-01-24 05:05:56
● 2017-02-01 14:47:02
○ 2019-03-20 10:08:10
○ 2026-04-27 18:28:44

○NSstatuspage2.nic.ru2016-01-24 → 2017-02-01 · 4 obs

● 2016-01-24 05:05:56
● 2017-02-01 14:47:02
○ 2019-03-20 10:08:10
○ 2026-04-27 18:28:44

●MXmx.yandex.net2019-03-20 → 2026-04-27 · 3 obs

○ 2017-02-01 14:47:02
● 2019-03-20 10:08:10
● 2026-04-27 18:28:44

○MXnomail.nic.ru2016-05-07 → 2017-02-01 · 4 obs

● 2016-05-07 06:58:26
● 2017-02-01 14:47:02
○ 2019-03-20 10:08:10
○ 2026-04-27 18:28:44

○A109.70.26.372016-01-24 → 2017-02-01 · 4 obs

● 2016-01-24 05:05:56
● 2017-02-01 14:47:02
○ 2019-03-20 10:08:10
○ 2026-04-27 18:28:44

○A176.122.23.542019-03-20 → 2019-03-20 · 4 obs

○ 2017-02-01 14:47:02
● 2019-03-20 10:08:10
○ 2026-03-17 10:50:14
○ 2026-04-27 18:28:44

○A194.85.61.762016-01-24 → 2017-02-01 · 4 obs

● 2016-01-24 05:05:56
● 2017-02-01 14:47:02
○ 2019-03-20 10:08:10
○ 2026-04-27 18:28:44

●A45.130.41.2502026-03-17 → 2026-04-27 · 3 obs

○ 2019-03-20 10:08:10
● 2026-03-17 10:50:14
● 2026-04-27 18:28:44

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
ru	a.dns.ripn.net, d.dns.ripn.net, f.dns.ripn.net, b.dns.ripn.net...	-
zaagtech.ru	ns2.beget.pro, ns2.beget.com, ns1.beget.com, ns1.beget.pro	-

✅ Authoritative Response

Server:185.50.27.12

NS records: ns2.beget.pro, ns2.beget.com, ns1.beget.com, ns1.beget.pro

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for zaagtech.ru (unsigned zone)

⏱️ Timing

Total: 1215ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`45.130.41.250`
NS	6	`ns2.beget.ru, ns1.beget.ru...`
MX	1	`mx.yandex.net (pri: 10)`
TXT	1	`v=spf1 redirect=beget.com`
SOA	1	`ns1.beget.com hostmaster.beget.com`

Analysis

IP Addresses

zaagtech.ru points to a single IP address: 45.130.41.250.

Other host names such as narkologicheskaya-klinika-v-samare16.ru, narkologicheskaya-klinika-rostov-na-donu13.ru, vyvod-iz-zapoya-stavropol15.ru, narkolog-na-dom-moskva-1.ru and snyatie-lomki-narkolog11.ru share IPs with zaagtech.ru.

Name Servers

zaagtech.ru is delegated to six name servers: ns1.beget.com, ns2.beget.com, ns1.beget.pro, ns2.beget.pro, ns1.beget.ru and ns2.beget.ru.

zaagtech.ru at least partially shares name servers with other domains, for example thekurs.ru, courseplus.ru, rainman.ru, 101-radio.ru and tulamen.ru.

Host names with one IP number:

ns1.beget.com points to: 5.101.159.11.

ns2.beget.com points to: 185.50.27.12.

ns1.beget.pro points to: 5.101.159.11.

ns2.beget.pro points to: 185.50.27.12.

ns1.beget.ru points to: 5.101.159.11.

ns2.beget.ru points to: 185.50.27.12.

Host names pointing to 5.101.159.11: ns1.beget.com, ns1.beget.pro and ns1.beget.ru.

Host names pointing to 185.50.27.12: ns2.beget.com, ns2.beget.pro and ns2.beget.ru.

Mail Servers

The mx.yandex.net mail server handles zaagtech.ru.

zaagtech.ru shares the same mail server setup as other domains, including fivegifts.ru, rybar.ru, ap-shina.ru, olgawhite.ru and furlux.ru.

zaagtech.ru shares at least some mail servers with other domains, for instance oznammakine.com, propalasobaka.org and promacter.ru.

mx.yandex.net points to two IP numbers: 2a02:6b8::311 and 77.88.21.249.

zaagtech.ru - robtex.com

zaagtech.ru

ru

Same first word

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

Analysis

IP Addresses

Name Servers

Mail Servers

`zaagtech.ru`

`ru`