🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`deploycore.dev`

CNAME	`mindcore.org`
DNSSEC	⚠️ Not signed
A	2606:4700:3031::6815:5fa3^{🇺🇸 Cloudflare2606:4700:3031::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3032::ac43:9208^{🇺🇸 Cloudflare2606:4700:3032::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.95.163^{Cloudflare104.21.80.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.146.8^{🇺🇸 Cloudflare172.67.144.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`chloe.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3a55^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chloe.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c055^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`chloe.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2055^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`chloe.ns.cloudflare.com`
		A	108.162.192.85^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chloe.ns.cloudflare.com`
		A	172.64.32.85^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chloe.ns.cloudflare.com`
		A	173.245.58.85^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`chloe.ns.cloudflare.com`
NS	`trey.ns.cloudflare.com`
		A	2606:4700:58::adf5:3bf2^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`trey.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c1f2^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`trey.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:21f2^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`trey.ns.cloudflare.com`
		A	108.162.193.242^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`trey.ns.cloudflare.com`
		A	172.64.33.242^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`trey.ns.cloudflare.com`
		A	173.245.59.242^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`trey.ns.cloudflare.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1f::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`pd-in-f27.1e100.net`
		A	142.250.31.26^{🇺🇸 Google142.250.31.0/24}
			PTR	`bj-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.26^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f26.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`aspmx2.googlemail.com`⁽¹⁰⁾
		A	2800:3f0:4003:c14::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f27.1e100.net`
MX	`aspmx3.googlemail.com`⁽¹⁰⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
TXT	`v=spf1 include:_spf.google.com ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.95.163, 172.67.146.8
		IPv6 hints	2606:4700:3031::6815:5fa3, 2606:4700:3032::ac43:9208
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=151, name=cloudflare-ech.com
SOA	`chloe.ns.cloudflare.com`dns@cloudflare.com serial=2411923189

`dev`

	DNSSEC	🔒 Signed (DS record present)
	NS	`ns-tld1.charlestonroadregistry.com` ⭐
	NS	`ns-tld2.charlestonroadregistry.com`
	NS	`ns-tld3.charlestonroadregistry.com`
	NS	`ns-tld4.charlestonroadregistry.com`
	NS	`ns-tld5.charlestonroadregistry.com`
	SOA	`ns-tld1.charlestonroadregistry.com`cloud-dns-hostmaster@google.com serial=1

🔒 HSTS Preload (+subdomains)

Same first word

deploycore.net

deploycore.dev

deploycore.website

Similar names

coredeploy.site

poyeldecor.com

codeployer.in

coredeploy.ai

coredeploy.xyz

polydecore.fr

Previous names

Next names

DNS History

8 records (8 active, 0 former)

●NSdns1.registrar-servers.com2026-09-06 → 2026-09-07 · 2 obs

● 2026-09-06 20:52:40
● 2026-09-07 12:05:36

●NSdns2.registrar-servers.com2026-09-06 → 2026-09-07 · 2 obs

● 2026-09-06 20:52:40
● 2026-09-07 12:05:36

●MXalt1.aspmx.l.google.com2026-09-06 → 2026-09-07 · 2 obs

● 2026-09-06 20:52:40
● 2026-09-07 12:05:36

●MXalt2.aspmx.l.google.com2026-09-06 → 2026-09-07 · 2 obs

● 2026-09-06 20:52:40
● 2026-09-07 12:05:36

●MXaspmx.l.google.com2026-09-06 → 2026-09-07 · 2 obs

● 2026-09-06 20:52:40
● 2026-09-07 12:05:36

●MXaspmx2.googlemail.com2026-09-06 → 2026-09-07 · 2 obs

● 2026-09-06 20:52:40
● 2026-09-07 12:05:36

●MXaspmx3.googlemail.com2026-09-06 → 2026-09-07 · 2 obs

● 2026-09-06 20:52:40
● 2026-09-07 12:05:36

●CNAMEmindcore.org2026-09-06 → 2026-09-07 · 2 obs

● 2026-09-06 20:52:40
● 2026-09-07 12:05:36

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
dev	ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com...	-
deploycore.dev	dns2.registrar-servers.com, dns1.registrar-servers.com	-

✅ Authoritative Response

Server:156.154.133.200

NS records: dns2.registrar-servers.com, dns1.registrar-servers.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for deploycore.dev (unsigned zone)

⏱️ Timing

Total: 344ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`dns1.registrar-servers.com, dns2.registrar-servers.com`
MX	5	`aspmx.l.google.com (pri: 1), alt1.aspmx.l.google.com (pri: 5)...`
CNAME	1	`mindcore.org`
SOA	1	`dns1.registrar-servers.com hostmaster.re`

Analysis

IP Addresses

deploycore.dev has four IP addresses: 104.21.95.163, 172.67.146.8, 2606:4700:3031::6815:5fa3 and 2606:4700:3032::ac43:9208.

moneyhub-luninelotor.click, meyvem.az, verybolt.com and two other host names share IP numbers with deploycore.dev.

Name Servers

Two name servers handle the delegation for deploycore.dev: chloe.ns.cloudflare.com and trey.ns.cloudflare.com.

deploycore.dev uses the same name servers as several other domains — among them testmeetingaiclass.workers.dev, stonecastlearmory.co.uk, aprais.com and two more.

deploycore.dev shares at least some of its name servers with other domains, including uwkttezxoqs.pages.dev, gtsketch.com, efterskoletroje.dk and two others.

These name servers are frequently paired with the name servers savanna.ns.cloudflare.com, fish.ns.cloudflare.com and ns61.cloudns.net.

Hostnames that resolve to 6 IP addresses:

chloe.ns.cloudflare.com resolves to 108.162.192.85, 172.64.32.85 and 173.245.58.85 among others, with 3 other IP addresses in total.

trey.ns.cloudflare.com resolves to 108.162.193.242, 172.64.33.242 and 173.245.59.242 among others, with 3 other IP addresses in total.

Mail Servers

Mail for deploycore.dev is handled by five mail servers, namely aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.

deploycore.dev has at least partial mail server overlap with other domains such as marymosher.com, sleepyhug.in, shawstintshop.com and two more.

These mail servers commonly co-occur with mail servers alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt3.aspmx.l.google.com and 3 others.

Hostnames that resolve to two IP addresses:

aspmx2.googlemail.com resolves to two addresses: 192.178.234.27 and 2800:3f0:4003:c14::1b.

aspmx3.googlemail.com resolves to two addresses: 172.253.116.26 and 2a00:1450:400b:c02::1b.

aspmx.l.google.com resolves to two addresses: 142.250.31.26 and 2607:f8b0:4004:c1f::1b.

alt1.aspmx.l.google.com resolves to two addresses: 192.178.234.26 and 2800:3f0:4003:c14::1b.

alt2.aspmx.l.google.com resolves to two addresses: 172.253.116.27 and 2a00:1450:400b:c02::1b.

aspmx2.googlemail.com along with alt1.aspmx.l.google.com each resolve to 2800:3f0:4003:c14::1b IP addresses.

aspmx3.googlemail.com along with alt2.aspmx.l.google.com each resolve to 2a00:1450:400b:c02::1b IP addresses.