m.webforex.cc is a mobile-style subdomain whose name points to online forex trading. It sits on the PhishDestroy blocklist, which we first added it to on 2026-09-05. It has not yet been assigned a specific scheme type. The site is now dead: it went offline on 2026-09-15, and its DNS was still inactive when we last checked on 2026-10-19.
How the scam works
We cannot confirm which scheme ran on this domain, so we will not name one. The forex branding and the security-vendor verdicts point to a site built to win a visitor's trust around trading or investing money. The usual risks with sites like this are entering login or personal details, or sending funds to an account you cannot verify. Anyone who interacted with it should assume that information or money handed over there may be lost.
Evidence
On 2026-09-17, eleven of 89 VirusTotal engines flagged the domain as malicious. Among them were BitDefender, CRDF, CyRadar, Forcepoint ThreatSeeker, Fortinet, G-Data, Kaspersky and LevelBlue. That is a modest share of engines, but it comes from several unrelated vendors, which makes a harmless false alarm less likely. PhishDestroy is the only blocklist listing it so far.
Infrastructure
The domain was registered through Gname.com Pte. Ltd. on 2026-04-26. That is about four months before PhishDestroy flagged it, so it was not a throwaway registration used for only a day or two. After detection it lasted about ten days before going offline on 2026-09-15. The "m." prefix suggests a version built for phone visitors, a common way to reach people who follow links from messaging apps or social media.
What to do
If you signed up or logged in here, change that password everywhere you reused it and turn on two-factor authentication. If you sent money or shared card or bank details, contact your bank or payment provider now. Do not pay any further "fees" or deposits that anyone tied to this site demands to release funds. Keep screenshots and payment receipts for a fraud report. Defenders should block the domain and related webforex.cc subdomains, and check logs for traffic to it between 2026-04-26 and 2026-09-15.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-19 01:13:56 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-09-05 05:28:15 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-09-05 05:28:15 UTC → 2026-09-30 16:14:55 UTC · 610.78hmidpoint estimate ≈ 2026-09-17 22:51:35 UTC · precision low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
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.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
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.
(SG)
