Skip to security report
Analytics Dashboard
Domain security and threat intelligence
m.webforex.cc favicon

m.webforex.cc

Registrar
Gname
Registered
Apr 26, 2026
Threat verdict Critical
Availability Content unavailable Content was unavailable in the latest observation Observed
Source: HTTP probe
Risk signals
VirusTotal detections: 11/89
Sep 5, 2026
API
This domain has been flagged as malicious
Security engines reporting a detection: 11. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
VirusTotal
11 det.
Age
6 mo
Observed status
Content unavailable
PhishDestroy
DestroyList
Listed

Source evidence

4 sources

VirusTotal

11 / 89

Report

OTX

no community references

Report

CF Radar

provider verdict: clean

Report

Google Safe Browsing

Checked; no threat flag recorded

Report

Evidence Summary

Critical
VirusTotal
11/89

Assessment

On 2026-10-01 m.webforex.cc returned an HTTP 502 response, indicating a server-side error at the time of the check. The domain was first observed on 2026-09-05 by the same publisher.

Recorded Evidence

The domain was listed in the PhishDestroy internal catalogue on 2026-09-17. VirusTotal scanned m.webforex.cc on 2026-09-17, finding 11 detections out of 89 scanners. The HTTP status was recorded as 502 on 2026-10-01.

Interpretation

These dated records show the domain’s status across different sources and dates. The HTTP 502 response documents a server error on the recorded date. VirusTotal’s scan reflects visibility to multiple security vendors on its observation date. The PhishDestroy internal listing marks the domain for internal review on its listed date.

Recommended Actions

Retain the dated HTTP 502 record and VirusTotal scan for ongoing monitoring and comparison. Reference the PhishDestroy internal listing to track any changes in internal handling. Perform periodic checks of m.webforex.cc to update these records and inform future assessments.

Detection-evasion analysis

Cloaking and traffic-distribution check

Not yet scanned No crawler-versus-browser difference has been recorded yet

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not yet scanned
Last cloaking scan

Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='m.webforex.cc', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("

Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Waiting

Domain details

Domain
Registrar (base domain) Gname SG(SG)
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for webforex.cc →
Registration (base domain)webforex.cc · Created Apr 26, 2026 (170d)
Time to First Unavailability 10 days
What we count Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedSep 5, 2026
Favicon Hash

Network & certificates

Stored technical evidence

Network & DNS

Nameservers 1

  • b9.share-dns.net

Location describes the IP network.

Latest Classified Outcome 2026-10-13 20:21:07 UTC

Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Unknown Probe Inconclusive 20% 2026-10-13 01:15:50 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-09-05 05:28:15 UTC current episode first observed: 2026-09-30 16:14:55 UTC observed RIP window: 2026-09-05 05:28:15 UTC → 2026-09-30 16:14:55 UTC · 610.78h midpoint 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.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

11 / 89 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 11 detections
BitDefender
CRDF
CyRadar
Forcepoint ThreatSeeker
Fortinet
G-Data
Kaspersky
LevelBlue
PhishFort
SOCRadar
Sophos

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. VirusTotal Detections Update 2026-09-16 20:31:57 UTC
    VirusTotal scanner detections updated from 10 to 11. Added scanner alerts: Sophos.
  2. Domain Status Transition 2026-09-15 10:00:16 UTC
    Domain state transitioned from alive to dead.
  3. Threat First Observed 2026-09-15 03:53:11 UTC
    Domain ingestion complete. Initial state is marked as alive.

Threat Response Pipeline

Discovery
Analysis
Monitoring

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

Threat Ingested
m.webforex.cc detected and queued for full analysis
Sep 5, 2026
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
VirusTotal
11/89 recorded on VirusTotal
Sep 17, 2026
VT Detection +1
+1 new detection (10 → 11): Sophos
Sep 16, 2026
Content Observed Unavailable
Monitoring recorded an unavailable response; the cause was not independently established.
Sep 15, 2026
DestroyList Published
Listed in the public PhishDestroy/DestroyList repository
Sep 5, 2026
Content Observed Unavailable
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Sep 15, 2026
Time to First Unavailability
245 hours elapsed from detection to the first unavailable observation.
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

Community intelligence

1 community report

CategoryPHISHING

The PhishFort Detection System has flagged this as a domain threat, classified as null. Threat detected at 2026-09-05T02:15:24.461Z.

Evidence & External Reports

Security Analysis
VirusTotal 11 det. ChainPatrol ChainAbuse 1 report URLQuery SSL Labs CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Third-Party Detection — ChainAbuse
1 report filed for m.webforex.cc · category: Phishing · source checked
Flagged by PhishFort Detection System on Sep 5, 2026 — automated submission, not a user testimony. Source: ChainAbuse (TRM Labs).
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

Were You Affected by This Site?

1 evidence signal groups linked 0 reports recorded Content unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Europol
Find the official reporting channel for your EU country
National police directory
PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 →

Report to Your Local Authorities

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

97-country directory

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

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself

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

Live Threat Feed Appeal This Listing
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/m.webforex.cc"
  title="PhishDestroy threat report for m.webforex.cc"
  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>