VirusTotal
0 / 92 engine detections
Open report“Tokenize”
0 / 92 engine detections
Open reportScan report
Open report3 community references
Open reportScan report
Open reportNo threat flag
Open reportPage capture
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
PhishDestroy has added tokenizehnwi.com to its internal blocklist as a suspicious domain. The recorded page title of the site is “Tokenize”. The domain was first seen by PhishDestroy on 2026-10-20.
No specific malicious behavior was observed on the page, so the listing does not identify a concrete scam mechanism. Suspicious domains may be used for typical phishing, credential harvesting, or fraudulent financial offers, but the exact method cannot be determined from the current evidence.
VirusTotal returned 0 detections out of 92 engines on a scan retrieved on 2026-10-20. Google Safe Browsing checked the URL on 2026-10-20 and did not flag it. The external blocklist ScamSniffer listed the domain (1 entry) on 2026-10-20. PhishDestroy’s internal blocklist also contains the domain as of 2026-10-20. OTX recorded three pulses mentioning the domain on 2026-10-20.
The domain was registered on 2026-10-12 through Realtime Register B.V. The recorded IP address associated with the site is 107.151.212.50. Registration occurred eight days before the first sighting by PhishDestroy.
If you visited the site but did not submit credentials or personal data, no immediate action is required beyond routine vigilance. If any login information or sensitive details were entered, change the associated passwords and monitor accounts for unauthorized activity. Network defenders should add tokenizehnwi.com to blocklists, review logs for connections to 107.151.212.50, and apply any relevant security policies to this exact address.
Last checked
a.share-dns.coma6.share-dns.comb.share-dns.netb6.share-dns.netLocation describes the IP network.
78400e988ad7fbb93e7d437a0840c63af98d11307201d1d3822fdb1e35ab89c7www.hnwitt-trade.comwww.tokenize-tradeus.comwww.tokenizetrade.vipwww.ubsadvanced.tradeSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of tokenizehnwi.com · checked Oct 20, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://tokenizehnwi.com/Server: nginxContent-Type: text/htmlContent-Encoding: gzip9e1e9384914db414598d38f7149341f21ccfbbcb4fbc9019d7ec54d88101a8e4summary_large_imagequic=":443"; h3=":443"; h3-29=":443"; h3-27=":443";h3-25=":443"; h3-T050=":443"; h3-Q050=":443";h3-Q049=":443";h3-Q048=":443"; h3-Q046=":443"; h3-Q043=":443"keep-alivegziptext/htmlTue, 20 Oct 2026 13:32:42 GMTW/"6acdb7cb-2893"Tue, 13 Oct 2026 04:47:07 GMTnginxmax-age=31536000chunkedAccept-EncodingValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Reachable
3 community references
View sourceNo threat flag
View source0/92 engine detections
View sourcePD-20261020-752EB6
tokenizehnwi.com
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
tokenizehnwi.com
PD-20261020-752EB6 Recipient: rtr-security-threats@realtimeregister.com If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
tokenizehnwi.com)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.