VirusTotal
5 / 89
On 2026-10-02, an HTTP status code of 403 was recorded for gfxtrade.com during a check of the domain. The same domain appears in the PhishDestroy internal listing, a publisher-owned catalogue, and was first observed on 2026-09-11.
An HTTP check on 2026-10-02 recorded status 403 for gfxtrade.com. The PhishDestroy internal listing records the domain in that catalogue. VirusTotal recorded 5 detections across 89 scanners on 2026-09-24. OTX recorded 4 pulses on 2026-09-20. The domain was first observed on 2026-09-11.
The HTTP 403 record describes only the response captured at that check, not all content the domain may serve. The PhishDestroy listing and the OTX pulse count are separate source records that each describe their own observation. The VirusTotal detection ratio is a scanner result set, not a verdict, and it should be read alongside the other named records rather than combined with them. The 2026-09-11 first observation and the later checks show a sequence of dated records without establishing a trend.
Preserve the gfxtrade.com HTTP check record and the PhishDestroy internal listing entry for later comparison. Separately retain the VirusTotal and OTX records so each source can be reviewed on its own terms. Compare the gfxtrade.com records against future checks of the same sources, and treat each source's output as distinct when reviewing the domain.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: alive_content: raw=ok; http=200; via=https_proxy
Edge-IP reputation is not attributed to this domain.
rachel.ns.cloudflare.compremium127.web-hosting.compriority 0Location describes the IP network.
30d6b95972a5ca61275920743212f5ad2aaa69d05f558a40378199e843027b35Saved 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 gfxtrade.com · checked Sep 18, 2026
8 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.
1 community report
CategoryPHISHING
The PhishFort Detection System has flagged this as a domain threat, classified as null. Threat detected at 2026-09-11T00:38:43.128Z.
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
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