VirusTotal
1 / 92 engine detections
Open report1 / 92 engine detections
Open reportScan report
Open report4 community references
Open reportprovider verdict: clean
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
1wtoken.xyz is a newly registered domain that has been placed on the PhishDestroy blocklist. The site was first observed by PhishDestroy on 2026-10-19 and remains alive, although its content was unreachable when last checked on the same day. No legitimate brand or service is clearly advertised, suggesting a malicious intent aimed at crypto users.
Although the exact page content could not be retrieved, the classification and typical behavior of similar crypto‑related threats indicate that the site likely tries to lure visitors into connecting a cryptocurrency wallet or entering private keys. Once a wallet is linked, attackers can request transaction approvals, resulting in unauthorized transfers and loss of funds.
VirusTotal scanned the domain and recorded one detection out of 92 scanning engines, with Forcepoint ThreatSeeker flagging it as malicious. The domain appears in four OTX pulses and is listed on the PhishDestroy blocklist. No additional detections from Google Safe Browsing, urlscan.io, or Spamhaus were reported, indicating limited but notable awareness among security vendors.
The domain was registered on 2026-10-13 through REG.RU LLC, giving it only a six‑day window before PhishDestroy first saw it. Hosting resolves to IP address 104.21.51.177, a network commonly used for fast content delivery. TLS is provided by Let’s Encrypt (issuer "Let’s Encrypt / YE1"), which does not imply abuse but shows the site uses a valid, automated certificate.
Anyone who visited the site, entered credentials, or connected a wallet should immediately change all related passwords, enable two‑factor authentication, and revoke any wallet approvals granted to unknown addresses. Monitor blockchain activity for unauthorized transfers. Defenders should block 1wtoken.xyz at the network perimeter, add it to internal threat feeds, and continue monitoring for related indicators.
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.
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.
Edge-IP reputation is not attributed to this domain.
olof.ns.cloudflare.comsummer.ns.cloudflare.comLocation describes the IP network.
dc5253b083f39f6e956a33c16b029fad8eb33afa8abcda12445054239607f8f9Saved 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 1wtoken.xyz · checked Oct 19, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
https://1wtoken.xyz/Content-Type: text/html; charset=UTF-8CF-Mitigated: challengeServer: cloudflareContent-Encoding: gzipSec-CH-UA-Bitness, Sec-CH-UA-Arch, Sec-CH-UA-Full-Version, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Platform, Sec-CH-UA, UA-Bitness, UA-Arch, UA-Full-Version, UA-Mobile, UA-Model,h3=":443"; ma=86400challengea4ced51ba8733a7c-FRAclosegzipdefault-src 'none'; script-src 'nonce-MSxUT3ODb9SonFxwQXc1CY' 'unsafe-eval' https://challenges.cloudflare.com; script-src-attr 'none'; style-src 'unsafe-inline'; img-src 'self' https://challenges.cloudflare.com; connect-src 'self' https://challenges.cloudflare.com; frame-src 'self' https://challenges.cloudflare.com blotext/html; charset=UTF-8Sec-CH-UA-Bitness, Sec-CH-UA-Arch, Sec-CH-UA-Full-Version, Sec-CH-UA-Mobile, Sec-CH-UA-Model, Sec-CH-UA-Platform-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Platform, Sec-CH-UA, UA-Bitness, UA-Arch, UA-Full-Version, UA-Mobile, UA-Model,require-corpsame-originsame-originMon, 19 Oct 2026 09:42:23 GMT{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}?1accelerometer=(),camera=(),clipboard-read=(),clipboard-write=(),geolocation=(),gyroscope=(),hid=(),magnetometer=(),microphone=(),payment=(),publickey-credentials-get=(),screen-wake-lock=(),serial=(),sync-xhr=(),usb=(),xr-spatial-tracking=*same-origin{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=OnVVcNpAO8Rb8yjEM0dot0xSNuQimCazzPVN7wXqhbNTtW4B3wo4Rm%2BqjOfbWZAXIqBCh9ZQFyVoSWVcfZeh1YHCCLGkBcZzqRLm3M5dxakToTPSfQrpmDyJ6ld7ew%3D%3D"}]}cloudflarechlray;desc="a4ced51ba8733a7c"chunkednosniffSAMEORIGINValues 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.
Unknown→protected
cloudflare_challenge · Cloudflare · challenge
Reachable
4 community references
View sourceNo threat flag
View source1/92 engine detections
View sourcePD-20261019-9A6602
1wtoken.xyz
View sourcePage captured
View sourceCompare what a browser and a crawler receive, and check for Keitaro traffic routing.
1wtoken.xyz
PD-20261019-9A6602 Recipient: abuse@reg.ru Registrar: REG.RU (Russia) Policy Violations: Abuse policy + ICANN contractual obligations; phishing classified as bad-faith use in UDRP; domains may be suspended/removed Applicable Laws: Criminal Code RF Art.159 (fraud), Art.272 (illegal access), Art.273 (malware creation), Art.274.1 (critical infrastructure interference)
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 ↗
1wtoken.xyz)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.