🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`securecube.dev`

DNSSEC	⚠️ Not signed
NS	`ashley.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3a47^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ashley.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c047^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`ashley.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2047^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`ashley.ns.cloudflare.com`
		A	108.162.192.71^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	172.64.32.71^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
		A	173.245.58.71^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`rudy.ns.cloudflare.com`
		A	2606:4700:58::adf5:3be5^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rudy.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c1e5^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`rudy.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:21e5^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`rudy.ns.cloudflare.com`
		A	108.162.193.229^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rudy.ns.cloudflare.com`
		A	172.64.33.229^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rudy.ns.cloudflare.com`
		A	173.245.59.229^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rudy.ns.cloudflare.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c2d::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`ry-in-f26.1e100.net`
		A	192.178.155.26^{🇺🇸 Google192.178.155.0/24}
			PTR	`yuiadrs-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.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
TXT	`google-site-verification=1cjjToemWhXthIPr_gMCP1jdNayEclsmLRbanDPqi98`
TXT	`v=spf1 include:_spf.google.com -all`
SOA	`ashley.ns.cloudflare.com`dns@cloudflare.com serial=2413419928

`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

securecube.dev

securecube.xyz

securecube.net

securecube.com

Similar names

securebecu.serveirc.com

securebecu.myftp.biz

cubesecure.com

Previous names

Next names

DNS History

7 records (7 active, 0 former)

●NSashley.ns.cloudflare.com2026-08-29 → 2026-08-29 · 2 obs

● 2026-08-29 10:06:24
● 2026-08-29 23:39:56

●NSrudy.ns.cloudflare.com2026-08-29 → 2026-08-29 · 2 obs

● 2026-08-29 10:06:24
● 2026-08-29 23:39:56

●MXalt1.aspmx.l.google.com2026-08-29 → 2026-08-29 · 2 obs

● 2026-08-29 10:06:24
● 2026-08-29 23:39:56

●MXalt2.aspmx.l.google.com2026-08-29 → 2026-08-29 · 2 obs

● 2026-08-29 10:06:24
● 2026-08-29 23:39:56

●MXalt3.aspmx.l.google.com2026-08-29 → 2026-08-29 · 2 obs

● 2026-08-29 10:06:24
● 2026-08-29 23:39:56

●MXalt4.aspmx.l.google.com2026-08-29 → 2026-08-29 · 2 obs

● 2026-08-29 10:06:24
● 2026-08-29 23:39:56

●MXaspmx.l.google.com2026-08-29 → 2026-08-29 · 2 obs

● 2026-08-29 10:06:24
● 2026-08-29 23:39:56

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
dev	ns-tld1.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld5.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com...	-
securecube.dev	ashley.ns.cloudflare.com, rudy.ns.cloudflare.com	-

✅ Authoritative Response

Server:173.245.58.71

NS records: ashley.ns.cloudflare.com, rudy.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for securecube.dev (unsigned zone)

⏱️ Timing

Total: 1255ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`ashley.ns.cloudflare.com, rudy.ns.cloudflare.com`
MX	5	`aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)...`
TXT	2	`google-site-verification=1cjjToemWhXthIP, v=spf1 include:_spf.google.com -all`
SOA	1	`ashley.ns.cloudflare.com dns.cloudflare.`

Analysis

Name Servers

securecube.dev uses two name servers for its delegation: ashley.ns.cloudflare.com and rudy.ns.cloudflare.com.

The name server configuration of securecube.dev is shared with other domains, for instance panamescorte.com, alnokhbamarkets.com, schidlaginibosku.pages.dev and two others.

securecube.dev partially shares its NS delegation with several other domains, including offthebone.net, bsmith.xyz, q-h-s.com and two others.

These name servers often co-occur with the name servers brodie.ns.cloudflare.com.

Hosts with 6 IP addresses each:

Hostname ashley.ns.cloudflare.com directs to 108.162.192.71, 172.64.32.71 and 173.245.58.71 along with 3 other IP addresses.

Hostname rudy.ns.cloudflare.com directs to 108.162.193.229, 172.64.33.229 and 173.245.59.229 along with 3 other IP addresses.

Mail Servers

Mail for securecube.dev is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

At least some of the mail servers used by securecube.dev are shared with other domains: voyages123go.ca, student.just.edu.bd, lillavenuecapital.com and two others among them.

These mail servers are often deployed together with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx3.googlemail.com and 3 other mail servers.

Host names pointing to two IP addresses:

aspmx.l.google.com directs traffic to 192.178.155.26 and 2607:f8b0:4004:c2d::1a.

alt1.aspmx.l.google.com directs traffic to 192.178.234.26 and 2800:3f0:4003:c14::1b.

alt2.aspmx.l.google.com directs traffic to 172.253.116.26 and 2a00:1450:400b:c02::1b.

alt3.aspmx.l.google.com directs traffic to 192.178.223.27 and 2a00:1450:4009:c0f::1a.

alt4.aspmx.l.google.com directs traffic to 172.253.157.26 and 2a00:1450:400c:c23::1a.