🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`nexttoken.app`

DNSSEC	⚠️ Not signed
A	2606:4700:3031::ac43:a5d4^{🇺🇸 Cloudflare2606:4700:3031::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3035::6815:39c2^{🇺🇸 Cloudflare2606:4700:3035::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.57.194^{Cloudflare104.21.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.165.212^{🇺🇸 Cloudflare172.67.160.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`anna.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3a66^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`anna.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c066^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`anna.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2066^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`anna.ns.cloudflare.com`
		A	108.162.192.102^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`anna.ns.cloudflare.com`
		A	172.64.32.102^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`anna.ns.cloudflare.com`
		A	173.245.58.102^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`anna.ns.cloudflare.com`
NS	`pete.ns.cloudflare.com`
		A	2606:4700:58::adf5:3b88^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`pete.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c188^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`pete.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2188^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`pete.ns.cloudflare.com`
		A	108.162.193.136^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`pete.ns.cloudflare.com`
		A	172.64.33.136^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`pete.ns.cloudflare.com`
		A	173.245.59.136^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`pete.ns.cloudflare.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c23::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadrs-in-f27.1e100.net`
		A	142.251.179.26^{🇺🇸 Google142.251.179.0/24}
			PTR	`pd-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1a^{🇨🇱 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::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=oKQEM094RLdfinakR7T5iwOmSovIUCYTaVowpO38El4`
TXT	`v=spf1 include:_spf.google.com ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.57.194, 172.67.165.212
		IPv6 hints	2606:4700:3031::ac43:a5d4, 2606:4700:3035::6815:39c2
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=47, name=cloudflare-ech.com
SOA	`anna.ns.cloudflare.com`dns@cloudflare.com serial=2412200590

`app`

	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=101427

🔒 HSTS Preload (+subdomains)

Same first word

nexttoken.cloud

nexttoken.tech

nexttoken.app

nexttoken.io

nexttoken.build

Similar names

teknonext.net

kontexten.com

tokennext.com

Previous names

Next names

DNS History

11 records (11 active, 0 former)

●NSanna.ns.cloudflare.com2026-08-19 → 2026-08-21 · 2 obs

● 2026-08-19 19:21:32
● 2026-08-21 03:14:40

●NSpete.ns.cloudflare.com2026-08-19 → 2026-08-21 · 2 obs

● 2026-08-19 19:21:32
● 2026-08-21 03:14:40

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

● 2026-08-19 19:21:32
● 2026-08-21 03:14:40

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

● 2026-08-19 19:21:32
● 2026-08-21 03:14:40

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

● 2026-08-19 19:21:32
● 2026-08-21 03:14:40

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

● 2026-08-19 19:21:32
● 2026-08-21 03:14:40

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

● 2026-08-19 19:21:32
● 2026-08-21 03:14:40

●A104.21.57.1942026-08-19 → 2026-08-21 · 2 obs

● 2026-08-19 19:21:32
● 2026-08-21 03:14:40

●A172.67.165.2122026-08-19 → 2026-08-21 · 2 obs

● 2026-08-19 19:21:32
● 2026-08-21 03:14:40

●A2606:4700:3031::ac43:a5d42026-08-19 → 2026-08-21 · 2 obs

● 2026-08-19 19:21:32
● 2026-08-21 03:14:40

●A2606:4700:3035::6815:39c22026-08-19 → 2026-08-21 · 2 obs

● 2026-08-19 19:21:32
● 2026-08-21 03:14:40

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
app	ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com, ns-tld4.charlestonroadregistry.com...	10 records
nexttoken.app	anna.ns.cloudflare.com, pete.ns.cloudflare.com	-

✅ Authoritative Response

Server:172.64.33.136

NS records: anna.ns.cloudflare.com, pete.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for nexttoken.app (unsigned zone)

⏱️ Timing

Total: 1836ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.57.194, 172.67.165.212`
AAAA	2	`2606:4700:3035::6815:39c2, 2606:4700:3031::ac43:a5d4`
NS	2	`anna.ns.cloudflare.com, pete.ns.cloudflare.com`
MX	5	`aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)...`
TXT	2	`google-site-verification=oKQEM094RLdfina, v=spf1 include:_spf.google.com ~all`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`anna.ns.cloudflare.com dns.cloudflare.co`

📌 Glue Records Collected

Total: 10

Out-of-bailiwick: 10 (ns-tld1.charlestonroadregistry.com, ns-tld2.charlestonroadregistry.com, ns-tld3.charlestonroadregistry.com...)

Analysis

IP Addresses

nexttoken.app resolves to four IP addresses: 104.21.57.194, 172.67.165.212, 2606:4700:3031::ac43:a5d4 and 2606:4700:3035::6815:39c2.

lara-bet-casino-de.de, happycitadelstream.pro, upchn.com and two other host names share IP numbers with nexttoken.app.

Name Servers

Two name servers handle the delegation for nexttoken.app: anna.ns.cloudflare.com and pete.ns.cloudflare.com.

nexttoken.app uses the same name servers as several other domains — among them paulbdelaat.nl, dastrader.mobi, udemycdn3.cn and two more.

nexttoken.app has at least partial name server overlap with other domains, such as walldorf.consulting, r7c2u.com, jaco.it and two others.

It is common to find these name servers paired with the name servers cash.ns.cloudflare.com.

Hostnames that resolve to 6 IP addresses:

anna.ns.cloudflare.com resolves to 108.162.192.102, 172.64.32.102 and 173.245.58.102 among others, with 3 other IP addresses in total.

pete.ns.cloudflare.com resolves to 108.162.193.136, 172.64.33.136 and 173.245.59.136 among others, with 3 other IP addresses in total.

Mail Servers

nexttoken.app is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

nexttoken.app has at least partial mail server overlap with other domains such as totalcareforyou.com, vicspan.in, lootcakes.com and two more.

These mail servers commonly co-occur with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.

Hostnames that resolve to two IP addresses:

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

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

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

alt3.aspmx.l.google.com resolves to two addresses: 192.178.223.27 and 2a00:1450:4009:c0f::1a.

alt4.aspmx.l.google.com resolves to two addresses: 172.253.157.26 and 2a00:1450:400c:c23::1a.