trackjoa.cc was first observed on 2026-10-11, with a record from that date documenting its presence in the PhishDestroy internal listing. The domain was also registered on 2026-10-01, providing a clear reference point for its timeline in public records.
Recorded Evidence
According to records dated 2026-10-11, trackjoa.cc appeared on both the MetaMask and SEAL external blocklists. The domain was registered through NAMECHEAP INC on 2026-10-01. Additionally, PhishDestroy internally listed the domain on 2026-10-11, further contributing to its documented security profile.
Interpretation
The PhishDestroy source contains a listing for trackjoa.cc, which records its inclusion in an internal security database. External blocklist entries from MetaMask and SEAL provide additional context, each documenting the domain's status on their respective lists. These sources collectively offer a snapshot of how trackjoa.cc was referenced by multiple security intelligence providers on the same date.
Recommended Actions
For ongoing monitoring, retain the MetaMask and SEAL blocklist records for trackjoa.cc as reference points. Compare future external blocklist entries and PhishDestroy listings to these documented sources to track any changes in the domain's security profile.
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.
Stored cloaking flag
Not yet scanned
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 08:31:20 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-11 08:31:20 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.
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-10-11 08:31:20 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 142.11.252.73.
Threat Response Pipeline
Discovery
Analysis
Monitoring
5 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.
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.
4 evidence signal groups linked0 reports recordedUnverified
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 · trackjoa.cc
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.
(IS)
