`faterkin.ru`

DNSSEC	⚠️ Not signed
A	109.172.7.175^{🇷🇺 RU-JSCIOT109.172.6.0/23}
		PTR	`faterkin.ru`
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=1770202269

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

PTR for

175.7.172.109.in-addr.arpa

Same first word

faterkin.ru

Similar names

DNS History

17 records (3 active, 14 former)

○NSns1.hosting.reg.ru2020-01-26 → 2020-01-26 · 4 obs

○ 2017-02-06 06:40:24
● 2020-01-26 00:21:22
○ 2026-03-22 13:11:40
○ 2026-04-14 18:45:46

○NSns1.hostmonster.com2015-06-15 → 2017-02-06 · 4 obs

● 2015-06-15 19:44:12
● 2017-02-06 06:40:24
○ 2020-01-26 00:21:22
○ 2026-04-14 18:45:46

●NSns1.reg.ru2026-03-22 → 2026-04-14 · 3 obs

○ 2020-01-26 00:21:22
● 2026-03-22 13:11:40
● 2026-04-14 18:45:46

○NSns2.hosting.reg.ru2020-01-26 → 2020-01-26 · 4 obs

○ 2017-02-06 06:40:24
● 2020-01-26 00:21:22
○ 2026-03-22 13:11:40
○ 2026-04-14 18:45:46

○NSns2.hostmonster.com2015-06-15 → 2017-02-06 · 4 obs

● 2015-06-15 19:44:12
● 2017-02-06 06:40:24
○ 2020-01-26 00:21:22
○ 2026-04-14 18:45:46

●NSns2.reg.ru2026-03-22 → 2026-04-14 · 3 obs

○ 2020-01-26 00:21:22
● 2026-03-22 13:11:40
● 2026-04-14 18:45:46

○NSserver22.hosting.reg.ru2020-01-26 → 2020-01-26 · 4 obs

○ 2017-02-06 06:40:24
● 2020-01-26 00:21:22
○ 2026-03-22 13:11:40
○ 2026-04-14 18:45:46

○MXalt1.aspmx.l.google.com2015-06-15 → 2017-02-06 · 4 obs

● 2015-06-15 19:44:12
● 2017-02-06 06:40:24
○ 2020-01-26 00:21:22
○ 2026-04-14 18:45:46

○MXalt2.aspmx.l.google.com2015-06-15 → 2017-02-06 · 4 obs

● 2015-06-15 19:44:12
● 2017-02-06 06:40:24
○ 2020-01-26 00:21:22
○ 2026-04-14 18:45:46

○MXaspmx.l.google.com2015-06-15 → 2017-02-06 · 4 obs

● 2015-06-15 19:44:12
● 2017-02-06 06:40:24
○ 2020-01-26 00:21:22
○ 2026-04-14 18:45:46

○MXaspmx2.googlemail.com2015-06-15 → 2017-02-06 · 4 obs

● 2015-06-15 19:44:12
● 2017-02-06 06:40:24
○ 2020-01-26 00:21:22
○ 2026-04-14 18:45:46

○MXaspmx3.googlemail.com2015-06-15 → 2017-02-06 · 4 obs

● 2015-06-15 19:44:12
● 2017-02-06 06:40:24
○ 2020-01-26 00:21:22
○ 2026-04-14 18:45:46

○MXmx1.hosting.reg.ru2020-01-26 → 2020-01-26 · 4 obs

○ 2017-02-06 06:40:24
● 2020-01-26 00:21:22
○ 2026-03-22 13:11:40
○ 2026-04-14 18:45:46

○MXmx2.hosting.reg.ru2020-01-26 → 2020-01-26 · 4 obs

○ 2017-02-06 06:40:24
● 2020-01-26 00:21:22
○ 2026-03-22 13:11:40
○ 2026-04-14 18:45:46

●A109.172.7.1752026-03-22 → 2026-04-14 · 3 obs

○ 2020-01-26 00:21:22
● 2026-03-22 13:11:40
● 2026-04-14 18:45:46

○A31.31.198.1242020-01-26 → 2020-01-26 · 4 obs

○ 2017-02-06 06:40:24
● 2020-01-26 00:21:22
○ 2026-03-22 13:11:40
○ 2026-04-14 18:45:46

○A74.220.215.2212015-06-15 → 2017-02-06 · 4 obs

● 2015-06-15 19:44:12
● 2017-02-06 06:40:24
○ 2020-01-26 00:21:22
○ 2026-04-14 18:45:46

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
ru	d.dns.ripn.net, b.dns.ripn.net, e.dns.ripn.net, f.dns.ripn.net...	-
faterkin.ru	ns2.reg.ru, ns1.reg.ru	20 records

✅ Authoritative Response

Server:176.99.13.11

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for faterkin.ru (unsigned zone)

⏱️ Timing

Total: 873ms | Queries: -

📄 Records

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

📌 Glue Records Collected

Total: 20

Out-of-bailiwick: 20 (ns2.reg.ru, ns2.reg.ru, ns2.reg.ru...)

Analysis

IP Addresses

faterkin.ru maps to IP address 109.172.7.175.

Other host names, for instance bistrodenegka.ru, www.runevolution.ru, 24run.ru, bruder-toys.ru and pochtamoroza.ru share IP numbers with faterkin.ru.

Name Servers

Two name servers ns1.reg.ru and ns2.reg.ru are delegated to faterkin.ru.

faterkin.ru uses the same name server configuration as other domains, such as safas.ru, enku.ru, ta-tm.com, idealsoft.ru and fm-marketplace.ru.

Host names with ten IP numbers:

The host name 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.

The host name 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.

faterkin.ru - robtex.com

faterkin.ru

ru

PTR for

Same first word

Similar names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

IP Addresses

Name Servers

`faterkin.ru`

`ru`