proxy-ai.tech - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`proxy-ai.tech`

DNSSEC	⚠️ Not signed
NS	`chase.ns.cloudflare.com` ⭐
		A	2606:4700:58::a29f:2c9c^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chase.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c39c^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`chase.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:239c^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`chase.ns.cloudflare.com`
		A	108.162.195.156^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chase.ns.cloudflare.com`
		A	162.159.44.156^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chase.ns.cloudflare.com`
		A	172.64.35.156^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chase.ns.cloudflare.com`
NS	`ryleigh.ns.cloudflare.com`
		A	2606:4700:50::a29f:26c6^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ryleigh.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c2c6^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`ryleigh.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:22c6^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`ryleigh.ns.cloudflare.com`
		A	108.162.194.198^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ryleigh.ns.cloudflare.com`
		A	162.159.38.198^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ryleigh.ns.cloudflare.com`
		A	172.64.34.198^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ryleigh.ns.cloudflare.com`
MX	`route2.mx.cloudflare.net` ⭐
		A	2606:4700:f5::e^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::f^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::10^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.17^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.18^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.19^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
MX	`route3.mx.cloudflare.net`⁽⁷²⁾
		A	2606:4700:f5::11^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::12^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::13^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.23^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.24^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.25^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
MX	`route1.mx.cloudflare.net`⁽⁷⁶⁾
		A	2606:4700:f5::b^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::c^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::d^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.11^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.12^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.13^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
SOA	`chase.ns.cloudflare.com`dns@cloudflare.com serial=2409543392

`tech`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns01.trs-dns.com` ⭐
	NS	`ns.trs-dns.com`
	NS	`ns01.trs-dns.net`
	NS	`ns10.trs-dns.info`
	NS	`ns10.trs-dns.org`
	SOA	`ns.trs-dns.com`trs-ops@tucows.com serial=1786841639

Same first word

proxy-ai.tech

DNS History

5 records (5 active, 0 former)

●NSchase.ns.cloudflare.com2026-04-20 → 2026-08-16 · 2 obs

● 2026-04-20 08:48:10
● 2026-08-16 00:57:54

●NSryleigh.ns.cloudflare.com2026-04-20 → 2026-08-16 · 2 obs

● 2026-04-20 08:48:10
● 2026-08-16 00:57:54

●MXroute1.mx.cloudflare.net2026-04-20 → 2026-08-16 · 2 obs

● 2026-04-20 08:48:10
● 2026-08-16 00:57:54

●MXroute2.mx.cloudflare.net2026-04-20 → 2026-08-16 · 2 obs

● 2026-04-20 08:48:10
● 2026-08-16 00:57:54

●MXroute3.mx.cloudflare.net2026-04-20 → 2026-08-16 · 2 obs

● 2026-04-20 08:48:10
● 2026-08-16 00:57:54

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
tech	ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org, ns10.trs-dns.info	8 records
proxy-ai.tech	chase.ns.cloudflare.com, ryleigh.ns.cloudflare.com	-

✅ Authoritative Response

Server:162.159.44.156

NS records: chase.ns.cloudflare.com, ryleigh.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for proxy-ai.tech (unsigned zone)

⏱️ Timing

Total: 320ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`chase.ns.cloudflare.com, ryleigh.ns.cloudflare.com`
MX	3	`route2.mx.cloudflare.net (pri: 3), route3.mx.cloudflare.net (pri: 72)...`
TXT	1	`v=spf1 include:_spf.mx.cloudflare.net ~a`
SOA	1	`chase.ns.cloudflare.com dns.cloudflare.c`

📌 Glue Records Collected

Total: 8

Out-of-bailiwick: 8 (ns01.trs-dns.com, ns01.trs-dns.net, ns10.trs-dns.org...)

Analysis

Name Servers

The NS records for proxy-ai.tech delegate to chase.ns.cloudflare.com and ryleigh.ns.cloudflare.com.

proxy-ai.tech shares the same name server configuration with zebrafishrapidtest.com, favaretooficialeiloes.com, digic.org and 1acx.com.

proxy-ai.tech shares at least some of its name servers with other domains, including karmod.es, vavadacasino-es.click, a-yals.com and two others.

These name servers are frequently paired with the name servers kip.ns.cloudflare.com and karsyn.ns.cloudflare.com.

Hostnames that resolve to 6 IP addresses:

chase.ns.cloudflare.com maps to 108.162.195.156, 162.159.44.156, 172.64.35.156 and 3 additional IP addresses.

ryleigh.ns.cloudflare.com maps to 108.162.194.198, 162.159.38.198, 172.64.34.198 and 3 additional IP addresses.

Mail Servers

proxy-ai.tech is handled by three mail servers: route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

proxy-ai.tech has at least partial mail server overlap with other domains such as tooearlybird.com, bisam.lv, deshnok.in and two more.

Hostnames that resolve to 6 IP addresses:

route1.mx.cloudflare.net maps to 162.159.205.11, 162.159.205.12, 162.159.205.13 and 3 additional IP addresses.

route2.mx.cloudflare.net maps to 162.159.205.17, 162.159.205.18, 162.159.205.19 and 3 additional IP addresses.

route3.mx.cloudflare.net maps to 162.159.205.23, 162.159.205.24, 162.159.205.25 and 3 additional IP addresses.