`crowdrepublic.com`

DNSSEC	⚠️ Not signed
A	81.177.25.206^{🇷🇺 RTCOMM-AS81.177.0.0/19 RTCOMM-RU}
		PTR	`mh2.webdesk.ru`
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	`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 ip4:123.123.123.123 include:_spf.yandex.ru ~all`
SOA	`ns1.yandexcloud.net`mx@cloud.yandex.net serial=1

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

Same first word

crowdrepublic.com

crowdrepublic.ru

DNS History

14 records (4 active, 10 former)

○NSns.crowdrepublic.com2015-06-25 → 2016-04-29 · 4 obs

● 2015-06-25 10:51:38
● 2016-04-29 17:40:02
○ 2017-01-30 22:09:10
○ 2026-04-03 06:00:10

○NSns.webdesk.ru2015-06-25 → 2016-04-29 · 4 obs

● 2015-06-25 10:51:38
● 2016-04-29 17:40:02
○ 2017-01-30 22:09:10
○ 2026-04-03 06:00:10

○NSns01.srvrsdns.co.uk2017-01-30 → 2017-01-30 · 4 obs

○ 2016-04-29 17:40:02
● 2017-01-30 22:09:10
○ 2026-02-28 00:58:12
○ 2026-04-03 06:00:10

○NSns01.srvrsdns.com2017-01-30 → 2017-01-30 · 4 obs

○ 2016-04-29 17:40:02
● 2017-01-30 22:09:10
○ 2026-02-28 00:58:12
○ 2026-04-03 06:00:10

○NSns01.srvrsdns.net2017-01-30 → 2017-01-30 · 4 obs

○ 2016-04-29 17:40:02
● 2017-01-30 22:09:10
○ 2026-02-28 00:58:12
○ 2026-04-03 06:00:10

○NSns01.srvrsdns.org2017-01-30 → 2017-01-30 · 4 obs

○ 2016-04-29 17:40:02
● 2017-01-30 22:09:10
○ 2026-02-28 00:58:12
○ 2026-04-03 06:00:10

○NSns1.hobbyworld.ru2015-06-25 → 2016-04-29 · 4 obs

● 2015-06-25 10:51:38
● 2016-04-29 17:40:02
○ 2017-01-30 22:09:10
○ 2026-04-03 06:00:10

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

○ 2017-01-30 22:09:10
● 2026-02-28 00:58:12
● 2026-04-03 06:00:10

○NSns2.hobbyworld.ru2015-06-25 → 2016-04-29 · 4 obs

● 2015-06-25 10:51:38
● 2016-04-29 17:40:02
○ 2017-01-30 22:09:10
○ 2026-04-03 06:00:10

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

○ 2017-01-30 22:09:10
● 2026-02-28 00:58:12
● 2026-04-03 06:00:10

○NSns3.webdesk.ru2015-06-25 → 2016-04-29 · 4 obs

● 2015-06-25 10:51:38
● 2016-04-29 17:40:02
○ 2017-01-30 22:09:10
○ 2026-04-03 06:00:10

●MXmx.yandex.net2017-01-30 → 2026-04-03 · 3 obs

○ 2016-04-29 17:40:02
● 2017-01-30 22:09:10
● 2026-04-03 06:00:10

○MXmx.yandex.ru2015-06-25 → 2016-04-29 · 4 obs

● 2015-06-25 10:51:38
● 2016-04-29 17:40:02
○ 2017-01-30 22:09:10
○ 2026-04-03 06:00:10

●A81.177.25.2062015-06-25 → 2026-04-03 · 2 obs

● 2015-06-25 10:51:38
● 2026-04-03 06:00:10

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	d.gtld-servers.net, k.gtld-servers.net, b.gtld-servers.net, i.gtld-servers.net...	-
crowdrepublic.com	ns1.yandexcloud.net, ns2.yandexcloud.net	-

✅ Authoritative Response

Server:84.201.189.229

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for crowdrepublic.com (unsigned zone)

⏱️ Timing

Total: 953ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`81.177.25.206`
NS	2	`ns1.yandexcloud.net, ns2.yandexcloud.net`
MX	1	`mx.yandex.net (pri: 10)`
TXT	1	`v=spf1 ip4:123.123.123.123 include:_spf.`
SOA	1	`ns1.yandexcloud.net mx.cloud.yandex.net`

Analysis

IP Addresses

crowdrepublic.com points to a single IP address: 81.177.25.206.

Other host names, such as igrokon.com and mh2.webdesk.ru, share IP numbers with crowdrepublic.com.

Name Servers

Two name servers ns1.yandexcloud.net and ns2.yandexcloud.net handle the delegation for crowdrepublic.com.

crowdrepublic.com shares the same name server setup as other domains, for example answerpro.ru, 5-gum.ru, avtoapp.online, solvers-estate.ru and ural-press.ru.

crowdrepublic.com at least partially shares name servers with other domains, for example komatsu.ru, avtoapp.ru and ptsonline.ru.

Host names with two IP numbers:

ns1.yandexcloud.net points to 2a0d:d6c1:0:1a::1b4 and 84.201.185.208.

ns2.yandexcloud.net points to 2a0d:d6c1:0:1a::2c9 and 84.201.189.229.

Mail Servers

The mx.yandex.net mail server handles crowdrepublic.com.

crowdrepublic.com shares the same mail server setup as other domains, including recool.by, eibach.ru, rost-crm.ru, wahkwang.com and altai-center.ru.

crowdrepublic.com shares at least partially some mail servers with other domains, for instance balli.az, varkan.ru, grainlab.ru, xn--b1afltjfde.xn--p1ai and alopatin.ru.

these mail servers are commonly used with mx.yandex.ru.

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

crowdrepublic.com - robtex.com