`proxyapi.ru`

DNSSEC	⚠️ Not signed
A	51.250.45.232^{🇷🇺 YandexCloud51.250.0.0/17}
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	`mx1.hosting.reg.ru` ⭐
		A	31.31.194.240^{🇷🇺 AS-REGRU31.31.194.0/24 Reg.Ru}
			PTR	`relay.hosting.reg.ru`
		A	31.31.194.241^{🇷🇺 AS-REGRU31.31.194.0/24 Reg.Ru}
			PTR	`relay.hosting.reg.ru`
MX	`mx2.hosting.reg.ru`⁽¹⁵⁾
		A	31.31.194.240^{🇷🇺 AS-REGRU31.31.194.0/24 Reg.Ru}
			PTR	`relay.hosting.reg.ru`
		A	31.31.194.241^{🇷🇺 AS-REGRU31.31.194.0/24 Reg.Ru}
			PTR	`relay.hosting.reg.ru`
TXT	`v=spf1 ip4:31.31.198.28 a mx include:_spf.hosting.reg.ru include:spf.unisende...`
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	`d.dns.ripn.net`
	NS	`e.dns.ripn.net`
	NS	`f.dns.ripn.net`
	SOA	`a.dns.ripn.net`hostmaster@ripn.net serial=4068815

📈 Tranco rank: #447,478

Same first word

proxyapi.com

proxyapi.ru

proxyapi.shop

Similar names

piaproxy.pro

apiproxy.net

apiproxy.cloud

apiproxy.com

apiproxy.studio

proxipay.com

piaproxy.net

apiproxy.org

DNS History

5 records (5 active, 0 former)

●NSns1.yandexcloud.net2026-03-27 → 2026-05-09 · 2 obs

● 2026-03-27 05:18:18
● 2026-05-09 20:33:56

●NSns2.yandexcloud.net2026-03-27 → 2026-05-09 · 2 obs

● 2026-03-27 05:18:18
● 2026-05-09 20:33:56

●MXmx1.hosting.reg.ru2026-03-27 → 2026-05-09 · 2 obs

● 2026-03-27 05:18:18
● 2026-05-09 20:33:56

●MXmx2.hosting.reg.ru2026-03-27 → 2026-05-09 · 2 obs

● 2026-03-27 05:18:18
● 2026-05-09 20:33:56

●A51.250.45.2322026-03-27 → 2026-05-09 · 2 obs

● 2026-03-27 05:18:18
● 2026-05-09 20:33:56

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
ru	d.dns.ripn.net, b.dns.ripn.net, a.dns.ripn.net, e.dns.ripn.net...	-
proxyapi.ru	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 proxyapi.ru (unsigned zone)

⏱️ Timing

Total: 1448ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`51.250.45.232`
NS	2	`ns1.yandexcloud.net, ns2.yandexcloud.net`
MX	2	`mx1.hosting.reg.ru (pri: 10), mx2.hosting.reg.ru (pri: 15)`
TXT	1	`v=spf1 ip4:31.31.198.28 a mx include:_sp`
SOA	1	`ns1.yandexcloud.net mx.cloud.yandex.net`

Analysis

IP Addresses

proxyapi.ru points to a single IP number: 51.250.45.232.

Name Servers

proxyapi.ru is delegated to two name servers: ns1.yandexcloud.net and ns2.yandexcloud.net.

proxyapi.ru uses the same name server setup as other domains, for instance 205.188.93.in-addr.arpa, paybox.ru, artics.com, pravozakon.ru and bref.ru.

proxyapi.ru at least partially shares name servers with other domains, such as bork.lt and mbx-sender-06.ru and itv.ru.

Host names with two IP numbers:

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

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

Mail Servers

proxyapi.ru is handled by two mail servers: mx1.hosting.reg.ru and mx2.hosting.reg.ru.

proxyapi.ru shares the same mail server setup as other domains, including pwi.ru, les-invest.ru, stoponanizm.ru, zibert.ru and fieldflower.ru.