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.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
저장된 은신 플래그
아직 스캔되지 않았습니다
마지막 은폐 스캔
스캐너 메모:timeout: raw=timeout; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='spotify-plus.com', port=80): Max retries exceeded with url: / (Caused by ConnectTimeoutErr
TDS 지문 인식 실시간 확인
이 패널이 열려 있을 때 PhishDestroy 스캐너에서 실행되는 7개의 케이타로 지문과 크롤러 대 브라우저 비교 결과.
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)
