`play-progress.com`

DNSSEC	⚠️ Not signed
A	178.248.234.146^{🇷🇺 HLL-AS178.248.234.0/23 HLL}
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	`_globalsign-domain-verification=leQpxVkJHFrg3sVnvc52573jyr12nmxeUllZPC5I5a`
TXT	`yandex-verification: 54c6fc177b95b27d`
TXT	`v=spf1 redirect=_spf.yandex.net`
SOA	`dns1.yandex.net`dns-hosting@yandex.ru serial=7

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

WOT: SAFE (74/100)

Same first word

play-progress.com

DNS History

18 records (4 active, 14 former)

●NSdns1.yandex.net2026-02-15 → 2026-04-24 · 3 obs

○ 2017-06-12 15:49:20
● 2026-02-15 17:33:56
● 2026-04-24 21:39:22

●NSdns2.yandex.net2026-02-15 → 2026-04-24 · 3 obs

○ 2017-06-12 15:49:20
● 2026-02-15 17:33:56
● 2026-04-24 21:39:22

○NSns.masterhost.ru2015-08-24 → 2017-06-12 · 4 obs

● 2015-08-24 07:19:24
● 2017-06-12 15:49:20
○ 2026-02-15 17:33:56
○ 2026-04-24 21:39:22

○NSns1.masterhost.ru2015-08-24 → 2017-06-12 · 4 obs

● 2015-08-24 07:19:24
● 2017-06-12 15:49:20
○ 2026-02-15 17:33:56
○ 2026-04-24 21:39:22

○NSns2.masterhost.ru2015-08-24 → 2017-06-12 · 4 obs

● 2015-08-24 07:19:24
● 2017-06-12 15:49:20
○ 2026-02-15 17:33:56
○ 2026-04-24 21:39:22

●MXmx.yandex.net2026-02-15 → 2026-04-24 · 3 obs

○ 2017-06-12 15:49:20
● 2026-02-15 17:33:56
● 2026-04-24 21:39:22

○MXmx4.masterhost.ru2015-08-24 → 2017-06-12 · 4 obs

● 2015-08-24 07:19:24
● 2017-06-12 15:49:20
○ 2026-02-15 17:33:56
○ 2026-04-24 21:39:22

●A178.248.234.1462026-02-15 → 2026-04-24 · 3 obs

○ 2017-06-12 15:49:20
● 2026-02-15 17:33:56
● 2026-04-24 21:39:22

○A2a00:15f8:a000:5:1:11:0:fcad2015-08-24 → 2017-06-12 · 4 obs

● 2015-08-24 07:19:24
● 2017-06-12 15:49:20
○ 2026-02-15 17:33:56
○ 2026-04-24 21:39:22

○A2a00:15f8:a000:5:1:12:0:fcad2015-08-24 → 2017-06-12 · 4 obs

● 2015-08-24 07:19:24
● 2017-06-12 15:49:20
○ 2026-02-15 17:33:56
○ 2026-04-24 21:39:22

○A2a00:15f8:a000:5:1:13:0:fcad2015-08-24 → 2017-06-12 · 4 obs

● 2015-08-24 07:19:24
● 2017-06-12 15:49:20
○ 2026-02-15 17:33:56
○ 2026-04-24 21:39:22

○A2a00:15f8:a000:5:1:14:0:fcad2015-08-24 → 2017-06-12 · 4 obs

● 2015-08-24 07:19:24
● 2017-06-12 15:49:20
○ 2026-02-15 17:33:56
○ 2026-04-24 21:39:22

○A90.156.201.1102017-05-02 → 2017-06-12 · 5 obs

○ 2016-12-31 03:54:24
● 2017-05-02 11:15:22
● 2017-06-12 15:49:20
○ 2026-02-15 17:33:56
○ 2026-04-24 21:39:22

○A90.156.201.1122015-08-24 → 2016-09-12 · 4 obs

● 2015-08-24 07:19:24
● 2016-09-12 10:25:08
○ 2016-11-22 20:47:08
○ 2026-04-24 21:39:22

○A90.156.201.462015-08-24 → 2017-06-12 · 4 obs

● 2015-08-24 07:19:24
● 2017-06-12 15:49:20
○ 2026-02-15 17:33:56
○ 2026-04-24 21:39:22

○A90.156.201.512015-08-24 → 2016-12-31 · 4 obs

● 2015-08-24 07:19:24
● 2016-12-31 03:54:24
○ 2017-05-02 11:15:22
○ 2026-04-24 21:39:22

○A90.156.201.532016-11-22 → 2017-06-12 · 5 obs

○ 2016-09-12 10:25:08
● 2016-11-22 20:47:08
● 2017-06-12 15:49:20
○ 2026-02-15 17:33:56
○ 2026-04-24 21:39:22

○A90.156.201.972015-08-24 → 2017-06-12 · 4 obs

● 2015-08-24 07:19:24
● 2017-06-12 15:49:20
○ 2026-02-15 17:33:56
○ 2026-04-24 21:39:22

🔍 DNS Trace

📋 Delegation Chain

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

✅ Authoritative Response

Server:213.180.204.213

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for play-progress.com (unsigned zone)

⏱️ Timing

Total: 752ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`178.248.234.146`
NS	2	`dns1.yandex.net, dns2.yandex.net`
MX	1	`mx.yandex.net (pri: 10)`
TXT	3	`_globalsign-domain-verification=leQpxVkJ, yandex-verification: 54c6fc177b95b27d...`
SOA	1	`dns1.yandex.net dns-hosting.yandex.ru`

Analysis

IP Addresses

play-progress.com points to IP number: 178.248.234.146.

Other host names such as mail.skystudio.kz, annapolyakova.ru, albadent.by, sorsdata.ru and ocenka-optima.ru share IPs with play-progress.com.

Name Servers

play-progress.com is delegated to two name servers: dns1.yandex.net and dns2.yandex.net.

play-progress.com shares the same name server setup as sudexpa.ru, eleks-tver.ru, iarga.ru, hungryboys.ru and chat-off.net.

play-progress.com at least partially shares name servers with other domains, for instance rek-fm.ru, ganeeva.info, kashaev.net, gphotel.ru and moto-naprokat.ru.

These name servers are commonly used with 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

play-progress.com is handled by a single mail server, mx.yandex.net.

The mail server setup for play-progress.com matches that of other domains, for instance naturelyatak.com, nppbad.ru, atacandemircelik.com, erboga.com and webcumo.net.

play-progress.com shares at least partially some mail servers with other domains, including bot-t.ru, ursk-stroy.com, oooeco-m.ru, net-zapoya.ru and nv66.ru.

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

play-progress.com - robtex.com