Malware Malware Security Risks Parked & For Sale Domains Security threats
証拠の概要
クリティカル
VirusTotal
9/92
OTX
31 community refs
URLScan
Stored capture
Assessment
The domain joshtest.com was observed on 2026-10-08, with VirusTotal recording 9 detections out of 92 scanners on 2026-09-29. Additional documentation includes its internal listing in the PhishDestroy catalogue, which provides another source for reference.
Recorded Evidence
VirusTotal checked joshtest.com on 2026-09-29, reporting 9 detections from 92 total scanners. OTX reviewed the domain on 2026-10-08, recording 31 pulses. The domain was internally listed by PhishDestroy as of 2026-10-08. Registration was documented with Amazon Registrar, Inc. on 2024-05-24.
Interpretation
The evidence from VirusTotal, OTX, and PhishDestroy offers a variety of recorded observations for joshtest.com, covering detection counts and catalogue listing. These dated records allow for comparison of findings across sources, but do not indicate any change or trend between them.
Recommended Actions
For joshtest.com, it is advisable to preserve the VirusTotal, OTX, and PhishDestroy records for ongoing reference. Comparing these sources can support tracking future developments or new evidence. Continued monitoring across these platforms is recommended to stay informed about joshtest.com's documented status.
Extracted from stored page analysis
Observed indicators
2 wallet · 1 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcome非アクティブreason: Domain For Sale80% confidence
Attributionmechanism: Parking Or Lifecycle Pagesource: Current Http Probe
Evidence layersAvailability: Non Threat ContentContent: Replaced Or ParkedDNS: ResolvedRegistration: Unknown
Latest HTTP observation非アクティブDomain For SaleParking Or Lifecycle Page80%2026-10-11 01:34:02 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-09 10:07:03 UTClast content: 2026-10-09 10:07:03 UTCcurrent episode first observed: 2026-10-09 22:07:16 UTCobserved RIP window: 2026-10-09 10:07:03 UTC → 2026-10-09 22:07:16 UTC · 12.00hmidpoint estimate ≈ 2026-10-09 16:07:09 UTC · precision medium · basis bounded
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.
使用技術 · 7 identified
Google Cloud
IaaS
Google Cloud is a suite of cloud computing services.
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.
Domain Status Transition2026-10-09 22:07:16 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-10-08 00:03:07 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 34.123.0.161.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
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.
