VirusTotal
12 / 92
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
“qfstradefxmarkets | Home”
Assessment based on the stored source evidence below. Review sources →
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@regtons.com.
The latest stored availability evidence still shows the domain reachable; 21 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
12 / 92
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
2 det.
Alerts refer to the preserved scan. They do not describe the current state of the site.
2 external matches
DetailsA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
3 community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: suspicious
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
stored report
View stored capture ↗ ReportA preserved page image documents what the collector received; a capture is not a safety verdict.
Analysis completed
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.
Stored evidence for qfstradefxmarkets.com: VirusTotal recorded 2 detections among 91 scanners on 2026-09-25. That ratio reproduces the stored check in its original units and is not converted into another measure. MetaMask and SEAL appear as named external blocklist observations for qfstradefxmarkets.com. Each item in this report remains at the scope supplied by its dated source record.
VirusTotal records 2 detections among 91 scanners in the stored snapshot dated 2026-09-25. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-09-25 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.
MetaMask and SEAL are recorded as named external blocklist observations for qfstradefxmarkets.com in the snapshot dated 2026-09-25. The stored MetaMask and SEAL blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains qfstradefxmarkets.com as a publisher record. That PhishDestroy record is counted separately from the MetaMask and SEAL external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.
The record first observed qfstradefxmarkets.com on 2026-09-25. The MetaMask and SEAL blocklist snapshot is dated 2026-09-25 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-07-20. A URLScan reference was stored on 2026-09-25 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.
For qfstradefxmarkets.com, the registrar field records Gransy, s.r.o.; this is kept as an exact source value. The source stores 84.16.253.0 as the observed address in this record. The registration date for qfstradefxmarkets.com is recorded as 2026-07-20. The stored ASN observation records 28753 and Leaseweb Deutschland GmbH in this record. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.
The qfstradefxmarkets.com record states that VirusTotal recorded 2 detections among 91 scanners on 2026-09-25. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-09-25. PhishDestroy remains a separate publisher catalogue entry in the stored record. For qfstradefxmarkets.com, the registrar field records Gransy, s.r.o.; this remains separate from the other source fields. The observed address field in this record contains 84.16.253.0. The supported conclusion is bounded to the exact stored observations for qfstradefxmarkets.com. Any statement beyond those source values would require additional dated material.
Avoid submitting sensitive information to qfstradefxmarkets.com during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain qfstradefxmarkets.com as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and MetaMask and SEAL blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to qfstradefxmarkets.com. The stored record does not justify extending that rule to 84.16.253.0 or to other infrastructure records.
23 · datasets with records / 8 · not recorded
What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.
These checks have no retained result. This does not mean they passed or that a scan is running.
2 · external source matches
Gransy, s.r.o. · 84.16.253.0 · DNS, TLS and retained responses
ns1.cloudservercentre.comns2.cloudservercentre.comqfstradefxmarkets.compriority 0Location describes the IP network.
4d5a1936abc300f8215e690acabc6cae66099ae6ef644631f399729b4e686264autoconfig.qfstradefxmarkets.comautodiscover.qfstradefxmarkets.comcpanel.qfstradefxmarkets.comcpcalendars.qfstradefxmarkets.comcpcontacts.qfstradefxmarkets.commail.qfstradefxmarkets.comwebdisk.qfstradefxmarkets.comwebmail.qfstradefxmarkets.comwww.qfstradefxmarkets.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
autoconfig.qfstradefxmarkets.comDomain recordautodiscover.qfstradefxmarkets.comDomain recordcpanel.qfstradefxmarkets.comDomain recordcpcalendars.qfstradefxmarkets.comDomain recordcpcontacts.qfstradefxmarkets.comDomain recordmail.qfstradefxmarkets.comDomain recordwebdisk.qfstradefxmarkets.comDomain recordwebmail.qfstradefxmarkets.comDomain recordwww.qfstradefxmarkets.comDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of qfstradefxmarkets.com · checked Sep 25, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored browser and crawler observations
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
LiteSpeedScanner note: alive_content: raw=ok; http=200; via=https_proxy; server=LiteSpeed
No live-check result has been retained.
1 · outbound report records
84.16.253.0.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
redirected→Unknown
probe_inconclusive
Unknown→redirected
http_redirect
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
live_content→Unknown
stale_current_evidence
Unknown→live_content
content_served
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
Unknown
probe_inconclusive
Reachable
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
Shared hosting, registrar records and related domains
79 stored lookalike domains
Original reports, independent checks and evidence links
PD-20260925-F977E7 Recipient: abuse@regtons.com Policy Violations: Illegal Activities: Active phishing operation targeting victims Fraud & Deception: Impersonation of legitimate services Identity Theft: Collection of credentials under false pretenses Applicable Laws (Unknown): International Anti-Cybercrime Regulations Budapest Convention on Cybercrime Universal Fraud Prevention Laws Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws. Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
Recovery steps, reporting contacts and complaint drafts
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 ↗
qfstradefxmarkets.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
Stored evidence snapshot. Source timestamps appear where available.
Captured title: “qfstradefxmarkets | Home”. Apparent target: MetaMask.
VirusTotal detections for qfstradefxmarkets.com: 12 (2026-10-07 02:14:02 UTC).
Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.
submit an appeal or review the FAQ page.