`projectchiefs.com`

DNSSEC	⚠️ Not signed
A	3.66.162.18^{🇩🇪 Amazon3.64.0.0/12 EC2 FRA Prefix}
		PTR	`ec2-3-66-162-18.eu-central-1.compute.amazonaws.com`
NS	`dns1.yandex.net` ⭐
		A	2a02:6b8::213^{🇷🇺 TELETECH2a02:6b8::/32 Yandex network}
			PTR	`dns1.yandex.net`
		A	213.180.204.213^{🇷🇺 TELETECH213.180.192.0/19 Yandex network}
			PTR	`dns1.yandex.net`
NS	`dns2.yandex.net`
		A	2a02:6b8:0:1::213^{🇷🇺 TELETECH2a02:6b8::/32 Yandex network}
			PTR	`dns2.yandex.net`
		A	93.158.134.213^{🇷🇺 TELETECH93.158.128.0/18 Yandex enterprise network}
			PTR	`dns2.yandex.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 redirect=_spf.yandex.net`
TXT	`google-site-verification=cw3xjic5B619aXxuAJIcNEKeozxt4lysiEa1ls7PaZs`
SOA	`dns1.yandex.net`dns-hosting@yandex.ru serial=14

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

Same first word

projectchiefs.com

DNS History

19 records (4 active, 15 former)

●NSdns1.yandex.net2016-07-04 → 2026-04-03 · 5 obs

○ 2016-03-12 07:30:00
● 2016-07-04 21:39:26
○ 2017-02-20 02:33:34
● 2020-01-18 12:38:38
● 2026-04-03 12:24:24

○NSdns10.pointhq.com2015-08-05 → 2016-03-12 · 4 obs

● 2015-08-05 19:26:00
● 2016-03-12 07:30:00
○ 2016-07-04 21:39:26
○ 2026-04-03 12:24:24

○NSdns11.pointhq.com2015-08-05 → 2016-03-12 · 4 obs

● 2015-08-05 19:26:00
● 2016-03-12 07:30:00
○ 2016-07-04 21:39:26
○ 2026-04-03 12:24:24

●NSdns2.yandex.net2016-07-04 → 2026-04-03 · 5 obs

○ 2016-03-12 07:30:00
● 2016-07-04 21:39:26
○ 2017-02-20 02:33:34
● 2020-01-18 12:38:38
● 2026-04-03 12:24:24

○NSdns4.pointhq.com2015-08-05 → 2016-03-12 · 4 obs

● 2015-08-05 19:26:00
● 2016-03-12 07:30:00
○ 2016-07-04 21:39:26
○ 2026-04-03 12:24:24

○NSdns8.pointhq.com2015-08-05 → 2016-03-12 · 4 obs

● 2015-08-05 19:26:00
● 2016-03-12 07:30:00
○ 2016-07-04 21:39:26
○ 2026-04-03 12:24:24

○NSdns9.pointhq.com2015-08-05 → 2016-03-12 · 4 obs

● 2015-08-05 19:26:00
● 2016-03-12 07:30:00
○ 2016-07-04 21:39:26
○ 2026-04-03 12:24:24

○NSns1.bdm.microsoftonline.com2017-02-20 → 2017-02-20 · 4 obs

○ 2016-07-04 21:39:26
● 2017-02-20 02:33:34
○ 2020-01-18 12:38:38
○ 2026-04-03 12:24:24

○NSns2.bdm.microsoftonline.com2017-02-20 → 2017-02-20 · 4 obs

○ 2016-07-04 21:39:26
● 2017-02-20 02:33:34
○ 2020-01-18 12:38:38
○ 2026-04-03 12:24:24

○NSns3.bdm.microsoftonline.com2017-02-20 → 2017-02-20 · 4 obs

○ 2016-07-04 21:39:26
● 2017-02-20 02:33:34
○ 2020-01-18 12:38:38
○ 2026-04-03 12:24:24

○NSns4.bdm.microsoftonline.com2017-02-20 → 2017-02-20 · 4 obs

○ 2016-07-04 21:39:26
● 2017-02-20 02:33:34
○ 2020-01-18 12:38:38
○ 2026-04-03 12:24:24

●MXmx.yandex.net2015-08-05 → 2026-04-03 · 5 obs

● 2015-08-05 19:26:00
● 2016-07-04 21:39:26
○ 2017-02-20 02:33:34
● 2020-01-18 12:38:38
● 2026-04-03 12:24:24

○MXprojectchiefs-com.mail.protection.outlook.com2017-02-20 → 2017-02-20 · 4 obs

○ 2016-07-04 21:39:26
● 2017-02-20 02:33:34
○ 2020-01-18 12:38:38
○ 2026-04-03 12:24:24

○A13.84.146.602017-02-20 → 2017-02-20 · 4 obs

○ 2016-07-04 21:39:26
● 2017-02-20 02:33:34
○ 2020-01-18 12:38:38
○ 2026-04-03 12:24:24

○A18.196.210.92020-01-18 → 2020-01-18 · 4 obs

○ 2017-02-20 02:33:34
● 2020-01-18 12:38:38
○ 2026-03-08 16:29:56
○ 2026-04-03 12:24:24

○A23.21.201.1332016-03-12 → 2016-03-12 · 4 obs

○ 2015-11-23 10:04:26
● 2016-03-12 07:30:00
○ 2016-07-04 21:39:26
○ 2026-04-03 12:24:24

○A23.21.224.1652015-11-23 → 2015-11-23 · 4 obs

○ 2015-08-05 19:26:00
● 2015-11-23 10:04:26
○ 2016-03-12 07:30:00
○ 2026-04-03 12:24:24

○A23.21.54.2272015-08-05 → 2015-08-05 · 3 obs

● 2015-08-05 19:26:00
○ 2015-11-23 10:04:26
○ 2026-04-03 12:24:24

●A3.66.162.182026-03-08 → 2026-04-03 · 3 obs

○ 2020-01-18 12:38:38
● 2026-03-08 16:29:56
● 2026-04-03 12:24:24

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
projectchiefs.com	dns1.yandex.net, dns2.yandex.net	-

✅ Authoritative Response

Server:93.158.134.213

NS records: dns1.yandex.net, dns2.yandex.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for projectchiefs.com (unsigned zone)

⏱️ Timing

Total: 542ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`3.66.162.18`
NS	2	`dns1.yandex.net, dns2.yandex.net`
MX	1	`mx.yandex.net (pri: 10)`
TXT	2	`v=spf1 redirect=_spf.yandex.net, google-site-verification=cw3xjic5B619aXx`
SOA	1	`dns1.yandex.net dns-hosting.yandex.ru`

Analysis

IP Addresses

projectchiefs.com points to a single IP: 3.66.162.18.

Other host names, for instance ec2-3-66-162-18.eu-central-1.compute.amazonaws.com, share IP numbers with projectchiefs.com.

Name Servers

projectchiefs.com's delegation is to two name servers dns1.yandex.net and dns2.yandex.net.

projectchiefs.com shares the same name server configuration as other domains, such as xn--80aabjyjev3ayg4d5b.xn--p1ai, zauralmedia.ru, bolshie.ru, minakirtasiye.com and sbeton.com.

projectchiefs.com at least partially shares its name servers with other domains, for instance uniiit.ru, sodegro.com, brickpark.ru, waoo.ru and tpiv.ru.

These name servers are commonly used alongside dns1.yandex.ru and dns2.yandex.ru.

Host names with two IP numbers: dns1.yandex.net points to 2a02:6b8::213 and 213.180.204.213; dns2.yandex.net points to 2a02:6b8:0:1::213 and 93.158.134.213

Mail Servers

projectchiefs.com is served by a single mail server, mx.yandex.net.

projectchiefs.com uses the same mail server setup as other domains such as ek-r24.ru, recargolf.com, goldfish.su, lider39.ru and omskoenebo.ru.

projectchiefs.com shares some mail servers with other domains, including www.tangoshoes.ru, santeh-snab.ru, tpoa.ru, microel.ru and sun-studio.su.

Hostname mx.yandex.net resolves to two IPs: 2a02:6b8::311 and 77.88.21.249.

projectchiefs.com - robtex.com