icloud-ubication.com returned an HTTP 200 status on 2026-10-08, indicating a successful response to web requests at that time. On the same date, the domain was also flagged by Google Safe Browsing for social engineering threats, highlighting a potential security concern.
Recorded Evidence
On 2026-10-08, Google Safe Browsing identified icloud-ubication.com as associated with social engineering. The domain appeared on the Phishunt blocklist as of 2026-10-08. VirusTotal reported 14 detections out of 92 scanners on 2026-10-05. OTX listed five pulses for this domain as of 2026-10-08. The registrar was Sav.com, LLC, with registration recorded on 2025-08-29, and SSL was issued by Let's Encrypt / YE2.
Interpretation
The collected source observations indicate that multiple security platforms have independently flagged icloud-ubication.com within a short timeframe. These records from Google Safe Browsing, Phishunt, VirusTotal, and OTX suggest the domain has drawn attention for activities that triggered automated or community-based security alerts. The presence of a valid SSL certificate and a high PageSpeed score do not contradict these findings, as they pertain to technical setup rather than security reputation.
Recommended Actions
Review the security records for icloud-ubication.com from Google Safe Browsing, Phishunt, VirusTotal, and OTX before interacting with the domain. Preserve these dated source observations for future comparison and ongoing monitoring. Use the HTTP response and security blocklist data to inform risk assessments and any necessary protective actions regarding this domain.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-12 10:07:52 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-12 10:07:52 UTClast content: 2026-10-12 10:07:52 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.
威胁情报交叉核验 · source references
ScamAdviserPublic lookup
A public ScamAdviser lookup is available. Review its current score and warnings at the source; the existence of a lookup page is not itself a malicious verdict.
Last analyzed First positive detection Previous stored snapshot: 14 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
CyRadar
Forcepoint ThreatSeeker
Fortinet
G-Data
Google Safe Browsing
Lionic
SOCRadar
Sophos
VIPRE
Webroot
网站性能分析
Google PageSpeed Insights — mobile performance audit of icloud-ubication.com· checked Oct 7, 2026
100
Good
Performance
FCP
0.78s
First Contentful Paint
LCP
1.54s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.8s
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 17:41:56 UTC
Telemetry event observed.
Threat First Observed2026-10-07 17:09:50 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 172.234.26.72.
威胁响应 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.
