minecamff.com returned an HTTP status 200 on 2026-10-13, which is a standard code for successful responses. The domain was also observed in a PhishDestroy internal listing on a similar timeline.
Recorded Evidence
On 2026-10-13, the HTTP status for minecamff.com was recorded as 200. The domain appeared in the PhishDestroy internal listing on the same date. OTX checked the domain on 2026-10-13 and recorded 32 pulses. VirusTotal reviewed the domain on 2026-10-09, with 6 detections out of 92 total scanners. The domain was registered with DYNADOT LLC on 2025-10-30.
Interpretation
The PhishDestroy internal listing documents the presence of minecamff.com in its catalogue, which serves as an internal reference point. VirusTotal provides a measurement of how many security scanners detected the domain, offering a comparative view of its recognition across different tools. OTX records the number of pulses, reflecting its attention in external threat intelligence feeds. These sources together provide a snapshot of the domain’s technical profile and its observation across multiple security platforms.
Recommended Actions
For minecamff.com, retain the HTTP status, PhishDestroy internal listing, OTX pulse count, and VirusTotal detection records for ongoing reference. Compare future observations from these sources to monitor any changes in the domain’s recorded evidence.
Latest HTTP observation未知Empty Response20%2026-10-13 01:35:41 UTC
RDAP registration未知
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.
技术 · 1 identified
N
Nginx
Web serversReverse proxies
Nginx is a web server that can also be used as a reverse proxy, load balancer, mail proxy and HTTP cache.
Last analyzed Previous stored snapshot: 6 detections
alphaMountain.ai
Forcepoint ThreatSeeker
Fortinet
卡巴斯基
Seclookup
Sophos
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-10-12 21:38:41 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 34.41.139.193.
威胁响应 Pipeline
发现
Analysis
Monitoring
9 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.
(US)
