Skip to security report
This domain has been flagged as malicious
Security engines reporting a detection: 14. Exercise extreme caution — do not enter credentials or personal information.
Domain security and threat intelligence
spotify-clone-xi-indol.vercel.app favicon

spotify-clone-xi-indol.vercel.app

In short

spotify-clone-xi-indol.vercel.app is a Spotify impersonation page detected by PhishDestroy on 2026-10-22. Risk: critical (100/100). Registrar: Vercel. Status: Last known active. Hosting: Amazon.com, Inc. VirusTotal: 14/92 engines flag it. Do not enter credentials or connect a wallet.

“spotify”

Registrar
Vercel
Resolved IP
64.29.17.67
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed HTTP probe
VirusTotal detections: 14/92 Automated brand label: Spotify
VirusTotal
engine detections ·
OTX
community references
Cloudflare Radar
Not recorded
Page captures
open gallery
Domain age
Not recorded
Reports sent
No sent record
Oct 23, 2026 CDN
X Telegram API
Source evidenceVirusTotal 14 / 92 7 sources

VirusTotal

14 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 46,
    "malicious": 14,
    "suspicious": 0,
    "undetected": 32
}
Vendor labels
{
    "ESET": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "Emsisoft": "phishing",
    "Fortinet": "phishing",
    "Netcraft": "malicious",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "Gridinsoft": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Categories
{
    "alphaMountain.ai": "Information Technology, Phishing (alphaMountain.ai)"
}
Registrar
Tucows Domains Inc
Created
2020-01-28T03:03:04Z
Expires
2026-01-28T03:03:04Z
Updated
2025-01-26T03:25:55Z
First seen
2026-10-20T23:30:08Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "64.29.17.131"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "216.198.79.131"
    }
]
Dns at
2026-10-21T18:17:25Z
Jarm
3fd3fd00000000000043d43d00043dc3b2afa8a5ec09b510a8559aff7899fb
Certificate
{
    "san": [
        "*.vercel.app"
    ],
    "issuer": "Google Trust Services / WR1",
    "serial": "f7911168ffa7d0f4135e24792e7a52a8",
    "sha256": "8f46c4a0a289bfde4060d06986f2af761ee62d668dde972e6bef4687ee4f6093",
    "subject": "*.vercel.app",
    "valid_to": "2026-11-27T19:48:08Z",
    "valid_from": "2026-08-29T19:48:09Z"
}
Registration record
{
    "registrar": "Tucows Domains Inc",
    "registrar_iana_id": "69",
    "registrar_url": "http://www.tucows.com",
    "created": "2020-01-28T03:03:04Z",
    "updated": "2025-01-26T03:25:55Z",
    "expires": "2026-01-28T03:03:04Z",
    "status": [
        "clientTransferProhibited",
        "clientUpdateProhibited"
    ],
    "nameservers": [
        "ns1.vercel-dns-3.com",
        "ns2.vercel-dns-3.com",
        "ns3.vercel-dns-3.com",
        "ns4.vercel-dns-3.com"
    ],
    "dnssec": "unsigned"
}
Separate source record · 14 malicious + 0 suspicious / 92 · 2026-10-21 18:17:05 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-21T18:17:05Z
fetched_at
2026-10-22T23:30:04Z
stats
{"timeout":0,"harmless":46,"malicious":14,"suspicious":0,"undetected":32}

URLScan

Malicious

Open report
URLScanOriginal source recordObserved: 20 fields

Observed: · Retrieved:

Uuid
01a165bc-7bd6-77b1-90f7-4821e2a94e1e
Final url
https://spotify-clone-xi-indol.vercel.app/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://spotify-clone-xi-indol.vercel.app/",
        "from": "http://spotify-clone-xi-indol.vercel.app/",
        "status": 307
    }
]
Ip
216.198.79.131
Contacted IP addresses
[
    "216.198.79.131"
]
Asns
[
    "16509"
]
Countries
[
    "US"
]
Document hash
13795bc4b3129e36b4f1498a3014e0ce549402117ed2d5d8a867b3be7085a637
Script hashes
[
    "af624edeff0237b4312d37c24742e22273417e7945035c77ddba0fdc79cdeb0d"
]
Globals
[
    "__reactRouterVersion"
]
Tls
{
    "san": [
        "*.vercel.app"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WR1",
    "subject": "*.vercel.app",
    "protocol": "TLS 1.3",
    "valid_to": "2026-11-27T19:48:08Z",
    "valid_from": "2026-08-29T19:48:09Z"
}
Domain age days
2
Apex age days
2
Tls age days
54
Tls valid days
89
Requests
38
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "spotify"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Spotify"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "server": "Vercel",
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=63072000; includeSubDomains; preload"
}
Separate monitor record · 2026-10-23 03:30 UTC

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

record_source
domain_monitor.urlscan
uuid
01a165bc-7bd6-77b1-90f7-4821e2a94e1e
score
100
malicious
true
result_at
2026-10-23T03:30:29Z
enriched_at
2026-10-23T08:18:36Z
source_timestamps
{"urlscan_result_at":"2026-10-23 05:30:29","urlscan_enriched_at":"2026-10-23 10:18:36"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

93 / 100 · heuristic score · 1 brand references · 1 classifications

Open report
Separate monitor score · 10 / 100 · 2026-10-23T02:20:19Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
10
analyzed_at
2026-10-23T02:20:19Z
source_timestamp
2026-10-23 04:20:19
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 22 fields
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "count": 2,
    "domain": "vercel.app",
    "issuers": [
        "letsencrypt.org",
        "pki.goog"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-21T15:30:10Z",
    "first": "2026-10-21T15:30:10Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 938
}
Page title and metadata
{
    "title": "spotify"
}
Trackers
{
    "requests": 18
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 29,
        "tls": 12,
        "wait": 18,
        "connect": 8,
        "download": 0
    },
    "response_ms": 67
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_128_GCM_SHA256",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 457,
    "co2_grams": 0,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "205.251.197.116",
            "host": "ns3.vercel-dns-3.com"
        },
        {
            "ip": "205.251.193.92",
            "host": "ns1.vercel-dns-3.com"
        },
        {
            "ip": "205.251.194.149",
            "host": "ns2.vercel-dns-3.com"
        },
        {
            "ip": "205.251.199.60",
            "host": "ns4.vercel-dns-3.com"
        }
    ],
    "zone": "vercel.app"
}
Location
{
    "ip": "216.198.79.195",
    "asn": "16509",
    "org": "Amazon.com, Inc.",
    "city": "Walnut",
    "country": "US"
}
Ssl
{
    "issuer": "Google Trust Services / WR1",
    "subject": "*.vercel.app"
}
DNS records
{
    "A": [
        "216.198.79.195",
        "64.29.17.195"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=63072000; includeSubDomains; preload",
    "message": "Site is compatible with the HSTS preload list!",
    "compatible": true
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": "max-age=63072000; includeSubDomains; preload",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "216.198.79.195",
    "family": 4
}
Redirects
{
    "chain": [
        "https://spotify-clone-xi-indol.vercel.app"
    ]
}
Tech stack
{
    "technologies": [
        "Vercel",
        "HSTS"
    ]
}
HTTP headers
{
    "headers": {
        "server": "Vercel",
        "content-type": "text/html; charset=utf-8",
        "strict-transport-security": "max-age=63072000; includeSubDomains; preload"
    }
}

Questions about spotify-clone-xi-indol.vercel.app

Is spotify-clone-xi-indol.vercel.app legit?

No. PhishDestroy classifies spotify-clone-xi-indol.vercel.app as a Spotify impersonation page (risk: critical, 100/100); it was first detected on 2026-10-22. VirusTotal: 14/92 engines flag it. Treat the site as unsafe.

Is spotify-clone-xi-indol.vercel.app safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on spotify-clone-xi-indol.vercel.app. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used spotify-clone-xi-indol.vercel.app?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 7 captures

All capture links and hashes (7)

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Spotify report ↗
IP Context Vercel shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider Vercel US(US)
Abuse contactabuse@vercel.com
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 23, 2026
DOM Analysisanalyzed Oct 23, 2026score 93/1001 brand signal
Submitted URLhttp://spotify-clone-xi-indol.vercel.app/
Favicon Hash
Observed page title
spotify
Automated brand references
Spotify
TLS Certificate
Issued by WR1 · stored validity ends in 33 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
64.29.17.67
Network ASN
AS16509
Organization
Vercel, Inc
Observed location
Walnut, US
Server header
Vercel

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
WR1
Valid from
2026-08-29 19:48:09
Valid until
2026-11-27 19:48:08
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint8f46c4a0a289bfde4060d06986f2af761ee62d668dde972e6bef4687ee4f6093
Certificate names · 1 SAN
  • *.vercel.app

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-25 03:29:24 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Stale Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-25 03:29:24 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-25 03:29:24 UTC last content: 2026-10-25 03:29:24 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.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

14 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
BitDefender
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Netcraft
SOCRadar
Sophos
Webroot

Archived Evidence

Wayback Machine Snapshot
View Archive
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://spotify-clone-xi-indol.vercel.app/
Final URL: https://spotify-clone-xi-indol.vercel.app/
spotify
Response
HTTP 200
HTML body
457 B
Compressed
296 B
Links
0 internal · 0 external
Selected response headers
Cache-Control: public, max-age=0, must-revalidate
Content-Type: text/html; charset=utf-8
Server: Vercel
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 14
Accept-Ranges
bytes
Access-Control-Allow-Origin
*
Age
54798
Cache-Control
public, max-age=0, must-revalidate
Content-Disposition
inline
Content-Length
457
Content-Type
text/html; charset=utf-8
Date
Wed, 21 Oct 2026 15:29:17 GMT
Etag
"346113af00dd2c9716ca2a10814ebe66"
Last-Modified
Wed, 21 Oct 2026 00:15:58 GMT
Server
Vercel
Strict-Transport-Security
max-age=63072000; includeSubDomains; preload
X-Vercel-Cache
HIT
X-Vercel-Id
fra1::kp798-1792596557643-a0130df41556

Values retained by the collector; long values may be shortened during collection.

Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history2

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→live_content

    content_served

  2. Domain monitor · First collection record

    Reachable

All retained availability observations12

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 04:29:24.000000
    Evidence SHA-256
    dfc55d75ee544e013b8f864878b3310c05ab2659eaaf440441bf20c01ae9d478
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 04:29:24
    Evidence reason
    alive_content
  2. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 04:29:24.000000
    Evidence SHA-256
    dfc55d75ee544e013b8f864878b3310c05ab2659eaaf440441bf20c01ae9d478
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 04:29:24
    Evidence reason
    alive_content
  3. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 12:33:59.000000
    Evidence SHA-256
    669899c1fce475814cc620848cd129179526e2eddf91f8cc3bab639fc4b11c33
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 12:33:59
    Evidence reason
    alive_content
  4. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 12:33:59.000000
    Evidence SHA-256
    669899c1fce475814cc620848cd129179526e2eddf91f8cc3bab639fc4b11c33
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 12:33:59
    Evidence reason
    alive_content
  5. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 00:36:39.000000
    Evidence SHA-256
    485cd98debc9f047e1feb9fdc7a8e00ce1fa37c68fc26f931b6dbeab4285116b
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 00:36:39
    Evidence reason
    alive_content
  6. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 00:36:39.000000
    Evidence SHA-256
    485cd98debc9f047e1feb9fdc7a8e00ce1fa37c68fc26f931b6dbeab4285116b
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 00:36:39
    Evidence reason
    alive_content
  7. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 12:38:04.000000
    Evidence SHA-256
    951e6f1d5d6eddc5222d9b0910f6549e3d39f8d9b3d90d029eedabf8f3a2edda
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-23 12:38:04
    Evidence reason
    alive_content
  8. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 12:38:04.000000
    Evidence SHA-256
    951e6f1d5d6eddc5222d9b0910f6549e3d39f8d9b3d90d029eedabf8f3a2edda
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-23 12:38:04
    Evidence reason
    alive_content
  9. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 04:32:11.000000
    Evidence SHA-256
    ca0c593b39577023d6c8c55d2c9b585be0d43d145d5079a3e9c436987cdb614e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-23 04:32:11
    Evidence reason
    alive_content
  10. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 04:32:11.000000
    Evidence SHA-256
    ca0c593b39577023d6c8c55d2c9b585be0d43d145d5079a3e9c436987cdb614e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-23 04:32:11
    Evidence reason
    alive_content
  11. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 00:31:44.000000
    Evidence SHA-256
    48e5309ba7bc3be527d0711917eebf9781a9e96a98bfcb97ad23700996344b59
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-23 00:31:44
    Evidence reason
  12. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 00:31:44.000000
    Evidence SHA-256
    48e5309ba7bc3be527d0711917eebf9781a9e96a98bfcb97ad23700996344b59
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-23 00:31:44
    Evidence reason

Recorded activity

4 entries
  1. VirusTotal

    14/92 engine detections

    View source
  2. Added to PhishDestroy

    spotify-clone-xi-indol.vercel.app

    View source
  3. URLScan

    Page captured

    View source
  4. Wayback Machine

    Page archived

    View source

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

spotify-clone-xi-indol.vercel.app

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
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.

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft • optional AI wording assistance requires separate consent

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including spotify-clone-xi-indol.vercel.app)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Official reporting routes

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 →
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/spotify-clone-xi-indol.vercel.app"
  title="PhishDestroy threat report for spotify-clone-xi-indol.vercel.app"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>