Skip to security report
Analytics Dashboard
Domain security report
tradesfxpro.com favicon

tradesfxpro.com

“TradesFXPro”

Threat verdict
CriticalDomain Appeal
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 3/91 Automated brand label: ["across"]
OTX: 5 refs Sep 15, 2026 ["across"] CDN
API
Registrar
GoDaddy
Resolved IP
72.60.239.137
Registered
Jun 15, 2026
2 sources
The capture source is temporarily unavailable.
1 / 2
Source
Primary capture
Collected · UTC
Open capture
In this reportGet help
This domain has been flagged as malicious
Security engines reporting a detection: 3. Exercise extreme caution — do not enter credentials or personal information.

Additional indicators at a glance

VirusTotal
VirusTotal
3 det.
OTX references
5 community refs
URLScan
URLScan
Report ↗
TLS Certificate
Within stored validity dates 25d
Let's Encrypt / YE1 · Hostname coverage not recorded
Age
4 mo
Observed status
Last known active 301
PhishDestroy
DestroyList
Listed

Source evidence

8 · sources

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.

VirusTotal

3 / 91

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

URLQuery

checked — no detections recorded

Report
Interpretation & limits

Alerts refer to the preserved scan. They do not describe the current state of the site.

OTX

5 community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

CF Radar

provider verdict: clean

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLScan capture

stored report

Report
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

URLScan verdict

Analysis completed

Report
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Google Safe Browsing

Checked; no threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Public blocklists

0 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Evidence Summary

Critical
VirusTotal
3/91
OTX
5 community refs
URLScan
Stored capture

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.

Assessment

tradesfxpro.com returned an HTTP 301 status in a check recorded on 2026-10-01, a redirect response captured at that moment. The domain was first observed on 2026-09-15, and its registration date is listed as 2026-06-15.

Recorded Evidence

The domain was first observed on 2026-09-15, and a PageSpeed check on the same date returned a performance score of 65. An SSL scan on 2026-09-15 identified the issuer as Let's Encrypt / YR1. VirusTotal, checked on 2026-09-29, reported 3 detections across 91 scanners. OTX was checked on 2026-09-17 and showed 3 pulses. The registrar is recorded as GoDaddy.com, LLC, and the IP address 72.60.239.137 is associated with CYPRESS COMMUNICATIONS, LLC in the US. PhishDestroy's internal listing is recorded as true.

Interpretation

The recorded observations span several dates and sources, so they should be read as separate snapshots rather than a single consistent picture. The HTTP 301 and PageSpeed score describe only what was measured at those moments, and the VirusTotal and OTX figures reflect their own collection methods. The chronology from first observation to the later checks does not by itself establish a trend or change in the domain's status.

Recommended Actions

For tradesfxpro.com, preserve the VirusTotal and OTX records so their detection and pulse counts can be compared against future checks. Retain the HTTP response record alongside the PageSpeed result to track whether the redirect behavior persists. Compare the PhishDestroy listing against later observations of the same domain, and keep the first-observed date as a reference point for any future timeline.

Data coverage & collection

19 · datasets with records / 12 · 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.

Recorded dataPartial recordUTC
VirusTotal
3 / 91 · engine detections
URLScan analysis
Automated verdict retained
URLQuery
Stored source record
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
5 · community references
External blocklists
0 · external matches
Cloudflare Radar
cleanCollection time not recorded
Spamhaus DBL
Collection time retained; verdict missing
Domain registration
GoDaddy.com, LLCCollection time not recorded
Network & DNS
72.60.239.137 · 2 · nameserversCollection time not recorded
TLS certificate
Let's Encrypt / YE1
Page captures
2 · retained captures
Page analysis
1 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
PageSpeed performance
65/100 · mobile performance
Availability history
28 · stored state changes
IP reputation
Network-level observations
Wayback archive
Archive link retained
Not recorded in this report 12

These checks have no retained result. This does not mean they passed or that a scan is running.

  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • HTML archives
  • Site configuration files
  • Response records
  • Recorded subdomains
  • Source observation history
  • Lookalike relationships
  • Community reports
  • Chainabuse records
Download the dated observations and supporting metadata.

Blocklist records

0 · external source matches

Public Blocklist Status

Domain, network & archive

GoDaddy.com, LLC · 72.60.239.137 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Vercel shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-09activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar GoDaddy US(US)
Abuse contactabuse@godaddy.com, abuse@hostinger.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for tradesfxpro.com →
RegistrationCreated Jun 15, 2026 (124d) — Expires Jun 15, 2027
HTTP Status301 Moved Permanently
Technical detailsProvenance & timestamps
First DetectedSep 15, 2026
DOM Analysisanalyzed Sep 15, 2026score 81/1001 brand signal
Submitted URLhttps://www.tradesfxpro.com/
Favicon Hash
Case ID

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
72.60.239.137
Network ASN
AS16509
Organization
CYPRESS COMMUNICATIONS, LLC
Observed location
Cleveland, US
Server header
Vercel

Edge-IP reputation is not attributed to this domain.

Nameservers 2
  • lunar.dns-parking.com
  • solar.dns-parking.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-08-14 20:02:16
Valid until
2026-11-12 20:02:15
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-10-11 01:03:39 UTC
Collection source
PhishDestroy collector
Certificate fingerprintfb3200672f855180548245729e8425aef3afdc173ba6fbafcb6f53c1b00b3e37

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 72.60.239.137rapiddns.io

Latest Classified Outcome 2026-10-17 22:07:24 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-17 22:07:24 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-17 22:07:24 UTC
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.
Technologies · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

3 / 91 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 3 detections
alphaMountain.ai
CRDF
SOCRadar

Archived Evidence

Wayback Machine Snapshot
A historical snapshot is available for evidence review
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of tradesfxpro.com · checked Sep 15, 2026

65
Needs Work
Performance
FCP
1.28s
First Contentful Paint
LCP
20.96s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
69ms
Total Blocking Time
SI
12.75s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Detection & evasion checks

Stored browser and crawler observations

Detection-evasion analysis

Cloaking suspected: scanner and visitor titles differ

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
Server header seen by scanner
hws

Scanner note: redirect: raw=redirect_301; http=301; via=https_proxy; location=https://www.tradesfxpro.com; server=hws

Title shown to the security scanner301 Moved Permanently
Title shown to a browser visitorTradesFXPro
Live TDS fingerprint check
Seven Keitaro fingerprints and a browser-versus-crawler comparison. A new scan starts only when you press the button.
Saved result
Cloaked / Filtered

Timeline & response

Collection history, report status and investigation channels

Stored observation history28

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  2. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  4. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  5. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

Earlier observations 23
  1. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  2. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  3. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  4. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  5. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  6. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  7. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  8. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  9. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  10. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  11. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  12. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  13. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  14. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  15. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  16. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  17. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  18. Availability monitor · Recorded state

    redirected→Unknown

    stale_current_evidence

  19. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  20. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  21. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  22. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  23. Availability monitor · Recorded state

    Unknown

    probe_inconclusive

Threat Response Pipeline

Discovery
Analysis
Monitoring

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

Threat Ingested
tradesfxpro.com detected and queued for full analysis
Sep 15, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Sep 30, 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.
Web Archive
Preserved in Wayback Machine — historical evidence archived
Oct 3, 2026
VirusTotal
3/91 recorded on VirusTotal
Sep 29, 2026
OTX Community References
5 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Oct 17, 2026
Brand Impersonation
Impersonation of ["across"]
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
Sep 30, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 18, 2026
DestroyList Published
Listed in the public PhishDestroy/DestroyList repository
Sep 15, 2026
Monitoring Continues
The domain remains reachable or access-restricted; future checks may update this 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

Related infrastructure

Shared hosting, registrar records and related domains

Evidence & investigation tools

Original reports, independent checks and evidence links

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 3 det. ChainPatrol URLQuery Report stored SSL Labs Hostname coverage not recorded CF Radar Open report OTX 5 refs WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
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 Archived
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

5 evidence signal groups linked 0 stored notification records Last known active

Listed domains receive at least one abuse report; this entry has no retained notification history.

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.

Immediate steps Find reporting contacts
Official reporting routes
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
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

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.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including tradesfxpro.com)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

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
Read the evidence in context

About This Report: tradesfxpro.com

Stored evidence snapshot. Source timestamps appear where available.

Captured title: “TradesFXPro”. Apparent target: ["across"].

VirusTotal detections for tradesfxpro.com: 3 (2026-09-29 02:12:24 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.

Embed this report

A compact widget with a link to the evidence

HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

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