ipsproxy.com - dns.ninja

`ipsproxy.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3034::ac43:8224^{🇺🇸 Cloudflare2606:4700:3034::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3036::6815:31d^{🇺🇸 Cloudflare2606:4700:3036::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.3.29^{Cloudflare104.21.0.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.130.36^{🇺🇸 Cloudflare172.67.128.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`chad.ns.cloudflare.com` ⭐
		A	2606:4700:58::adf5:3b52^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chad.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c152^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`chad.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2152^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`chad.ns.cloudflare.com`
		A	108.162.193.82^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chad.ns.cloudflare.com`
		A	172.64.33.82^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chad.ns.cloudflare.com`
		A	173.245.59.82^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chad.ns.cloudflare.com`
NS	`melany.ns.cloudflare.com`
		A	2606:4700:50::a29f:268a^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`melany.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c28a^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`melany.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:228a^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`melany.ns.cloudflare.com`
		A	108.162.194.138^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`melany.ns.cloudflare.com`
		A	162.159.38.138^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`melany.ns.cloudflare.com`
		A	172.64.34.138^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`melany.ns.cloudflare.com`
MX	`mx1.hostinger.com` ⭐
		A	2606:4700:90:0:c1f8:f874:2386:b61f^{🇺🇸 Cloudflare2606:4700:90::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	172.65.182.103^{🇺🇸 Cloudflare172.65.176.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
MX	`mx2.hostinger.com`⁽¹⁰⁾
		A	2606:4700:90:0:c1f8:f874:2386:b61f^{🇺🇸 Cloudflare2606:4700:90::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	172.65.182.103^{🇺🇸 Cloudflare172.65.176.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
TXT	`v=spf1 include:_spf.mail.hostinger.com ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.3.29, 172.67.130.36
		IPv6 hints	2606:4700:3034::ac43:8224, 2606:4700:3036::6815:31d
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=26, name=cloudflare-ech.com
SOA	`chad.ns.cloudflare.com`dns@cloudflare.com serial=2411220225

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

⚠️ On DNS blocklist: tif

Same first word

ipsproxy.com

Similar names

DNS History

18 records (8 active, 10 former)

●NSchad.ns.cloudflare.com2026-05-13 → 2026-08-06 · 3 obs

○ 2026-04-29 12:10:22
● 2026-05-13 08:17:00
● 2026-08-06 23:44:16

●NSmelany.ns.cloudflare.com2026-05-13 → 2026-08-06 · 3 obs

○ 2026-04-29 12:10:22
● 2026-05-13 08:17:00
● 2026-08-06 23:44:16

○NSns1.dns-parking.com2026-03-23 → 2026-04-29 · 5 obs

○ 2017-08-30 18:59:36
● 2026-03-23 01:00:58
● 2026-04-29 12:10:22
○ 2026-05-13 08:17:00
○ 2026-08-06 23:44:16

○NSns1.myhostadmin.net2016-12-05 → 2016-12-05 · 3 obs

● 2016-12-05 02:08:10
○ 2017-08-30 18:59:36
○ 2026-08-06 23:44:16

○NSns2.dns-parking.com2026-03-23 → 2026-04-29 · 5 obs

○ 2017-08-30 18:59:36
● 2026-03-23 01:00:58
● 2026-04-29 12:10:22
○ 2026-05-13 08:17:00
○ 2026-08-06 23:44:16

○NSns2.myhostadmin.net2016-12-05 → 2016-12-05 · 3 obs

● 2016-12-05 02:08:10
○ 2017-08-30 18:59:36
○ 2026-08-06 23:44:16

○NSns3.myhostadmin.net2016-12-05 → 2016-12-05 · 3 obs

● 2016-12-05 02:08:10
○ 2017-08-30 18:59:36
○ 2026-08-06 23:44:16

○NSns4.myhostadmin.net2016-12-05 → 2016-12-05 · 3 obs

● 2016-12-05 02:08:10
○ 2017-08-30 18:59:36
○ 2026-08-06 23:44:16

○NSns5.myhostadmin.net2016-12-05 → 2016-12-05 · 3 obs

● 2016-12-05 02:08:10
○ 2017-08-30 18:59:36
○ 2026-08-06 23:44:16

○NSns6.myhostadmin.net2016-12-05 → 2016-12-05 · 3 obs

● 2016-12-05 02:08:10
○ 2017-08-30 18:59:36
○ 2026-08-06 23:44:16

●MXmx1.hostinger.com2026-05-13 → 2026-08-06 · 2 obs

● 2026-05-13 08:17:00
● 2026-08-06 23:44:16

●MXmx2.hostinger.com2026-05-13 → 2026-08-06 · 2 obs

● 2026-05-13 08:17:00
● 2026-08-06 23:44:16

●A104.21.3.292026-05-13 → 2026-08-06 · 3 obs

○ 2026-04-29 12:10:22
● 2026-05-13 08:17:00
● 2026-08-06 23:44:16

●A172.67.130.362026-05-13 → 2026-08-06 · 3 obs

○ 2026-04-29 12:10:22
● 2026-05-13 08:17:00
● 2026-08-06 23:44:16

○A2606:4700:3032::6815:31d2026-05-13 → 2026-06-01 · 5 obs

○ 2026-04-29 12:10:22
● 2026-05-13 08:17:00
● 2026-06-01 03:22:10
○ 2026-06-29 12:10:14
○ 2026-08-06 23:44:16

●A2606:4700:3034::ac43:82242026-05-13 → 2026-08-06 · 3 obs

○ 2026-04-29 12:10:22
● 2026-05-13 08:17:00
● 2026-08-06 23:44:16

●A2606:4700:3036::6815:31d2026-06-29 → 2026-08-06 · 3 obs

○ 2026-06-01 03:22:10
● 2026-06-29 12:10:14
● 2026-08-06 23:44:16

○A72.62.73.1852026-03-23 → 2026-04-29 · 4 obs

● 2026-03-23 01:00:58
● 2026-04-29 12:10:22
○ 2026-05-13 08:17:00
○ 2026-08-06 23:44:16

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	e.gtld-servers.net, i.gtld-servers.net, d.gtld-servers.net, b.gtld-servers.net...	-
ipsproxy.com	chad.ns.cloudflare.com, melany.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.194.138

NS records: chad.ns.cloudflare.com, melany.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for ipsproxy.com (unsigned zone)

⏱️ Timing

Total: 217ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.3.29, 172.67.130.36`
AAAA	2	`2606:4700:3034::ac43:8224, 2606:4700:3036::6815:31d`
NS	2	`chad.ns.cloudflare.com, melany.ns.cloudflare.com`
MX	2	`mx2.hostinger.com (pri: 10), mx1.hostinger.com (pri: 5)`
TXT	1	`v=spf1 include:_spf.mail.hostinger.com ~`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`chad.ns.cloudflare.com dns.cloudflare.co`

📌 Glue Records Collected

Total: 12

Out-of-bailiwick: 12 (chad.ns.cloudflare.com, chad.ns.cloudflare.com, chad.ns.cloudflare.com...)

Analysis

IP Addresses

ipsproxy.com points to the four IP addresses 104.21.3.29, 172.67.130.36, 2606:4700:3034::ac43:8224 and 2606:4700:3036::6815:31d.

worldwidedreamproperty.com, 93416.cc, ns1.doyonavocats.ca and two other host names share IP numbers with ipsproxy.com.

Name Servers

The NS records for ipsproxy.com delegate to chad.ns.cloudflare.com and melany.ns.cloudflare.com.

ipsproxy.com uses the same name servers as several other domains — among them 87258.cfd, interphonet.com.mx, port01-7s6.pages.dev and two more.

There is at least partial name server overlap between ipsproxy.com and other domains — constructorajimenez.com.co, brevity.pro, cathook.club and two more among them.

These name servers frequently co-occur with the name servers ganz.ns.cloudflare.com and nina.ns.cloudflare.com.

Hostnames that resolve to 6 IP addresses:

chad.ns.cloudflare.com maps to 108.162.193.82, 172.64.33.82, 173.245.59.82 and 3 additional IP addresses.

melany.ns.cloudflare.com maps to 108.162.194.138, 162.159.38.138, 172.64.34.138 and 3 additional IP addresses.

Mail Servers

Mail for ipsproxy.com is handled by two mail servers — mx1.hostinger.com and mx2.hostinger.com.

ipsproxy.com uses an identical mail server configuration to several other domains — among them itanasa.com, cleanup-service-eg.com, ougjjou.com and two more.

ipsproxy.com and other domains — clinicapasapas.com for instance — share at least some mail servers.

mx1.hostinger.com has IP addresses 172.65.182.103 and 2606:4700:90:0:c1f8:f874:2386:b61f; mx2.hostinger.com has the same IP addresses: 172.65.182.103 and 2606:4700:90:0:c1f8:f874:2386:b61f.

mx1.hostinger.com and mx2.hostinger.com each have 2606:4700:90:0:c1f8:f874:2386:b61f IP addresses.

mx1.hostinger.com and mx2.hostinger.com each have 172.65.182.103 IP addresses.