jpdevsecops.com - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`jpdevsecops.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3031::6815:322a^{🇺🇸 Cloudflare2606:4700:3031::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3033::ac43:c8bc^{🇺🇸 Cloudflare2606:4700:3033::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.50.42^{Cloudflare104.21.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.200.188^{🇺🇸 Cloudflare172.67.192.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`blakely.ns.cloudflare.com` ⭐
		A	2606:4700:50::a29f:2660^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`blakely.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c260^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`blakely.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2260^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`blakely.ns.cloudflare.com`
		A	108.162.194.96^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`blakely.ns.cloudflare.com`
		A	162.159.38.96^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`blakely.ns.cloudflare.com`
		A	172.64.34.96^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`blakely.ns.cloudflare.com`
NS	`lamar.ns.cloudflare.com`
		A	2606:4700:58::a29f:2c8e^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lamar.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c38e^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`lamar.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:238e^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`lamar.ns.cloudflare.com`
		A	108.162.195.142^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lamar.ns.cloudflare.com`
		A	162.159.44.142^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lamar.ns.cloudflare.com`
		A	172.64.35.142^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`lamar.ns.cloudflare.com`
MX	`smtp.google.com` ⭐
		A	2607:f8b0:4004:c1b::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`wv-in-f26.1e100.net`
		A	2607:f8b0:4004:c1d::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`ww-in-f26.1e100.net`
		A	2607:f8b0:4004:c1d::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`ww-in-f27.1e100.net`
		A	2607:f8b0:4004:c25::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadtq-in-f26.1e100.net`
		A	142.251.163.26^{🇺🇸 Google142.251.163.0/24}
			PTR	`wv-in-f26.1e100.net`
		A	142.251.167.26^{🇺🇸 Google142.251.167.0/24}
			PTR	`ww-in-f26.1e100.net`
		A	142.251.167.27^{🇺🇸 Google142.251.167.0/24}
			PTR	`ww-in-f27.1e100.net`
		A	173.194.45.26^{🇺🇸 Google173.194.0.0/16}
			PTR	`yuiadum-in-f26.1e100.net`
		A	192.178.218.27^{🇺🇸 Google192.178.218.0/24}
			PTR	`yuiadtq-in-f27.1e100.net`
TXT	`google-site-verification=5uQm69nA7vp7KZTXD9NNgMWzE9MANEhZF-QSWZ52sl4`
TXT	`v=spf1 include:_spf.google.com ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.50.42, 172.67.200.188
		IPv6 hints	2606:4700:3031::6815:322a, 2606:4700:3033::ac43:c8bc
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=184, name=cloudflare-ech.com
SOA	`blakely.ns.cloudflare.com`dns@cloudflare.com serial=2414465096

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

Same first word

jpdevsecops.com

Previous names

Next names

DNS History

7 records (7 active, 0 former)

●NSblakely.ns.cloudflare.com2026-08-31 → 2026-09-24 · 2 obs

● 2026-08-31 06:44:06
● 2026-09-24 10:45:12

●NSlamar.ns.cloudflare.com2026-08-31 → 2026-09-24 · 2 obs

● 2026-08-31 06:44:06
● 2026-09-24 10:45:12

●MXsmtp.google.com2026-08-31 → 2026-09-24 · 2 obs

● 2026-08-31 06:44:06
● 2026-09-24 10:45:12

●A104.21.50.422026-09-14 → 2026-09-24 · 2 obs

● 2026-09-14 09:15:22
● 2026-09-24 10:45:12

●A172.67.200.1882026-09-14 → 2026-09-24 · 2 obs

● 2026-09-14 09:15:22
● 2026-09-24 10:45:12

●A2606:4700:3031::6815:322a2026-09-14 → 2026-09-24 · 2 obs

● 2026-09-14 09:15:22
● 2026-09-24 10:45:12

●A2606:4700:3033::ac43:c8bc2026-09-14 → 2026-09-24 · 2 obs

● 2026-09-14 09:15:22
● 2026-09-24 10:45:12

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
jpdevsecops.com	blakely.ns.cloudflare.com, lamar.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.195.142

NS records: blakely.ns.cloudflare.com, lamar.ns.cloudflare.com

🔒 DNSSEC Status

🔐 Secure (DNSSEC validated)

Chain of trust verified from root to domain

⏱️ Timing

Total: 267ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.200.188, 104.21.50.42`
AAAA	2	`2606:4700:3033::ac43:c8bc, 2606:4700:3031::6815:322a`
NS	2	`blakely.ns.cloudflare.com, lamar.ns.cloudflare.com`
MX	1	`smtp.google.com (pri: 10)`
TXT	2	`google-site-verification=5uQm69nA7vp7KZT, v=spf1 include:_spf.google.com ~all`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`blakely.ns.cloudflare.com dns.cloudflare`

📌 Glue Records Collected

Total: 12

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

Analysis

IP Addresses

jpdevsecops.com points to the four IP addresses 104.21.50.42, 172.67.200.188, 2606:4700:3031::6815:322a and 2606:4700:3033::ac43:c8bc.

bawangtoto.vip, djbetplay.com, mail.voiceofpeopletoday.com and two other host names share IP numbers with jpdevsecops.com.

Name Servers

jpdevsecops.com is served by two delegated name servers, blakely.ns.cloudflare.com and lamar.ns.cloudflare.com.

jpdevsecops.com uses the same name servers as several other domains — among them kamari.store, river-97i.pages.dev, samuraizd.workers.dev and two more.

There is at least partial name server overlap between jpdevsecops.com and other domains — wzrost.pages.dev, slbv8y4bna.workers.dev, showsnextstop.com and two more among them.

These name servers are routinely deployed together with the name servers phoenix.ns.cloudflare.com.

Hostnames that resolve to 6 IP addresses:

blakely.ns.cloudflare.com carries IP addresses 108.162.194.96, 162.159.38.96 and 172.64.34.96, with 3 other addresses beyond those.

lamar.ns.cloudflare.com carries IP addresses 108.162.195.142, 162.159.44.142 and 172.64.35.142, with 3 other addresses beyond those.

Mail Servers

Mail for jpdevsecops.com is handled by a single mail server, smtp.google.com.

jpdevsecops.com uses an identical mail server configuration to several other domains — among them claimapproved.ai, onvultrex.info, maintenanceflowbuilding.com and two more.

jpdevsecops.com has at least partial mail server overlap with other domains such as oneworksgo.co, linksanddiamonds.com, lighthouseforchrist.org and two more.

These mail servers commonly appear together with aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two other mail servers.

smtp.google.com resolves to 9 IP addresses — 142.251.163.26, 142.251.167.26, 142.251.167.27 and 6 others.