Skip to security report
Recorded security signals
Stored VirusTotal result: 17/92 engines flagged. malicious: 14. suspicious: 3. Analysis time (as stored): 2026-11-01T23:38:18Z. Retrieved (as stored): 2026-11-04T20:37:24Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
tokex.digital favicon

tokex.digital

In short

On 2026-07-20, tokex.digital displayed a dark-themed landing page branded "Tokex" with the headline "Tokex — Premium AI-Driven Trading Automation." The page describes an AI-enhanced trading assistant with automated strategies, proactive monitoring, and governance-ready controls, alongside feature cards for around-the-clock oversight, audit-ready history, and policy-aligned controls. A "Create Your Tokex Account" panel on the right collects given name, family name, email address, and phone number, with a "JOIN TOKEX NOW" button and links to Terms and Conditions, Privacy Policy, and Cookie Policy.

“Tokex | AI Trading Platform | Official Website”

Registrar
United StatesSpaceship
Resolved IP
Netherlands185.62.57.10Snel.com B.V. · CDN
Registered
Mar 26, 2026
First observed
Nov 4, 2026
PhishDestroy assessment Critical
95/100
Evidence score
Availability Last known active Latest stored reachability observation Observed URLScan
VirusTotal detections: 17/92
VirusTotal
engine detections ·
OTX
community references
URLScan
engine verdict · score 97
Cloudflare Radar
Page captures
open gallery
Domain age
registered 2026-03-26 according to WHOIS · source data differ
OTX: 3 refs Nov 4, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded tokex.digital on 2026-11-04. Stored VirusTotal result: 17/92 engines flagged. malicious: 14. suspicious: 3. Analysis time (as stored): 2026-11-01T23:38:18Z. Retrieved (as stored): 2026-11-04T20:37:24Z. Risk: critical (95/100). Registrar: Spaceship. Status: Last known active. Hosting: Snel.com B.V. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
17 / 92
Hosting
Netherlands185.62.57.10Snel.com B.V. · CDN
Registrar
United StatesSpaceship
Registered
Mar 26, 2026
OTX
3 community refs
Page captures
2

Capture recorded with this analysis · URLScan · 2026-07-20T09:30:53Z
SHA-256: b8f85802a4ac954248ea9b0a5d504fb8335785f0647c7ae4ef953db91f1b39a6

PhishDestroy analysis, reviewed version

On 2026-07-20, tokex.digital displayed a dark-themed landing page branded "Tokex" with the headline "Tokex — Premium AI-Driven Trading Automation." The page describes an AI-enhanced trading assistant with automated strategies, proactive monitoring, and governance-ready controls, alongside feature cards for around-the-clock oversight, audit-ready history, and policy-aligned controls. A "Create Your Tokex Account" panel on the right collects given name, family name, email address, and phone number, with a "JOIN TOKEX NOW" button and links to Terms and Conditions, Privacy Policy, and Cookie Policy.

The stored VirusTotal domain result reports 17 detections out of 92 engines. DNS8 reported "suspicious"; ESET reported "suspicious".

Source evidenceVirusTotal 17 / 92 · OTX 3 references 7 sources

VirusTotal

17 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
44
Malicious
14
Suspicious
3
Undetected
31

Vendor labels

DNS8
suspicious
ESET
suspicious
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
phishing
CyRadar
phishing
Webroot
malicious
Fortinet
phishing
SOCRadar
phishing
Kaspersky
phishing
Seclookup
malicious
Gridinsoft
suspicious
BitDefender
phishing
Chong Lua Dao
malicious
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Categories

Sophos
phishing and fraud
Webroot
Phishing and Other Frauds
alphaMountain.ai
Phishing (alphaMountain.ai)
Forcepoint ThreatSeeker
phishing and other frauds

Created

Updated

First seen

DNS records

  • TTL, seconds
    21600
    Type
    NS
    Value
    kenia.ns.cloudflare.com
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    curt.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    185.62.57.10
  • TTL, seconds
    21600
    Type
    NS
    Value
    curt.ns.cloudflare.com

DNS records observed

JARM fingerprint

40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319

Certificate

Subject alternative names
  • tokex.digital
Issuer
ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2
Serial
f4a90bbd0bc9211b7d5ceaf723a5a6d6
SHA-256
201dd45e90342758496108e8d9086d2e620ad2bf2e7e3b055eaa6692b48f7a0b
Subject
tokex.digital
Valid until
Valid from

Registry data (RDAP)

Status
  • client transfer prohibited
Registry events
Last changed
Registration
Registrar expiration
Last RDAP database update
Registrar
Spaceship, Inc.
Registrar IANA ID
3862
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 44,
    "malicious": 14,
    "suspicious": 3,
    "undetected": 31
}
Vendor labels
{
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "Sophos": "phishing and fraud",
    "Webroot": "Phishing and Other Frauds",
    "alphaMountain.ai": "Phishing (alphaMountain.ai)",
    "Forcepoint ThreatSeeker": "phishing and other frauds"
}
Created
2026-03-26T00:00:00Z
Updated
2026-03-27T00:00:00Z
First seen
2024-03-04T23:17:40Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "kenia.ns.cloudflare.com"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "curt.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "185.62.57.10"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "curt.ns.cloudflare.com"
    }
]
Dns at
2026-11-01T23:38:31Z
Jarm
40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319
Certificate
{
    "san": [
        "tokex.digital"
    ],
    "issuer": "ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2",
    "serial": "f4a90bbd0bc9211b7d5ceaf723a5a6d6",
    "sha256": "201dd45e90342758496108e8d9086d2e620ad2bf2e7e3b055eaa6692b48f7a0b",
    "subject": "tokex.digital",
    "valid_to": "2026-12-27T23:59:59Z",
    "valid_from": "2026-09-28T00:00:00Z"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "last changed": "2026-08-20T17:18:28Z",
        "registration": "2026-03-26T11:33:38Z",
        "registrar expiration": "2027-03-26T11:33:38Z",
        "last update of RDAP database": "2026-10-30T08:08:13Z"
    },
    "registrar": "Spaceship, Inc.",
    "registrar_iana_id": "3862"
}
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

source
VirusTotal
scope
unknown
result_state
observed
numerator
17
denominator
92
malicious
null
suspicious
null
vendors
["alphaMountain.ai","BitDefender","Chong Lua Dao","CyRadar","DNS8","ESET","Forcepoint ThreatSeeker","Fortinet","G-Data","Gridinsoft","Kaspersky","Lionic","Seclookup","SOCRadar","Sophos","VIPRE","Webroot"]
observed_at
2026-11-01 23:38:18
checked_at
2026-11-04 21:37:27
fetched_at
2026-11-04 20:37:28
time_basis
as stored; legacy timezone not established

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Report ID

4841940c-cd0a-4670-be73-349d88ec4457

Final URL

https://tokex.digital/

HTTP response

200

Navigation history

  • URL
    https://tokex.digital/
    Status
    200

DOM structure hash

8355e0db3119c09ae49e974557eafcb80296ed1efa3b7b8947cd6002630e1b65

Document hash

666cbacd8fa5c64f7682b1f8e99a33d280998e4e3753d107a7f043ca988684f8

Phishing classifier result

  • phishing

Domain risk categories

  • Malware
  • Security threats
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    tokex.digital
    Type
    A
    Value
    185.62.57.10

DNSSEC valid

No

IP address

127.0.1.24

127.0.1.24 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Verdict

Tags
  • malware
Malicious
Yes
Categories
  • malware
Original source fields · JSON
Uuid
4841940c-cd0a-4670-be73-349d88ec4457
Final url
https://tokex.digital/
Status
200
History
[
    {
        "url": "https://tokex.digital/",
        "status": 200
    }
]
DOM structure hash
8355e0db3119c09ae49e974557eafcb80296ed1efa3b7b8947cd6002630e1b65
Document hash
666cbacd8fa5c64f7682b1f8e99a33d280998e4e3753d107a7f043ca988684f8
Phishing v2
[
    "phishing"
]
Domain risks
[
    "Malware",
    "Security threats",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "tokex.digital",
        "type": "A",
        "value": "185.62.57.10"
    }
]
Dnssec valid
false
Ip
127.0.1.24

127.0.1.24 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Verdict
{
    "tags": [
        "malware"
    ],
    "malicious": true,
    "categories": [
        "malware"
    ]
}
Separate stored summary: Not recorded · observation date not recorded

This summary differs from the dated scan above. It is retained for provenance and does not override the selected source observation.

verdict
null
categories
[]
observed_at
null
source_path
phishdestroy.technologies.cf_radar
scope
Separate stored summary; an absent observation date is not evidence of a clean scan.

URLScan

Malicious · engine verdict · score 97

SHA-256 286fd9c6eef10b3eef8966f9d595cae399da04abc554a26bc3e44545258da4f2

Open report
URLScanOriginal source recordObserved: 22 fields

Observed: · Retrieved:

Report ID

019f7edd-18f0-757c-9f29-c4d22f579805

Final URL

https://tokex.digital/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://tokex.digital/
    From
    http://tokex.digital/
    Status
    307
  • To
    http://tokex.digital/
    From
    https://tokex.digital/
    Status
    307
  • To
    https://tokex.digital/
    From
    http://tokex.digital/
    Status
    301

IP address

188.114.96.3

Contacted domains

  • cdnjs.cloudflare.com
  • cdn.jsdelivr.net
  • fonts.googleapis.com
  • static.cloudflareinsights.com
  • static.cloudflare.com

Contacted IP addresses

  • 104.17.208.5
  • 172.217.208.95
  • 104.17.24.14
  • 188.114.96.3
  • 188.114.97.3

Autonomous systems (ASN)

  • 13335
  • 15169

Server countries

  • US

Document hash

286fd9c6eef10b3eef8966f9d595cae399da04abc554a26bc3e44545258da4f2

Script hashes

  • ccf00d1923b0131a10e0c6d26f95e5dee6ebf8621a27e83c5a2f68a2e0093142

JavaScript globals

  • LANG_MSGS
  • ClientJS
  • _w0jmllo6
  • toggleTermsPopup
  • __cfQR
  • __cfRLUnblockHandlers

Cookies

  • entry_url

TLS session and certificate

Subject alternative names
  • tokex.digital
Cipher
AES_128_GCM
Issuer
WE1
Subject
tokex.digital
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

1064

Differs from the registration date in WHOIS (2026-03-26), which gives 115 days on the scan date 2026-07-20. The two sources disagree; both values are kept as recorded.

Registered domain age, days

1064

Differs from the registration date in WHOIS (2026-03-26), which gives 115 days on the scan date 2026-07-20. The two sources disagree; both values are kept as recorded.

Certificate age, days

56

Certificate validity, days

90

Page requests

19

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
97
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
cloudflare
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=31536000; includeSubDomains; preload
Content-security-policy
default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://static.cloudflare.com https://cdn.jsdelivr.net; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://cdnjs.
X-frame-options
SAMEORIGIN
X-content-type-options
nosniff
Referrer-policy
strict-origin-when-cross-origin
Permissions-policy
camera=(), microphone=(), geolocation=()
Cross-origin-opener-policy
same-origin
Link
<https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.1/css/fontawesome.min.css>; rel=preload; as=style; crossorigin, <https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.1/css/solid.min.css>;
Original source fields · JSON
Uuid
019f7edd-18f0-757c-9f29-c4d22f579805
Final url
https://tokex.digital/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://tokex.digital/",
        "from": "http://tokex.digital/",
        "status": 307
    },
    {
        "to": "http://tokex.digital/",
        "from": "https://tokex.digital/",
        "status": 307
    },
    {
        "to": "https://tokex.digital/",
        "from": "http://tokex.digital/",
        "status": 301
    }
]
Ip
188.114.96.3
Contacted domains
[
    "cdnjs.cloudflare.com",
    "cdn.jsdelivr.net",
    "fonts.googleapis.com",
    "static.cloudflareinsights.com",
    "static.cloudflare.com"
]
Contacted IP addresses
[
    "104.17.208.5",
    "172.217.208.95",
    "104.17.24.14",
    "188.114.96.3",
    "188.114.97.3"
]
Asns
[
    "13335",
    "15169"
]
Countries
[
    "US"
]
Document hash
286fd9c6eef10b3eef8966f9d595cae399da04abc554a26bc3e44545258da4f2
Script hashes
[
    "ccf00d1923b0131a10e0c6d26f95e5dee6ebf8621a27e83c5a2f68a2e0093142"
]
Globals
[
    "LANG_MSGS",
    "ClientJS",
    "_w0jmllo6",
    "toggleTermsPopup",
    "__cfQR",
    "__cfRLUnblockHandlers"
]
Cookies
[
    "entry_url"
]
Tls
{
    "san": [
        "tokex.digital"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "tokex.digital",
    "protocol": "TLS 1.3",
    "valid_to": "2026-08-23T06:51:17Z",
    "valid_from": "2026-05-25T05:51:28Z"
}
Domain age days
1064

Differs from the registration date in WHOIS (2026-03-26), which gives 115 days on the scan date 2026-07-20. The two sources disagree; both values are kept as recorded.

Apex age days
1064

Differs from the registration date in WHOIS (2026-03-26), which gives 115 days on the scan date 2026-07-20. The two sources disagree; both values are kept as recorded.

Tls age days
56
Tls valid days
90
Requests
19
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 97,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=31536000; includeSubDomains; preload",
    "content-security-policy": "default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://static.cloudflare.com https://cdn.jsdelivr.net; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://cdnjs.",
    "x-frame-options": "SAMEORIGIN",
    "x-content-type-options": "nosniff",
    "referrer-policy": "strict-origin-when-cross-origin",
    "permissions-policy": "camera=(), microphone=(), geolocation=()",
    "cross-origin-opener-policy": "same-origin",
    "link": "<https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.1/css/fontawesome.min.css>; rel=preload; as=style; crossorigin, <https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.1/css/solid.min.css>; "
}
Separate monitor record · date not recorded

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

record_source
domain_monitor.urlscan
uuid
019f7edd-18f0-757c-9f29-c4d22f579805
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

3 community references

Open report

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

40 / 100 · heuristic score · 1 brand reference · 0 classifications

Open report
Separate monitor score · 40 / 100 · 2026-11-04T20:42:34Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
40
analyzed_at
2026-11-04T20:42:34Z
source_timestamp
2026-11-04 21:42:34
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
tokex.digital — Tokex AI-Driven Trading Automation Sign-Up Page
ai_description
PhishDestroy records tokex.digital as a page presenting Tokex AI-driven trading automation and a Create Your Tokex Account registration form.
ai_summary
On 2026-07-20, tokex.digital displayed a dark-themed landing page branded "Tokex" with the headline "Tokex — Premium AI-Driven Trading Automation." The page describes an AI-enhanced trading assistant with automated strategies, proactive monitoring, and governance-ready controls, alongside feature cards for around-the-clock oversight, audit-ready history, and policy-aligned controls. A "Create Your Tokex Account" panel on the right collects given name, family name, email address, and phone number, with a "JOIN TOKEX NOW" button and links to Terms and Conditions, Privacy Policy, and Cookie Policy. The stored VirusTotal domain result reports 17 detections out of 92 engines. DNS8 reported "suspicious"; ESET reported "suspicious".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-11-04 21:40:41
revision
ea3f42a3759a6919ed549ce1f47e5cee062e889b0be3a115c24fd451b2bf6b3c
mode
reviewed
interpretation
Selected public package; text generation time is separate from source observation dates.

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 24 fields

Mail configuration

SPF lookups
0

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
1
Archived days
2
Snapshots per day
0.17
Average page size, bytes
12914

Crawler rules

User agents
  • *
Present
Yes
Sitemap URLs
  • https://tokex.digital/sitemap.xml

Sitemap

Present
Yes
URL count
175

Page title and metadata

Page title
Tokex | AI Trading Platform | Official Website
Indexing directives
index, follow
Theme color
#0d0d12
Description
Tokex delivers AI-powered automation for trading bots, streamlined execution workflows, and robust risk controls to empower decisive, data-driven decisions.
Canonical URL
https://tokex.digital/

Trackers

Requests
23
Observed services
  • Name
    Cloudflare
    Company
    Cloudflare
    Country
    US
    Category
    Hosting
    Requests
    6
  • Name
    Google Fonts
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Google Static
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    4
  • Name
    jsDelivr
    Company
    jsDelivr
    Category
    Hosting
    Requests
    3

Forms and mixed content

Scripts without SRI
  • https://cdn.jsdelivr.net/npm/intl-tel-input@23/build/js/intlTelInput.min.js
Third-party scripts
1

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
22
TLS
29
Waiting
26
Connection
20
Download
31
Response time, ms
128

TLS connection

ALPN
h2
Cipher
TLS_CHACHA20_POLY1305_SHA256
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
OCSP stapling
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443

Carbon estimate

Bytes
46716
CO₂, grams
0.0017
Cleaner than, %
38

DNS servers

Nameservers
  • IP address
    173.245.59.94
    Host
    curt.ns.cloudflare.com
  • IP address
    108.162.194.93
    Host
    kenia.ns.cloudflare.com
DNS zone
tokex.digital

Location

IP address
185.62.57.10
ASN
62370
Organization
Snel.com B.V.
City
Rotterdam
Country
NL

TLS certificate

Issuer
ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2
Subject
tokex.digital

DNS records

A
  • 185.62.57.10
NS
  • curt.ns.cloudflare.com
  • kenia.ns.cloudflare.com
SOA
Primary nameserver
curt.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2416874830
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
no-referrer-when-downgrade
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
185.62.57.10
IP version
4

Redirects

Redirect chain
  • https://tokex.digital

Technology stack

Technologies
  • Cloudflare
  • Cloudflare Turnstile
  • ClientJS
  • Priority Hints
  • jsDelivr
  • Google Font API
  • Font Awesome
  • cdnjs
  • Open Graph
  • HTTP/3

Page links

Internal links
49

HTTP headers

Response headers
Content-type
text/html; charset=utf-8
Referrer-policy
no-referrer-when-downgrade
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-21T04:33:02Z",
    "first": "2026-10-15T04:22:34Z",
    "changes": 1,
    "days_archived": 2,
    "scans_per_day": 0.17,
    "avg_page_bytes": 12914
}
Crawler rules
{
    "agents": [
        "*"
    ],
    "present": true,
    "sitemaps": [
        "https://tokex.digital/sitemap.xml"
    ]
}
Sitemap
{
    "present": true,
    "url_count": 175
}
Page title and metadata
{
    "title": "Tokex | AI Trading Platform | Official Website",
    "robots": "index, follow",
    "themeColor": "#0d0d12",
    "description": "Tokex delivers AI-powered automation for trading bots, streamlined execution workflows, and robust risk controls to empower decisive, data-driven decisions.",
    "canonicalUrl": "https://tokex.digital/"
}
Trackers
{
    "requests": 23,
    "trackers": [
        {
            "name": "Cloudflare",
            "company": "Cloudflare",
            "country": "US",
            "category": "Hosting",
            "requests": 6
        },
        {
            "name": "Google Fonts",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 1
        },
        {
            "name": "Google Static",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 4
        },
        {
            "name": "jsDelivr",
            "company": "jsDelivr",
            "category": "Hosting",
            "requests": 3
        }
    ]
}
Forms and mixed content
{
    "no_sri": [
        "https://cdn.jsdelivr.net/npm/intl-tel-input@23/build/js/intlTelInput.min.js"
    ],
    "third_party_scripts": 1
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 22,
        "tls": 29,
        "wait": 26,
        "connect": 20,
        "download": 31
    },
    "response_ms": 128
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_CHACHA20_POLY1305_SHA256",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "ocsp_stapled": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 46716,
    "co2_grams": 0.0017,
    "cleaner_than": 38
}
Dns server
{
    "ns": [
        {
            "ip": "173.245.59.94",
            "host": "curt.ns.cloudflare.com"
        },
        {
            "ip": "108.162.194.93",
            "host": "kenia.ns.cloudflare.com"
        }
    ],
    "zone": "tokex.digital"
}
Location
{
    "ip": "185.62.57.10",
    "asn": "62370",
    "org": "Snel.com B.V.",
    "city": "Rotterdam",
    "country": "NL"
}
Ssl
{
    "issuer": "ZeroSSL GmbH / ZeroSSL ECC DV SSL CA 2",
    "subject": "tokex.digital"
}
DNS records
{
    "A": [
        "185.62.57.10"
    ],
    "NS": [
        "curt.ns.cloudflare.com",
        "kenia.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"curt.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2416874830, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": "no-referrer-when-downgrade",
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "185.62.57.10",
    "family": 4
}
Redirects
{
    "chain": [
        "https://tokex.digital"
    ]
}
Tech stack
{
    "technologies": [
        "Cloudflare",
        "Cloudflare Turnstile",
        "ClientJS",
        "Priority Hints",
        "jsDelivr",
        "Google Font API",
        "Font Awesome",
        "cdnjs",
        "Open Graph",
        "HTTP/3"
    ]
}
Page links
{
    "internal_count": 49
}
HTTP headers
{
    "headers": {
        "content-type": "text/html; charset=utf-8",
        "referrer-policy": "no-referrer-when-downgrade"
    }
}

Questions about tokex.digital

Is tokex.digital legit?

PhishDestroy rates tokex.digital as critical risk (95/100) from the recorded evidence; it was first recorded on 2026-11-04. Stored VirusTotal result: 17/92 engines flagged. malicious: 14. suspicious: 3. Analysis time (as stored): 2026-11-01T23:38:18Z. Retrieved (as stored): 2026-11-04T20:37:24Z. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is tokex.digital safe to connect a wallet?

This report does not record which wallet requests tokex.digital makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used tokex.digital?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Last checked

Stored Capture · 2 captures

All capture links and hashes (2)
Observed page title
Tokex | AI Trading Platform | Official Website
Automated brand references
Across
TLS Certificate
Issued by WE1

Domain details

Domain
IP Context Netherlands185.62.57.10 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-11all-domainsblocklistcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar Spaceship US(US)
RegistrationCreated Mar 26, 2026 (223d)
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedNov 4, 2026
DOM Analysisanalyzed Nov 4, 2026score 40/1001 brand signal
Submitted URLhttp://tokex.digital/
Favicon Hash
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Netherlands185.62.57.10
Network ASN
AS62370
Organization
Snel.com B.V.
Observed location
NetherlandsRotterdam, NL
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • curt.ns.cloudflare.com
  • kenia.ns.cloudflare.com

SOA

  • nsname: curt.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2416874830
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

Location describes the IP network.

TLS certificate

Issuer
WE1
Valid from
2026-05-25 05:51:28
Valid until
2026-08-23 06:51:17
Hostname coverage
Stored certificate expired or unverified
Validity
Stored certificate expired
Collection source
PhishDestroy collector
Certificate fingerprint201dd45e90342758496108e8d9086d2e620ad2bf2e7e3b055eaa6692b48f7a0b
Certificate names · 1 SAN
  • tokex.digital

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Report This Domain Submit evidence & help protect others

VirusTotal Analysis

17 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
DNS8
ESET
VIPRE
G-Data
Lionic
Sophos
CyRadar
Webroot
Fortinet
SOCRadar
Kaspersky
Seclookup
Gridinsoft
BitDefender
Chong Lua Dao
alphaMountain.ai
Forcepoint ThreatSeeker
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of tokex.digital · checked Nov 4, 2026

76
Needs Work
Performance
FCP
0.79 s
First Contentful Paint
LCP
3.02 s
Largest Contentful Paint
CLS
0.333
Cumulative Layout Shift
TBT
147 ms
Total Blocking Time
SI
1.84 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor

Captured network requests

Network requests: 19 SHA-256 hashes: 17 URLScan scan:

Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-04 20:02 UTC.

Open this scan on URLScan 019f7edd-18f0-757c-9f29-c4d22f579805 ↗

All retained availability observations1

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-04 21:02:06.106157
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · in progress

Recorded events: 9. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    tokex.digital detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · OTX Community References · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 7 of 7
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 97
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • VirusTotal
    Detections recorded on VirusTotal: 17/92
  • OTX Community References
    Community publication references on AlienVault OTX: 3. References are not vendor verdicts and are excluded from the evidence score.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

5 entries
  1. AlienVault OTX

    3 community references

    View source
  2. Cloudflare Radar

    Phishing

    View source
  3. Added to PhishDestroy

    tokex.digital

    View source
  4. VirusTotal

    17/92 engine detections

    View source
  5. URLScan

    Malicious · engine verdict · score 97

    View source
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

tokex.digital

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Official reporting routes

More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

Template-based draft • optional AI wording assistance requires separate consent

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including tokex.digital)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/tokex.digital"
  title="PhishDestroy threat report for tokex.digital"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>