On 2026-10-07, Phishunt listed spotify-payment.click on its external blocklist, marking it as a domain of interest for security monitoring. The domain achieved a Pagespeed performance score of 100 on the same date, indicating a technically responsive site at that time.
Recorded Evidence
VirusTotal recorded 15 detections out of 92 scanners for spotify-payment.click on 2026-09-29. OTX registered 4 threat intelligence pulses for the domain on 2026-10-07. The domain was registered with Sav.com, LLC on 2026-02-14. Pagespeed measured its performance score as 100 on 2026-10-07. Phishunt added spotify-payment.click to its external blocklist on 2026-10-07.
Interpretation
The evidence from VirusTotal, OTX, Pagespeed, and Phishunt provides a range of technical and security observations for spotify-payment.click. Each source offers a distinct perspective, with blocklist and threat intelligence records highlighting external monitoring, while performance metrics reflect site responsiveness. The dates of these observations allow for comparison of the domain's status across different platforms within a close timeframe.
Recommended Actions
Preserve the VirusTotal, OTX, Pagespeed, and Phishunt records for spotify-payment.click as reference points for future review. Compare these dated observations to new data from the same sources to monitor any changes in detection or blocklist status. Use the recorded evidence to inform any decisions regarding engagement with the domain.
DOM Analysisanalyzed 2026年10月9日score 98/1001 brand signal
Submitted URLhttps://spotify-payment.click/
Favicon Hash
ICANN OVERSIGHT
认证和 RAA 背景
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-13 10:08:07 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 10:08:07 UTClast content: 2026-10-13 10:08:07 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.
Last analyzed Previous stored snapshot: 15 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
Gridinsoft
卡巴斯基
LevelBlue
Lionic
Seclookup
Sophos
VIPRE
Webroot
网站性能分析
Google PageSpeed Insights — mobile performance audit of spotify-payment.click· checked Oct 7, 2026
100
Good
Performance
FCP
0.77s
First Contentful Paint
LCP
0.77s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
89ms
Total Blocking Time
SI
0.98s
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.
Threat First Observed2026-10-07 05:30:54 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 34.76.205.124.
威胁响应 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.
(US)
