Skip to security report
Analytics Dashboard
Recorded security signals
VirusTotal: result unavailable for this observation. Listed by external blocklists: ScamSniffer. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
capital.tokenizeae.com favicon

capital.tokenizeae.com

In short

PhishDestroy first recorded capital.tokenizeae.com on 2026-11-12. VirusTotal: result unavailable for this observation. Listed by external blocklists: ScamSniffer.

Review the evidence
Registrar
United StatesNameSilo
Resolved IP
Canada172.67.201.120Cloudflare, Inc. · CDN
Registered
Nov 4, 2026
First observed
Nov 12, 2026
PhishDestroy assessment High
58/100
Evidence score
First observed Nov 12, 2026 07:22 UTC · PhishDestroy
Risk signals
Stored blocklist matches: 1 Young domain: 7 days old
Blocklist matches
1
ScamSniffer
URLScan
Malicious
Page captures
1
open gallery
Domain age
7 days
registered 2026-11-04 according to WHOIS
Nov 12, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded capital.tokenizeae.com on 2026-11-12. VirusTotal: result unavailable for this observation. Listed by external blocklists: ScamSniffer. Risk: high (58/100). Registrar: NameSilo. Hosting: Cloudflare, Inc. Do not enter credentials or connect a wallet.

High
Blocklist matches
1
Hosting
Canada172.67.201.120Cloudflare, Inc. · CDN
Registrar
United StatesNameSilo
Registered
Nov 4, 2026
Page captures
1
Page captures Source results Registration record

Recorded source summary

capital.tokenizeae.com is a subdomain of tokenizeae.com. PhishDestroy first observed the hostname on Nov 12, 2026. Current evidence score: 58/100 (high).

Positive findings are stored from 2 sources: ScamSniffer and URLScan. On Nov 12, 2026 at 07:20 UTC, ScamSniffer listed the hostname in the separate external-blocklist snapshot; URLScan returned a malicious verdict with score 100; scan metadata linked the capture to ubs and assigned phishing as its category.

The collector marked the hostname reachable on Nov 12, 2026 at 07:22 UTC, but did not retain the HTTP response code. Latest classified outcome: unknown; cause probe inconclusive on Nov 12, 2026 at 06:22 UTC. Registration records for the registrable domain tokenizeae.com list NameSilo, LLC as the registrar and Nov 4, 2026 as the creation date. Registration preceded first observation by 7 days. At collection time, the hostname resolved to 172.67.201.120 on AS13335 (Cloudflare, Inc.). The IP and ASN identify shared Cloudflare edge infrastructure; the origin server is not established by this address. The evidence archive retains 1 visual capture from URLScan; the captures preserve the landing-page appearance. TLS metadata lists YE2 as the certificate issuer with validity through Feb 2, 2027.

The record contains 2 positive source findings supporting the current phishing classification.

Source evidence 2 sources

URLScan

Malicious

SHA-256 af1ffdc3c349c1b80f4ec7beb75f017e119c7295f8e2250129ca0da4c6de9c56

Open report
URLScanOriginal source recordObserved: 21 fields

Observed: · Retrieved:

Report ID

01a1cea1-547c-749b-98b1-690787ba31a9

Final URL

https://capital.tokenizeae.com/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://capital.tokenizeae.com/
    From
    http://capital.tokenizeae.com/
    Status
    307

IP address

172.67.201.120

Contacted domains

  • api.zloei.top

Contacted IP addresses

  • 188.114.97.3
  • 172.67.201.120

Autonomous systems (ASN)

  • 13335

Document hash

af1ffdc3c349c1b80f4ec7beb75f017e119c7295f8e2250129ca0da4c6de9c56

Script hashes

  • f295be063ca8c48451ee69fdaff22f78e0974151dd1d64df4e8a8aee6e30d58b
  • 370c79976d79236c940511c72a15cbd4ada5812ce2f64786c39391f3166b65d3
  • dc31e94f898ee4763257cabb14034fd96754513b0ad6044d83cac83f12931b12
  • aa131e8948b321185d19418f1212ae1d19e2911556640d8659e26579e3a322f6

JavaScript globals

  • webpackChunkgalaxy_digital
  • clearImmediate
  • setImmediate
  • _
  • regeneratorRuntime
  • proto
  • TronWebProto
  • __ubsDumpWalletEnv
  • vm

Browser storage keys

  • __storage_test__
  • language
  • lang
  • virtualStatus

TLS session and certificate

Subject alternative names
  • *.tokenizeae.com
  • tokenizeae.com
Cipher
AES_128_GCM
Issuer
YE2
Subject
tokenizeae.com
Protocol
QUIC
Valid until
Valid from

Domain age, days

0

Registered domain age, days

6

Certificate age, days

7

Certificate validity, days

89

Page requests

30

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-2aab354
Score
90
Malicious
Yes
Overall verdict
Tags
  • phishing
Score
100
Brands
  • ubs
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • UBS
Malicious
Yes
Categories
  • phishing

HTTP headers

Server
cloudflare
Content-type
text/html
Strict-transport-security
max-age=31536000
Priority
u=0,i
Original source fields · JSON
Uuid
01a1cea1-547c-749b-98b1-690787ba31a9
Final url
https://capital.tokenizeae.com/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://capital.tokenizeae.com/",
        "from": "http://capital.tokenizeae.com/",
        "status": 307
    }
]
Ip
172.67.201.120
Contacted domains
[
    "api.zloei.top"
]
Contacted IP addresses
[
    "188.114.97.3",
    "172.67.201.120"
]
Asns
[
    "13335"
]
Document hash
af1ffdc3c349c1b80f4ec7beb75f017e119c7295f8e2250129ca0da4c6de9c56
Script hashes
[
    "f295be063ca8c48451ee69fdaff22f78e0974151dd1d64df4e8a8aee6e30d58b",
    "370c79976d79236c940511c72a15cbd4ada5812ce2f64786c39391f3166b65d3",
    "dc31e94f898ee4763257cabb14034fd96754513b0ad6044d83cac83f12931b12",
    "aa131e8948b321185d19418f1212ae1d19e2911556640d8659e26579e3a322f6"
]
Globals
[
    "webpackChunkgalaxy_digital",
    "clearImmediate",
    "setImmediate",
    "_",
    "regeneratorRuntime",
    "proto",
    "TronWebProto",
    "__ubsDumpWalletEnv",
    "vm"
]
Storage keys
[
    "__storage_test__",
    "language",
    "lang",
    "virtualStatus"
]
Tls
{
    "san": [
        "*.tokenizeae.com",
        "tokenizeae.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE2",
    "subject": "tokenizeae.com",
    "protocol": "QUIC",
    "valid_to": "2027-02-02T15:58:21Z",
    "valid_from": "2026-11-04T15:58:22Z"
}
Domain age days
0
Apex age days
6
Tls age days
7
Tls valid days
89
Requests
30
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-2aab354"
        ],
        "score": 90,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "ubs"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "UBS"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html",
    "strict-transport-security": "max-age=31536000",
    "priority": "u=0,i"
}

Spamhaus DBL

Check recorded; verdict not retained

Open report

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
Network Security Intelligence Registrar context
Registrar context NameSilo
Stored registration data identifies NameSilo as the registrar. PhishDestroy maintains separate registrar investigations; that broader material is contextual and is not an independent detection for this domain.
Review source investigation

Questions about capital.tokenizeae.com

Is capital.tokenizeae.com legit?

PhishDestroy rates capital.tokenizeae.com as high risk (58/100) from the recorded evidence; it was first recorded on 2026-11-12. VirusTotal: result unavailable for this observation. Listed by external blocklists: ScamSniffer. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is capital.tokenizeae.com safe to connect a wallet?

This report does not record which wallet requests capital.tokenizeae.com 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 capital.tokenizeae.com?

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 matchesScamSniffer · PhishDestroy · no match in the other 10 2
ScamSniffer Listed View source
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 1 capture

URLScan · 2026-11-12 1 / 1
SourceURLScan · 2026-11-12
Recorded
StateStored capture
HTTP status200
Final URLhttps://capital.tokenizeae.com/
Position1 / 1
Open capture Source Report Wayback Download
All capture links and hashes (1)

Domain details

Domain
IP Context Canada172.67.201.120 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) NameSilo US(US) PhishDestroy Investigation
Abuse contactabuse@namesilo.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for tokenizeae.com →
Registration (base domain)tokenizeae.com · Created Nov 4, 2026 (7d · Very New!) — Expires Nov 4, 2027
Technical detailsProvenance & timestamps
First DetectedNov 12, 2026
Submitted URLhttp://capital.tokenizeae.com/
Favicon Hash
TLS Certificate
Issued by YE2 · stored validity ends in 82 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada172.67.201.120
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
CanadaToronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • becky.ns.cloudflare.com
  • conrad.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
YE2
Valid from
2026-11-04 15:58:22
Valid until
2027-02-02 15:58:21
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate names · 2 SANs
  • *.tokenizeae.com
  • tokenizeae.com

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

viewdns.info · 172.67.201.120rapiddns.io
Report This Domain Submit evidence & help protect others
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://capital.tokenizeae.com/
Tokenize
Tokenize is a multi-asset regulated, licensed global broker, providing trading services & facilities to both retail & institutional clients.
Response
HTTP 200
HTML body
2.5 KB
Compressed
1.0 KB
Links
0 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Favicon fingerprint: 22e21d1e38a26ca3e273e0058ab89d59f5eb90468d70cd5c04ca29e46c917930
Open Graph title: Tokenize - World Leader in Online Trading | Regulated Broker
Open Graph description: Tokenize is a multi-asset regulated, licensed global broker, providing trading services & facilities to both retail & institutional clients.
Twitter card: summary_large_image
Saved response-header values · 15
Alt-Svc
h3=":443"; ma=86400
cf-cache-status
DYNAMIC
CF-RAY
a593cb9bceb13b3b-FRA
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Thu, 12 Nov 2026 07:24:09 GMT
Last-Modified
Wed, 11 Nov 2026 13:14:13 GMT
NEL
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=frEnCsPkwe1WYVQR1zehhf44suFckDQxOFSWHJjVs5Z2aNJyB5TMHxJMixe6EQDM1A3PQR9IplCw7TNetrDIMEH6Z3iNpgUkTe8gMeocO%2FL%2BzGYpYEG%2FNxDRE%2F6Iir%2BHF6KkQ
Server
cloudflare
Server-Timing
cfCacheStatus;desc="DYNAMIC"
Strict-Transport-Security
max-age=31536000
Transfer-Encoding
chunked
Vary
Accept-Encoding

Values retained by the collector; long values may be shortened during collection.

Archived
Registration & observation details1

Availability observations

Last reachable observation

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

All stored data62

Detections & threat intelligence

Blocklist hits
PhishDestroy, ScamSniffer
Blocklist count
2
Blocklist checked at
2026-11-12 08:20:02
URLScan ID
01a1cea1-547c-749b-98b1-690787ba31a9
Report count
0
User reports
0
URLScan checked at
2026-11-12 08:22:43
DOM risk score
0
Spamhaus checked at
2026-11-12 08:37:04
URLScan captured at
2026-11-12 07:20:50
URLScan result ID
01a1cea1-547c-749b-98b1-690787ba31a9
URLScan payload hash
af1ffdc3c349c1b80f4ec7beb75f017e119c7295f8e2250129ca0da4c6de9c56
URLScan evidence
{ "v": 1, "ip": "172.67.201.120", "ips": [ "188.114.97.3", "172.67.201.120" ], "tls": { "s…
{
    "v": 1,
    "ip": "172.67.201.120",
    "ips": [
        "188.114.97.3",
        "172.67.201.120"
    ],
    "tls": {
        "san": [
            "*.tokenizeae.com",
            "tokenizeae.com"
        ],
        "cipher": "AES_128_GCM",
        "issuer": "YE2",
        "subject": "tokenizeae.com",
        "protocol": "QUIC",
        "valid_to": "2027-02-02T15:58:21Z",
        "valid_from": "2026-11-04T15:58:22Z"
    },
    "asns": [
        "13335"
    ],
    "uuid": "01a1cea1-547c-749b-98b1-690787ba31a9",
    "status": 200,
    "domains": [
        "api.zloei.top"
    ],
    "globals": [
        "webpackChunkgalaxy_digital",
        "clearImmediate",
        "setImmediate",
        "_",
        "regeneratorRuntime",
        "proto",
        "TronWebProto",
        "__ubsDumpWalletEnv",
        "vm"
    ],
    "headers": {
        "server": "cloudflare",
        "priority": "u=0,i",
        "content-type": "text/html",
        "strict-transport-security": "max-age=31536000"
    },
    "doc_hash": "af1ffdc3c349c1b80f4ec7beb75f017e119c7295f8e2250129ca0da4c6de9c56",
    "requests": 30,
    "task_url": "http://capital.tokenizeae.com/",
    "verdicts": {
        "engines": {
            "tags": [
                "urlscan-ml",
                "urlscan-ml-2aab354"
            ],
            "score": 90,
            "malicious": true
        },
        "overall": {
            "tags": [
                "phishing"
            ],
            "score": 100,
            "brands": [
                "ubs"
            ],
            "malicious": true,
            "categories": [
                "phishing"
            ]
        },
        "urlscan": {
            "tags": [
                "phishing"
            ],
            "score": 100,
            "brands": [
                "UBS"
            ],
            "malicious": true,
            "categories": [
                "phishing"
            ]
        }
    },
    "final_url": "https://capital.tokenizeae.com/",
    "redirects": [
        {
            "to": "https://capital.tokenizeae.com/",
            "from": "http://capital.tokenizeae.com/",
            "status": 307
        }
    ],
    "fetched_at": "2026-11-12T07:24:05Z",
    "redirected": "https-only",
    "scanned_at": "2026-11-12T07:20:50Z",
    "task_domain": "capital.tokenizeae.com",
    "storage_keys": [
        "__storage_test__",
        "language",
        "lang",
        "virtualStatus"
    ],
    "tls_age_days": 7,
    "apex_age_days": 6,
    "script_hashes": [
        "f295be063ca8c48451ee69fdaff22f78e0974151dd1d64df4e8a8aee6e30d58b",
        "370c79976d79236c940511c72a15cbd4ada5812ce2f64786c39391f3166b65d3",
        "dc31e94f898ee4763257cabb14034fd96754513b0ad6044d83cac83f12931b12",
        "aa131e8948b321185d19418f1212ae1d19e2911556640d8659e26579e3a322f6"
    ],
    "tls_valid_days": 89,
    "domain_age_days": 0
}

Network, hosting & TLS

IP address
172.67.201.120
Nameservers
becky.ns.cloudflare.com conrad.ns.cloudflare.com
DNS resolves
Yes
IP country
CA
IP city
Toronto
IP org
Cloudflare, Inc.
TLS issuer
YE2
TLS SANs
*.tokenizeae.com, tokenizeae.com
TLS valid from
2026-11-04 15:58:22
TLS valid to
2027-02-02 15:58:21
ASN
13335
ASN name
Cloudflare, Inc.
Server header
cloudflare
CDN
No
DNS state
stale

Registration

Registrar
NameSilo, LLC
WHOIS emails
abuse@namesilo.com
Creation date
2026-11-04 16:54:20
Expiration date
2027-11-04 16:54:20
Registrar action verified
No
Registrar action linked to report
No
Registration state
unknown

Status, takedown & timeline

Detected at
2026-11-12 08:22:43
Status
pending
Site status
alive
Last alive
2026-11-12 08:22:43
Last checked
2026-11-12 08:22:43
Created at
2026-11-12 08:22:43
Updated at
2026-11-12 08:37:04
Outcome state
unknown
Outcome cause
probe_inconclusive
Outcome actor type
unknown
Outcome confidence
20
Outcome evidence source
current_state_backfill
Outcome evidence at
2026-11-12 08:22:43.000000
Outcome evidence
{ "reason": "", "http_status": 0, "observed_at": "2026-11-12 08:22:43", "latest_http_obser…
{
    "reason": "",
    "http_status": 0,
    "observed_at": "2026-11-12 08:22:43",
    "latest_http_observation": {
        "cause": "probe_inconclusive",
        "state": "unknown",
        "source": "http_observation",
        "mechanism": null,
        "actor_name": null,
        "actor_type": "unknown",
        "confidence": 20,
        "observed_at_utc": "2026-11-12 07:22:43",
        "availability_state": "unreachable",
        "provider_action_verified": false
    }
}
Outcome evidence at (UTC)
2026-11-12 07:22:43.000000
Availability state
unreachable
Content state
unknown
Last reachable at (UTC)
2026-11-12 07:22:43.000000
Shutdown time basis
inconclusive
Shutdown time precision
open

Page & captures

Source URL
http://capital.tokenizeae.com/
Favicon hash
7c860f0e3150eba18fef561d71c1dbf9
Technologies
{ "urlscan": { "v": 1, "ip": "172.67.201.120", "ips": [ "188.114.97.3", "172.67.201.120" ]…
{
    "urlscan": {
        "v": 1,
        "ip": "172.67.201.120",
        "ips": [
            "188.114.97.3",
            "172.67.201.120"
        ],
        "tls": {
            "san": [
                "*.tokenizeae.com",
                "tokenizeae.com"
            ],
            "cipher": "AES_128_GCM",
            "issuer": "YE2",
            "subject": "tokenizeae.com",
            "protocol": "QUIC",
            "valid_to": "2027-02-02T15:58:21Z",
            "valid_from": "2026-11-04T15:58:22Z"
        },
        "asns": [
            "13335"
        ],
        "uuid": "01a1cea1-547c-749b-98b1-690787ba31a9",
        "status": 200,
        "domains": [
            "api.zloei.top"
        ],
        "globals": [
            "webpackChunkgalaxy_digital",
            "clearImmediate",
            "setImmediate",
            "_",
            "regeneratorRuntime",
            "proto",
            "TronWebProto",
            "__ubsDumpWalletEnv",
            "vm"
        ],
        "headers": {
            "server": "cloudflare",
            "priority": "u=0,i",
            "content-type": "text/html",
            "strict-transport-security": "max-age=31536000"
        },
        "doc_hash": "af1ffdc3c349c1b80f4ec7beb75f017e119c7295f8e2250129ca0da4c6de9c56",
        "requests": 30,
        "task_url": "http://capital.tokenizeae.com/",
        "verdicts": {
            "engines": {
                "tags": [
                    "urlscan-ml",
                    "urlscan-ml-2aab354"
                ],
                "score": 90,
                "malicious": true
            },
            "overall": {
                "tags": [
                    "phishing"
                ],
                "score": 100,
                "brands": [
                    "ubs"
                ],
                "malicious": true,
                "categories": [
                    "phishing"
                ]
            },
            "urlscan": {
                "tags": [
                    "phishing"
                ],
                "score": 100,
                "brands": [
                    "UBS"
                ],
                "malicious": true,
                "categories": [
                    "phishing"
                ]
            }
        },
        "final_url": "https://capital.tokenizeae.com/",
        "redirects": [
            {
                "to": "https://capital.tokenizeae.com/",
                "from": "http://capital.tokenizeae.com/",
                "status": 307
            }
        ],
        "fetched_at": "2026-11-12T07:24:05Z",
        "redirected": "https-only",
        "scanned_at": "2026-11-12T07:20:50Z",
        "task_domain": "capital.tokenizeae.com",
        "storage_keys": [
            "__storage_test__",
            "language",
            "lang",
            "virtualStatus"
        ],
        "tls_age_days": 7,
        "apex_age_days": 6,
        "script_hashes": [
            "f295be063ca8c48451ee69fdaff22f78e0974151dd1d64df4e8a8aee6e30d58b",
            "370c79976d79236c940511c72a15cbd4ada5812ce2f64786c39391f3166b65d3",
            "dc31e94f898ee4763257cabb14034fd96754513b0ad6044d83cac83f12931b12",
            "aa131e8948b321185d19418f1212ae1d19e2911556640d8659e26579e3a322f6"
        ],
        "tls_valid_days": 89,
        "domain_age_days": 0
    }
}

Other

AI queued
No
Indexnow sent at
2026-11-12 08:30:05

Captured network requests

Network requests: 30 SHA-256 hashes: 29 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-12 07:24 UTC.

Open this scan on URLScan 01a1cea1-547c-749b-98b1-690787ba31a9 ↗

Stored observation history1

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Domain monitor · First collection record

    Reachable

All retained availability observations2

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
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-12 08:22:43.000000
    Evidence SHA-256
    3b037a617b04c4711b2e004ef607bb8f91fcaa5db57dfc559447b98641a6709b
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-12 08:22:43
    Evidence reason
  2. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-12 08:22:43.000000
    Evidence SHA-256
    3b037a617b04c4711b2e004ef607bb8f91fcaa5db57dfc559447b98641a6709b
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-12 08:22:43
    Evidence reason

Threat Response Pipeline

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

Recorded events: 7. 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
    capital.tokenizeae.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Blocklist Detection · Registrar Context: NameSilo · Forensic Evidence Collected Recorded: 5 of 5
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan classified the page as malicious · Score: 100
  • Blocklist Detection
    Found in blocklists: ScamSniffer
  • Registrar Context: NameSilo
    Separate registrar research is available. Registrar association is contextual and is not scored as an independent detection.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
Publication & AvailabilityDestroyList Published Recorded: 1 of 1

Recorded activity

2 entries
  1. Added to PhishDestroy

    capital.tokenizeae.com

    View source
  2. URLScan

    Page captured

    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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation
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.

capital.tokenizeae.com

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal ChainPatrol URLQuery SSL Labs Stored certificate dates valid WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked Unverified
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.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
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.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

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 capital.tokenizeae.com)
  • 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

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

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.

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.

Request a correction or appeal How PhishDestroy works
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/capital.tokenizeae.com"
  title="PhishDestroy threat report for capital.tokenizeae.com"
  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>