The domain spotify-plus.com was observed with a Google Safe Browsing social engineering flag on 2026-10-12, providing a dated detection record. Additional sources document its presence in security intelligence databases, offering a broader view of its recorded profile.
Recorded Evidence
Google Safe Browsing flagged spotify-plus.com for social engineering on 2026-10-12. VirusTotal recorded 18 detections out of 92 scanners for this domain on 2026-10-02. OTX included spotify-plus.com in 4 pulses as of 2026-10-12. PhishDestroy listed the domain in its internal catalogue, and the registration date was recorded as 2026-08-22.
Interpretation
The VirusTotal record contains a measurement of scanner detections, documenting how many security vendors flagged spotify-plus.com at the time of its review. Google Safe Browsing provides a dated observation of a social engineering detection. OTX references show the domain's inclusion in multiple intelligence-sharing pulses, expanding the context of its recorded activity.
Recommended Actions
For spotify-plus.com, retain the VirusTotal and Google Safe Browsing records for ongoing comparison with future scans. Preserve the OTX pulse references as part of its intelligence-sharing documentation. Review the PhishDestroy internal listing for any updates. Use these recorded observations to inform further technical or security assessments.
探测与规避分析
隐身和流量分配检查
尚未扫描目前尚未记录到爬虫与浏览器之间的差异
针对该主机的爬虫与浏览器观察记录，以及针对“Keitaro”式流量分配系统的实时指纹检测。
存储的隐身标志
尚未扫描
上次隐形扫描
扫描说明:timeout: raw=timeout; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='spotify-plus.com', port=80): Max retries exceeded with url: / (Caused by ConnectTimeoutErr
Latest HTTP observation未知Probe Inconclusive20%2026-10-12 10:01:03 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.
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-12 09:46:24 UTC
Telemetry event observed.
Threat First Observed2026-10-12 09:45:45 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 38.54.63.61.
威胁响应 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)
