pin-code.ru - dns.ninja

`pin-code.ru`

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}
		A	176.99.13.13^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
		A	176.99.13.15^{🇷🇺 AS-REGRU176.99.13.0/24 Reg.Ru}
		A	176.99.13.17^{🇷🇺 AS-REGRU176.99.13.0/24 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	`ns1.agava.ru` ⚠️ Not in zone NS records
		A	2a00:f940:4::47^{🇷🇺 AS-REGRU2a00:f940:4::/48 Reg.Ru SRS Infrastructure Route}
			PTR	`ns1.reg.ru`
		A	194.58.117.11^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns1.reg.ru`
NS	`ns2.agava.ru` ⚠️ Not in zone NS records
		A	2a00:f940:5::190^{🇷🇺 AS-REGRU2a00:f940:5::/48 Reg.Ru SRS Infrastructure Route}
			PTR	`ns2.reg.ru`
		A	194.58.117.12^{🇷🇺 AS-REGRU194.58.117.0/24 Reg.Ru}
			PTR	`ns2.reg.ru`
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=_spf.yandex.net`
SOA	`ns1.reg.ru`hostmaster@ns1.reg.ru serial=1761224921

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

Same first word

pin-code.org.in

pin-code.com

pin-code.in

pin-code.de

pin-code.org

pin-code.by

pin-code.net

pin-code.ru

Similar names

dope-inc.com

edion-cp.com

dpo-nice.com

DNS History

20 records (4 active, 16 former)

○NSns.newdesign.ru2008-11-24 → 2008-11-24 · 3 obs

● 2008-11-24 00:45:38
○ 2015-05-29 17:59:08
○ 2026-07-05 21:20:14

●NSns1.agava.ru2026-03-17 → 2026-07-05 · 3 obs

○ 2017-01-06 09:03:30
● 2026-03-17 13:17:16
● 2026-07-05 21:20:14

●NSns1.reg.ru2017-01-06 → 2026-07-05 · 3 obs

○ 2016-07-04 07:48:22
● 2017-01-06 09:03:30
● 2026-07-05 21:20:14

○NSns1.timeweb.ru2015-05-29 → 2016-07-04 · 5 obs

○ 2008-11-24 00:45:38
● 2015-05-29 17:59:08
● 2016-07-04 07:48:22
○ 2017-01-06 09:03:30
○ 2026-07-05 21:20:14

●NSns2.agava.ru2026-03-17 → 2026-07-05 · 3 obs

○ 2017-01-06 09:03:30
● 2026-03-17 13:17:16
● 2026-07-05 21:20:14

○NSns2.reg.ru2017-01-06 → 2017-01-06 · 4 obs

○ 2016-07-04 07:48:22
● 2017-01-06 09:03:30
○ 2026-03-17 13:17:16
○ 2026-07-05 21:20:14

○NSns2.timeweb.ru2015-05-29 → 2016-07-04 · 5 obs

○ 2008-11-24 00:45:38
● 2015-05-29 17:59:08
● 2016-07-04 07:48:22
○ 2017-01-06 09:03:30
○ 2026-07-05 21:20:14

○NSns3.timeweb.org2015-05-29 → 2016-07-04 · 5 obs

○ 2008-11-24 00:45:38
● 2015-05-29 17:59:08
● 2016-07-04 07:48:22
○ 2017-01-06 09:03:30
○ 2026-07-05 21:20:14

○NSns4.timeweb.org2015-05-29 → 2016-07-04 · 5 obs

○ 2008-11-24 00:45:38
● 2015-05-29 17:59:08
● 2016-07-04 07:48:22
○ 2017-01-06 09:03:30
○ 2026-07-05 21:20:14

○NSns5.newdesign.ru2008-11-24 → 2008-11-24 · 3 obs

● 2008-11-24 00:45:38
○ 2015-05-29 17:59:08
○ 2026-07-05 21:20:14

○MXmx.pin-code.ru2008-11-24 → 2008-11-24 · 3 obs

● 2008-11-24 00:45:38
○ 2015-05-29 17:59:08
○ 2026-07-05 21:20:14

●MXmx.yandex.net2017-01-06 → 2026-07-05 · 3 obs

○ 2016-07-04 07:48:22
● 2017-01-06 09:03:30
● 2026-07-05 21:20:14

○MXmx.yandex.ru2015-05-29 → 2016-07-04 · 5 obs

○ 2008-11-24 00:45:38
● 2015-05-29 17:59:08
● 2016-07-04 07:48:22
○ 2017-01-06 09:03:30
○ 2026-07-05 21:20:14

○A176.57.216.1212015-05-29 → 2015-05-29 · 4 obs

○ 2008-11-24 00:45:38
● 2015-05-29 17:59:08
○ 2015-10-17 17:15:48
○ 2026-07-05 21:20:14

○A2a03:4900:0:6037:80:78:250:342017-01-06 → 2017-01-06 · 4 obs

○ 2016-07-04 07:48:22
● 2017-01-06 09:03:30
○ 2026-03-17 13:17:16
○ 2026-07-05 21:20:14

○A2a03:6f00:1::5c35:72aa2015-10-17 → 2016-07-04 · 5 obs

○ 2015-05-29 17:59:08
● 2015-10-17 17:15:48
● 2016-07-04 07:48:22
○ 2017-01-06 09:03:30
○ 2026-07-05 21:20:14

○A2a03:6f00:1::b039:d8792015-05-29 → 2015-05-29 · 4 obs

○ 2008-11-24 00:45:38
● 2015-05-29 17:59:08
○ 2015-10-17 17:15:48
○ 2026-07-05 21:20:14

○A80.78.250.342017-01-06 → 2017-01-06 · 4 obs

○ 2016-07-04 07:48:22
● 2017-01-06 09:03:30
○ 2026-03-17 13:17:16
○ 2026-07-05 21:20:14

○A89.111.189.1882008-11-24 → 2008-11-24 · 3 obs

● 2008-11-24 00:45:38
○ 2015-05-29 17:59:08
○ 2026-07-05 21:20:14

○A92.53.114.1702015-10-17 → 2016-07-04 · 5 obs

○ 2015-05-29 17:59:08
● 2015-10-17 17:15:48
● 2016-07-04 07:48:22
○ 2017-01-06 09:03:30
○ 2026-07-05 21:20:14

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
ru	d.dns.ripn.net, e.dns.ripn.net, b.dns.ripn.net, a.dns.ripn.net...	-
pin-code.ru	ns2.agava.ru, ns1.agava.ru	10 records

✅ Authoritative Response

Server:194.58.117.12

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for pin-code.ru (unsigned zone)

⏱️ Timing

Total: 1143ms | Queries: -

📄 Records

Type	Count	Sample Data
MX	1	`mx.yandex.net (pri: 10)`
TXT	1	`v=spf1 redirect=_spf.yandex.net`
SOA	1	`ns1.reg.ru hostmaster.ns1.reg.ru`

📌 Glue Records Collected

Total: 10

Out-of-bailiwick: 10 (ns2.agava.ru, ns2.agava.ru, ns2.agava.ru...)

Analysis

Name Servers

pin-code.ru is delegated to three name servers: ns1.agava.ru, ns2.agava.ru and ns1.reg.ru.

pin-code.ru has at least partial name server overlap with other domains, such as momag.ru, xn----dtbigfd5afcgoelef.xn--p1ai, coffeekiss.ru and two others.

It is common to find these name servers paired with the name servers ns2.reg.ru.

Hostnames that resolve to 10 IP addresses:

ns1.reg.ru resolves to 176.99.13.11, 176.99.13.13, 176.99.13.15 and 7 other IP addresses.

Hostnames that resolve to two IP addresses:

ns1.agava.ru points to 194.58.117.11 and 2a00:f940:4::47.

ns2.agava.ru points to 194.58.117.12 and 2a00:f940:5::190.

ns1.reg.ru and ns1.agava.ru are host names that each point to 194.58.117.11 IP addresses.

Mail Servers

Mail for pin-code.ru is handled by a single mail server, mx.yandex.net.

pin-code.ru uses an identical mail server configuration to several other domains — among them armaggan.com, holidayexpresstransfers.com, restalytica.ru and two more.

pin-code.ru has at least partial mail server overlap with other domains such as grizzluka.ru, www.diamond-box.ru, argitos.com and two more.

This set of mail servers commonly appears together with the mail servers mx1.timeweb.ru.

mx.yandex.net has two IP addresses: 77.88.21.249 and 2a02:6b8::311.