tradehedgefund.com returned HTTP status 200 in an HTTP check dated 2026-10-01, the most recent recorded response for the domain. The same evidence set records a registration date of 2026-07-06 and a PhishDestroy internal listing, both of which are separate observations rather than conclusions about the site's content.
Recorded Evidence
The HTTP check dated 2026-10-01 recorded status 200, while the domain was first observed on 2026-09-17. VirusTotal, checked on 2026-09-25, reported 11 detections across 91 scanners, and OTX, checked on the same date, showed 5 pulses. The PhishDestroy internal listing is recorded as true, and the registrar is Gransy, s.r.o. with registration dated 2026-07-06. The SSL certificate, scanned on 2026-09-24, was issued by Let's Encrypt / YR2, and PageSpeed on 2026-09-25 returned a performance score of 81.
Interpretation
The named sources measure different things on different dates, so their values should be read as separate records rather than a combined judgment. The HTTP status describes only the response captured on its check date, and the VirusTotal and OTX figures reflect their own scanning contexts. The gap between first observation and the later checks shows the domain was recorded across multiple dates, but those dates alone do not establish a trend.
Recommended Actions
Preserve the HTTP, VirusTotal, OTX, and PhishDestroy records for tradehedgefund.com as separate source documents. Compare the VirusTotal and OTX observations against future checks of the same sources, and review the PhishDestroy listing alongside the HTTP record. Keep the PageSpeed and SSL scan results with the other records so each source can be rechecked independently.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo 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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeReachable but protectedreason: Captcha85% confidence
Attributionmechanism: Challengesource: Current Http Probe
Evidence layersAvailability: Reachable but protectedContent: UnknownDNS: ResolvedRegistration: Unknown
Latest HTTP observationReachable but protectedCaptchaChallenge85%2026-10-11 10:13:51 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-11 10:13:51 UTClast content: 2026-10-09 10:15:22 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.
Last analyzed First positive detection Previous stored snapshot: 11 detections
alphaMountain.ai
Bfore.Ai PreCrime
BitDefender
CRDF
ESET
Fortinet
G-Data
Kaspersky
MalwareURL
SOCRadar
Sophos
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of tradehedgefund.com· checked Sep 25, 2026
81
Needs Work
Performance
FCP
3.63s
First Contentful Paint
LCP
3.78s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
3.63s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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.
Threat First Observed2026-09-23 15:53:11 UTC
Domain ingestion complete. Initial state is marked as alive.
Threat Response Pipeline
Discovery
Analysis
Monitoring
6 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
tradehedgefund.com detected and queued for full analysis
Sep 17, 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.
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+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
2 evidence signal groups linked0 reports recordedLast known active
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.
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 →
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
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · tradehedgefund.com
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches4
Same favicon hash or the same page title as this host.
