Security engines reporting a detection: 2. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
Stored registration data identifies NameSilo as the registrar. PhishDestroy maintains separate registrar investigations; that broader material is contextual and is not an independent detection for this domain.
icloudmex-lost.com was observed on 2026-10-07 with a Google Safe Browsing flag for social engineering threats, indicating a potential risk to users. Additionally, the domain achieved a perfect PageSpeed performance score on the same date.
Recorded Evidence
On 2026-10-07, Google Safe Browsing flagged icloudmex-lost.com for social engineering threats. The domain was listed on the Phishunt external blocklist as of 2026-10-07. VirusTotal recorded 2 detections out of 92 scanners on 2026-10-01. The domain was registered with NameSilo, LLC on 2025-09-26. Internal listing by Phishdestroy was also noted.
Interpretation
The collected evidence from Google Safe Browsing, Phishunt, and VirusTotal provides a multi-source perspective on the domain's risk profile. The presence of both external and internal listings, along with recent detection records, highlights the importance of reviewing such domains across several security platforms. The registration and observation dates offer context for the timeline of these findings.
Recommended Actions
It is advisable to monitor icloudmex-lost.com using Google Safe Browsing and VirusTotal records for any changes in threat detection. Retain the blocklist entries from Phishunt and internal Phishdestroy listings for ongoing comparison. Review the domain's registration details and performance scores to inform future assessments and security decisions related to this domain.
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.
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.
Google PageSpeed Insights — mobile performance audit of icloudmex-lost.com· checked Oct 7, 2026
100
Good
Performance
FCP
0.78s
First Contentful Paint
LCP
1.52s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.81s
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.
Status Check2026-10-07 05:34:34 UTC
Telemetry event observed.
Threat First Observed2026-10-07 05:34:03 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 172.237.129.242.
Threat Response Pipeline
Discovery
Analysis
Monitoring
9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
icloudmex-lost.com detected and queued for full analysis
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.
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 · icloudmex-lost.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.
(US)
PhishDestroy Investigation
