🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`jpdevelops.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3030::6815:1309^{🇺🇸 Cloudflare2606:4700:3030::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3033::ac43:b861^{🇺🇸 Cloudflare2606:4700:3033::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.19.9^{Cloudflare104.21.16.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.184.97^{🇺🇸 Cloudflare172.67.176.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`ignacio.ns.cloudflare.com` ⭐
		A	2606:4700:58::a29f:2c52^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ignacio.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c352^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`ignacio.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2352^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`ignacio.ns.cloudflare.com`
		A	108.162.195.82^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ignacio.ns.cloudflare.com`
		A	162.159.44.82^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ignacio.ns.cloudflare.com`
		A	172.64.35.82^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ignacio.ns.cloudflare.com`
NS	`karsyn.ns.cloudflare.com`
		A	2606:4700:50::a29f:26c2^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`karsyn.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c2c2^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`karsyn.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:22c2^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`karsyn.ns.cloudflare.com`
		A	108.162.194.194^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`karsyn.ns.cloudflare.com`
		A	162.159.38.194^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`karsyn.ns.cloudflare.com`
		A	172.64.34.194^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`karsyn.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	`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`
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`
TXT	`protonmail-verification=7929bab7468f7188df4778b41615ab02cbcaca93`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.19.9, 172.67.184.97
		IPv6 hints	2606:4700:3030::6815:1309, 2606:4700:3033::ac43:b861
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=201, name=cloudflare-ech.com
SOA	`ignacio.ns.cloudflare.com`dns@cloudflare.com serial=2414065656

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

Same first word

jpdevelops.com

Previous names

Next names

DNS History

21 records (9 active, 12 former)

○NSdns1.registrar-servers.com2018-10-28 → 2018-10-28 · 3 obs

● 2018-10-28 19:29:56
○ 2026-09-06 12:52:42
○ 2026-09-14 09:15:24

○NSdns2.registrar-servers.com2018-10-28 → 2018-10-28 · 3 obs

● 2018-10-28 19:29:56
○ 2026-09-06 12:52:42
○ 2026-09-14 09:15:24

●NSignacio.ns.cloudflare.com2026-09-06 → 2026-09-14 · 3 obs

○ 2018-10-28 19:29:56
● 2026-09-06 12:52:42
● 2026-09-14 09:15:24

●NSkarsyn.ns.cloudflare.com2026-09-06 → 2026-09-14 · 3 obs

○ 2018-10-28 19:29:56
● 2026-09-06 12:52:42
● 2026-09-14 09:15:24

○MXeforward1.registrar-servers.com2018-10-28 → 2018-10-28 · 3 obs

● 2018-10-28 19:29:56
○ 2026-09-06 12:52:42
○ 2026-09-14 09:15:24

○MXeforward2.registrar-servers.com2018-10-28 → 2018-10-28 · 3 obs

● 2018-10-28 19:29:56
○ 2026-09-06 12:52:42
○ 2026-09-14 09:15:24

○MXeforward3.registrar-servers.com2018-10-28 → 2018-10-28 · 3 obs

● 2018-10-28 19:29:56
○ 2026-09-06 12:52:42
○ 2026-09-14 09:15:24

○MXeforward4.registrar-servers.com2018-10-28 → 2018-10-28 · 3 obs

● 2018-10-28 19:29:56
○ 2026-09-06 12:52:42
○ 2026-09-14 09:15:24

○MXeforward5.registrar-servers.com2018-10-28 → 2018-10-28 · 3 obs

● 2018-10-28 19:29:56
○ 2026-09-06 12:52:42
○ 2026-09-14 09:15:24

●MXroute1.mx.cloudflare.net2026-09-06 → 2026-09-14 · 3 obs

○ 2018-10-28 19:29:56
● 2026-09-06 12:52:42
● 2026-09-14 09:15:24

●MXroute2.mx.cloudflare.net2026-09-06 → 2026-09-14 · 3 obs

○ 2018-10-28 19:29:56
● 2026-09-06 12:52:42
● 2026-09-14 09:15:24

●MXroute3.mx.cloudflare.net2026-09-06 → 2026-09-14 · 3 obs

○ 2018-10-28 19:29:56
● 2026-09-06 12:52:42
● 2026-09-14 09:15:24

●A104.21.19.92026-09-11 → 2026-09-14 · 3 obs

○ 2026-09-06 12:52:42
● 2026-09-11 02:43:38
● 2026-09-14 09:15:24

○A162.255.119.1492018-10-28 → 2018-10-28 · 3 obs

● 2018-10-28 19:29:56
○ 2026-09-06 12:52:42
○ 2026-09-14 09:15:24

●A172.67.184.972026-09-11 → 2026-09-14 · 3 obs

○ 2026-09-06 12:52:42
● 2026-09-11 02:43:38
● 2026-09-14 09:15:24

○A188.114.96.02026-09-06 → 2026-09-06 · 4 obs

○ 2018-10-28 19:29:56
● 2026-09-06 12:52:42
○ 2026-09-11 02:43:38
○ 2026-09-14 09:15:24

○A188.114.97.02026-09-06 → 2026-09-06 · 4 obs

○ 2018-10-28 19:29:56
● 2026-09-06 12:52:42
○ 2026-09-11 02:43:38
○ 2026-09-14 09:15:24

●A2606:4700:3030::6815:13092026-09-11 → 2026-09-14 · 3 obs

○ 2026-09-06 12:52:42
● 2026-09-11 02:43:38
● 2026-09-14 09:15:24

●A2606:4700:3033::ac43:b8612026-09-11 → 2026-09-14 · 3 obs

○ 2026-09-06 12:52:42
● 2026-09-11 02:43:38
● 2026-09-14 09:15:24

○A2a06:98c1:3120::2026-09-06 → 2026-09-06 · 4 obs

○ 2018-10-28 19:29:56
● 2026-09-06 12:52:42
○ 2026-09-11 02:43:38
○ 2026-09-14 09:15:24

○A2a06:98c1:3121::2026-09-06 → 2026-09-06 · 4 obs

○ 2018-10-28 19:29:56
● 2026-09-06 12:52:42
○ 2026-09-11 02:43:38
○ 2026-09-14 09:15:24

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, j.gtld-servers.net, b.gtld-servers.net, h.gtld-servers.net...	-
jpdevelops.com	karsyn.ns.cloudflare.com, ignacio.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.195.82

NS records: karsyn.ns.cloudflare.com, ignacio.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for jpdevelops.com (unsigned zone)

⏱️ Timing

Total: 240ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.184.97, 104.21.19.9`
AAAA	2	`2606:4700:3030::6815:1309, 2606:4700:3033::ac43:b861`
NS	2	`ignacio.ns.cloudflare.com, karsyn.ns.cloudflare.com`
MX	3	`route2.mx.cloudflare.net (pri: 29), route1.mx.cloudflare.net (pri: 90)...`
TXT	2	`protonmail-verification=7929bab7468f7188, v=spf1 include:_spf.mx.cloudflare.net ~a`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`ignacio.ns.cloudflare.com dns.cloudflare`

📌 Glue Records Collected

Total: 12

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

Analysis

IP Addresses

jpdevelops.com resolves to four IP addresses: 104.21.19.9, 172.67.184.97, 2606:4700:3030::6815:1309 and 2606:4700:3033::ac43:b861.

ta999x.com, linswind.com, img.networthpost.com plus two other host names have IP numbers in common with jpdevelops.com.

Name Servers

Two name servers handle the delegation for jpdevelops.com: ignacio.ns.cloudflare.com and karsyn.ns.cloudflare.com.

The name server configuration of jpdevelops.com is shared with other domains, for instance rokas.email, fayettecountyhistorical.org, carpetcleaninglords.co.uk and two others.

jpdevelops.com has at least partial name server overlap with other domains, such as propalmscore.info, getaninsurancequote.co.uk, youtupegames2.workers.dev and two others.

It is common to see these name servers used together with name servers aleena.ns.cloudflare.com and kelly.ns.cloudflare.com.

Hosts with 6 IP addresses each:

ignacio.ns.cloudflare.com resolves to 108.162.195.82, 162.159.44.82 and 172.64.35.82 among others, with 3 other IP addresses in total.

karsyn.ns.cloudflare.com resolves to 108.162.194.194, 162.159.38.194 and 172.64.34.194 among others, with 3 other IP addresses in total.

Mail Servers

jpdevelops.com has three mail servers: route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

At least some of the mail servers used by jpdevelops.com are shared with other domains: hadiaghazadeh.com, loongma.org, s5.design and two others among them.

Hosts with 6 IP addresses each:

route1.mx.cloudflare.net resolves to 162.159.205.11, 162.159.205.12 and 162.159.205.13 among others, with 3 other IP addresses in total.

route2.mx.cloudflare.net resolves to 162.159.205.17, 162.159.205.18 and 162.159.205.19 among others, with 3 other IP addresses in total.

route3.mx.cloudflare.net resolves to 162.159.205.23, 162.159.205.24 and 162.159.205.25 among others, with 3 other IP addresses in total.

jpdevelops.com - robtex.com

jpdevelops.com

com

Same first word

Previous names

Next names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

IP Addresses

Name Servers

Mail Servers

`jpdevelops.com`

`com`