🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`complex64.dev`

DNSSEC	⚠️ Not signed
NS	`kirk.ns.cloudflare.com` ⭐
		A	2606:4700:58::adf5:3bc0^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kirk.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c1c0^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`kirk.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:21c0^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`kirk.ns.cloudflare.com`
		A	108.162.193.192^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kirk.ns.cloudflare.com`
		A	172.64.33.192^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kirk.ns.cloudflare.com`
		A	173.245.59.192^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kirk.ns.cloudflare.com`
NS	`veda.ns.cloudflare.com`
		A	2606:4700:50::a29f:2693^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`veda.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c293^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`veda.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2293^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`veda.ns.cloudflare.com`
		A	108.162.194.147^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`veda.ns.cloudflare.com`
		A	162.159.38.147^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`veda.ns.cloudflare.com`
		A	172.64.34.147^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`veda.ns.cloudflare.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c19::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bk-in-f27.1e100.net`
		A	192.179.24.26^{🇺🇸 Google192.178.0.0/15}
			PTR	`rz-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::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.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::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.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.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`google-site-verification=3HQzuLfrVSw6HrQnSZCcRmg0oKh4PHAhKsAUDMjfbUU`
TXT	`v=spf1 include:_spf.google.com -all`
SOA	`kirk.ns.cloudflare.com`dns@cloudflare.com serial=2413416802

`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

complex64.com

complex64.dev

complex64.ru

Previous names

Next names

DNS History

7 records (7 active, 0 former)

●NSkirk.ns.cloudflare.com2026-08-30 → 2026-09-14 · 2 obs

● 2026-08-30 06:11:00
● 2026-09-14 15:30:06

●NSveda.ns.cloudflare.com2026-08-30 → 2026-09-14 · 2 obs

● 2026-08-30 06:11:00
● 2026-09-14 15:30:06

●MXalt1.aspmx.l.google.com2026-08-30 → 2026-09-14 · 2 obs

● 2026-08-30 06:11:00
● 2026-09-14 15:30:06

●MXalt2.aspmx.l.google.com2026-08-30 → 2026-09-14 · 2 obs

● 2026-08-30 06:11:00
● 2026-09-14 15:30:06

●MXalt3.aspmx.l.google.com2026-08-30 → 2026-09-14 · 2 obs

● 2026-08-30 06:11:00
● 2026-09-14 15:30:06

●MXalt4.aspmx.l.google.com2026-08-30 → 2026-09-14 · 2 obs

● 2026-08-30 06:11:00
● 2026-09-14 15:30:06

●MXaspmx.l.google.com2026-08-30 → 2026-09-14 · 2 obs

● 2026-08-30 06:11:00
● 2026-09-14 15:30:06

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
dev	ns-tld2.charlestonroadregistry.com, ns-tld1.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com...	-
complex64.dev	veda.ns.cloudflare.com, kirk.ns.cloudflare.com	-

✅ Authoritative Response

Server:173.245.59.192

NS records: veda.ns.cloudflare.com, kirk.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for complex64.dev (unsigned zone)

⏱️ Timing

Total: 2813ms | Queries: -

📄 Records

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

Analysis

Name Servers

complex64.dev uses two name servers for its delegation: kirk.ns.cloudflare.com and veda.ns.cloudflare.com.

complex64.dev has the same name server delegation as a number of other domains, such as workupperhandcreative.com, getacademyfrontline.com, pensionconsultantseasy.com and two more.

There is at least partial name server overlap between complex64.dev and other domains — taiwanfood54.shop, benoymichael.workers.dev, reltis.workers.dev and two more among them.

These name servers tend to appear in combination with the name servers rose.ns.cloudflare.com, ganz.ns.cloudflare.com, garrett.ns.cloudflare.com and anuj.ns.cloudflare.com.

Host names resolving to 6 IP numbers:

Hostname kirk.ns.cloudflare.com directs to 108.162.193.192, 172.64.33.192 and 173.245.59.192 along with 3 other IP addresses.

Hostname veda.ns.cloudflare.com directs to 108.162.194.147, 162.159.38.147 and 172.64.34.147 along with 3 other IP addresses.

Mail Servers

complex64.dev has five mail servers, which are aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

complex64.dev shares at least some of its mail servers with other domains — for example lhvcamp.org, openairfitness.info, digitalsrini.in and two more.

It is common for these mail servers to co-occur with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com as mail servers.

Hosts with two IP numbers each:

aspmx.l.google.com directs traffic to 192.179.24.26 and 2607:f8b0:4004:c19::1b.

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::1a.

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

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