`npk-brizk.com`

DNSSEC	⚠️ Not signed
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=1738609769

`com`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.gtld-servers.net` ⭐
	NS	`b.gtld-servers.net`
	NS	`c.gtld-servers.net`
	NS	`d.gtld-servers.net`
	NS	`e.gtld-servers.net`
	NS	`f.gtld-servers.net`
	NS	`g.gtld-servers.net`
	NS	`h.gtld-servers.net`
	NS	`i.gtld-servers.net`
	NS	`j.gtld-servers.net`
	NS	`k.gtld-servers.net`
	NS	`l.gtld-servers.net`
	NS	`m.gtld-servers.net`
	SOA	`a.gtld-servers.net`nstld@verisign-grs.com serial=1776023592

Same first word

npk-brizk.com

DNS History

4 records (2 active, 2 former)

●NSns1.reg.ru2015-06-02 → 2026-04-12 · 2 obs

● 2015-06-02 00:43:34
● 2026-04-12 20:16:18

●NSns2.reg.ru2015-06-02 → 2026-04-12 · 2 obs

● 2015-06-02 00:43:34
● 2026-04-12 20:16:18

○A194.58.112.1732017-10-04 → 2017-10-04 · 3 obs

○ 2016-12-10 09:01:26
● 2017-10-04 04:23:06
○ 2026-04-12 20:16:18

○A31.31.204.592015-06-02 → 2016-12-10 · 4 obs

● 2015-06-02 00:43:34
● 2016-12-10 09:01:26
○ 2017-10-04 04:23:06
○ 2026-04-12 20:16:18

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
npk-brizk.com	ns1.reg.ru, ns2.reg.ru	-

✅ Authoritative Response

Server:176.99.13.11

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for npk-brizk.com (unsigned zone)

⏱️ Timing

Total: 927ms | Queries: -

📄 Records

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

Analysis

Name Servers

npk-brizk.com's delegation uses two name servers, ns1.reg.ru and ns2.reg.ru.

npk-brizk.com shares the same name server setup as other domains, for example stroitel-btsk.ru, enchi.ru, obrabotkazakaz.online, iv3.ru and new-tuva.info.

Host names with ten IP numbers:

ns1.reg.ru points to: 2a00:f940:9::1:1, 2a00:f940:9::2:1, 176.99.13.11, 176.99.13.13, 176.99.13.15, 176.99.13.17, 194.58.117.11, 194.58.117.13, 194.58.117.15 and 194.58.117.17.

ns2.reg.ru points to: 2a00:f940:9::1:2, 2a00:f940:9::2:2, 176.99.13.12, 176.99.13.14, 176.99.13.16, 176.99.13.18, 194.58.117.12, 194.58.117.14, 194.58.117.16 and 194.58.117.18.

npk-brizk.com - robtex.com

npk-brizk.com

com