`idcollection.ru`

DNSSEC	⚠️ Not signed
A	51.250.112.214^{🇷🇺 YandexCloud51.250.112.0/21}
		PTR	`other.fqdn.zone-1932073899089120398.dnstest.test`
NS	`ns1.yandexcloud.net` ⭐
		A	2a0d:d6c1:0:1a::1b4^{🇷🇺 YandexCloud2a0d:d6c1::/32}
			PTR	`ns1.yandexcloud.net`
		A	84.201.185.208^{🇷🇺 YandexCloud84.201.184.0/22 Yandex Cloud}
			PTR	`ns1.yandexcloud.net`
NS	`ns2.yandexcloud.net`
		A	2a0d:d6c1:0:1a::2c9^{🇷🇺 YandexCloud2a0d:d6c1::/32}
			PTR	`ns2.yandexcloud.net`
		A	84.201.189.229^{🇷🇺 YandexCloud84.201.188.0/23 Yandex Cloud}
			PTR	`ns2.yandexcloud.net`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c29::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadum-in-f26.1e100.net`
		A	192.178.155.27^{🇺🇸 Google192.178.155.0/24}
			PTR	`yuiadrs-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`google-site-verification=hV5YNVM1yecYtduCyB5wllonhD_9-JzYtZzvW5rtJNM`
TXT	`spf2.0/mfrom,pra include:senderid.unisender.com ~all`
TXT	`facebook-domain-verification=36yt8apzafqjw6nj4t8s2wcxvewl8k`
TXT	`mailru-verification: af9947483db036b3`
TXT	`google-site-verification=dKiW7BFzxcYdsWZawd-x1_MNnMKEVme5EFcEzwQXyzY`
TXT	`google-site-verification=KSpgI-rwr4dFJfVigK5Ypf295i5DXQBdLjc-s4LJKuw`
TXT	`mailru-verification: 88d2585346bd7ff3`
TXT	`v=spf1 a mx include:_spf.google.com ip4:79.174.14.173 ip4:136.243.74.77 ip4:8...`
SOA	`ns1.yandexcloud.net`mx@cloud.yandex.net serial=1

`ru`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.dns.ripn.net` ⭐
	NS	`b.dns.ripn.net`
	NS	`c.tld-servers.ru`
	NS	`d.dns.ripn.net`
	NS	`e.dns.ripn.net`
	NS	`f.dns.ripn.net`
	SOA	`a.dns.ripn.net`hostmaster@ripn.net serial=4069867

Same first word

idcollection.ru

Similar names

toledoclinic.com

DNS History

21 records (8 active, 13 former)

○NSns.masterhost.ru2015-08-12 → 2017-05-20 · 4 obs

● 2015-08-12 01:56:12
● 2017-05-20 05:45:18
○ 2026-02-28 17:26:52
○ 2026-08-04 18:05:12

○NSns1.masterhost.ru2015-08-12 → 2017-05-20 · 4 obs

● 2015-08-12 01:56:12
● 2017-05-20 05:45:18
○ 2026-02-28 17:26:52
○ 2026-08-04 18:05:12

●NSns1.yandexcloud.net2026-02-28 → 2026-08-04 · 3 obs

○ 2017-05-20 05:45:18
● 2026-02-28 17:26:52
● 2026-08-04 18:05:12

○NSns2.masterhost.ru2015-08-12 → 2017-05-20 · 4 obs

● 2015-08-12 01:56:12
● 2017-05-20 05:45:18
○ 2026-02-28 17:26:52
○ 2026-08-04 18:05:12

●NSns2.yandexcloud.net2026-02-28 → 2026-08-04 · 3 obs

○ 2017-05-20 05:45:18
● 2026-02-28 17:26:52
● 2026-08-04 18:05:12

●MXalt1.aspmx.l.google.com2015-08-12 → 2026-08-04 · 2 obs

● 2015-08-12 01:56:12
● 2026-08-04 18:05:12

●MXalt2.aspmx.l.google.com2015-08-12 → 2026-08-04 · 2 obs

● 2015-08-12 01:56:12
● 2026-08-04 18:05:12

●MXalt3.aspmx.l.google.com2015-08-12 → 2026-08-04 · 2 obs

● 2015-08-12 01:56:12
● 2026-08-04 18:05:12

●MXalt4.aspmx.l.google.com2015-08-12 → 2026-08-04 · 2 obs

● 2015-08-12 01:56:12
● 2026-08-04 18:05:12

●MXaspmx.l.google.com2015-08-12 → 2026-08-04 · 2 obs

● 2015-08-12 01:56:12
● 2026-08-04 18:05:12

○A136.243.74.772015-12-12 → 2016-03-06 · 5 obs

○ 2015-08-12 01:56:12
● 2015-12-12 02:05:06
● 2016-03-06 19:01:00
○ 2016-10-01 22:24:10
○ 2026-08-04 18:05:12

○A138.201.127.2282016-10-01 → 2017-05-20 · 5 obs

○ 2016-03-06 19:01:00
● 2016-10-01 22:24:10
● 2017-05-20 05:45:18
○ 2026-02-28 17:26:52
○ 2026-08-04 18:05:12

○A2a00:15f8:a000:5:1:11:1:18042015-08-12 → 2015-08-12 · 3 obs

● 2015-08-12 01:56:12
○ 2015-12-12 02:05:06
○ 2026-08-04 18:05:12

○A2a00:15f8:a000:5:1:12:1:18042015-08-12 → 2015-08-12 · 3 obs

● 2015-08-12 01:56:12
○ 2015-12-12 02:05:06
○ 2026-08-04 18:05:12

○A2a00:15f8:a000:5:1:13:1:18042015-08-12 → 2015-08-12 · 3 obs

● 2015-08-12 01:56:12
○ 2015-12-12 02:05:06
○ 2026-08-04 18:05:12

○A2a00:15f8:a000:5:1:14:1:18042015-08-12 → 2015-08-12 · 3 obs

● 2015-08-12 01:56:12
○ 2015-12-12 02:05:06
○ 2026-08-04 18:05:12

●A51.250.112.2142026-02-28 → 2026-08-04 · 3 obs

○ 2017-05-20 05:45:18
● 2026-02-28 17:26:52
● 2026-08-04 18:05:12

○A90.156.201.152015-08-12 → 2015-08-12 · 3 obs

● 2015-08-12 01:56:12
○ 2015-12-12 02:05:06
○ 2026-08-04 18:05:12

○A90.156.201.342015-08-12 → 2015-08-12 · 3 obs

● 2015-08-12 01:56:12
○ 2015-12-12 02:05:06
○ 2026-08-04 18:05:12

○A90.156.201.462015-08-12 → 2015-08-12 · 3 obs

● 2015-08-12 01:56:12
○ 2015-12-12 02:05:06
○ 2026-08-04 18:05:12

○A90.156.201.842015-08-12 → 2015-08-12 · 3 obs

● 2015-08-12 01:56:12
○ 2015-12-12 02:05:06
○ 2026-08-04 18:05:12

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
ru	a.dns.ripn.net, b.dns.ripn.net, d.dns.ripn.net, e.dns.ripn.net...	-
idcollection.ru	ns2.yandexcloud.net, ns1.yandexcloud.net	-

✅ Authoritative Response

Server:84.201.185.208

NS records: ns2.yandexcloud.net, ns1.yandexcloud.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for idcollection.ru (unsigned zone)

⏱️ Timing

Total: 1572ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`51.250.112.214`
NS	2	`ns1.yandexcloud.net, ns2.yandexcloud.net`
MX	5	`alt3.aspmx.l.google.com (pri: 10), alt2.aspmx.l.google.com (pri: 5)...`
TXT	8	`google-site-verification=hV5YNVM1yecYtdu, spf2.0/mfrom,pra include:senderid.unisen...`
SOA	1	`ns1.yandexcloud.net mx.cloud.yandex.net`

Analysis

IP Addresses

idcollection.ru points to a single IP number: 51.250.112.214.

Name Servers

idcollection.ru has two authoritative name servers — ns1.yandexcloud.net and ns2.yandexcloud.net.

idcollection.ru shares its name server setup with other domains, including proptech.ru, ilyang.ru, udex.expert and two others.

idcollection.ru has some name servers in common with other domains such as fostur.ru, gwe.ru and renlife.com

Both ns1.yandexcloud.net and ns2.yandexcloud.net have two IP addresses each. ns1.yandexcloud.net resolves to 84.201.185.208 and 2a0d:d6c1:0:1a::1b4; ns2.yandexcloud.net resolves to 84.201.189.229 and 2a0d:d6c1:0:1a::2c9.

Mail Servers

Five mail servers handle idcollection.ru: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

idcollection.ru shares mail servers — at least in part — with other domains, including impossiblelabs.io, omninotary.com, spiderpig.me and two others.

These mail servers are frequently used alongside mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 other.

Host names with two IP numbers:

aspmx.l.google.com resolves to 192.178.155.27 and 2607:f8b0:4004:c29::1a.

alt1.aspmx.l.google.com resolves to 108.177.123.26 and 2800:3f0:4003:c0f::1a.

alt2.aspmx.l.google.com resolves to 172.253.116.26 and 2a00:1450:400b:c02::1b.

alt3.aspmx.l.google.com resolves to 192.178.223.26 and 2a00:1450:4009:c0f::1b.

alt4.aspmx.l.google.com resolves to 172.253.157.27 and 2a00:1450:400c:c23::1b.