Skip to security report
Analytics Dashboard
Domain security and threat intelligence
syed-khasim.github.io favicon

syed-khasim.github.io

In short

syed-khasim.github.io is a Spotify impersonation page detected by PhishDestroy on 2026-09-11. Risk: critical (80/100). Registrar: GitHub Pages. Status: Content unavailable. VirusTotal: 8/89 engines flag it. Do not enter credentials or connect a wallet.

“Spotify web-music player”

Registrar
GitHub Pages
Resolved IP
185.199.111.153
PhishDestroy assessment Critical
Availability Content unavailable Content was unavailable in the latest observation Observed · HTTP probe
Risk signals
VirusTotal detections: 8/89 Automated brand label: Spotify
Sep 11, 2026 CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 8. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
8 / 89
engine detections
Google Safe Browsing
No threat flag
Page captures
4
open gallery
Source evidenceVirusTotal 8 / 89 5 sources

VirusTotal

8 / 89 engine detections

Open report

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

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

Analysis

Critical
VirusTotal
8 / 89
Page captures
4
Page captures Source results Registration record

PhishDestroy threat report

Overview

syed-khasim.github.io is a GitHub Pages site that impersonated Spotify behind the title "Spotify web-music player". It targeted people who would recognise and trust the Spotify brand. PhishDestroy first saw it on 2026-09-11, and it went offline that same day. When last checked on 2026-10-19, the address was dead and served no content at its root.

How the scam works

Pages like this copy the look of Spotify's web player so a visitor assumes they are on the real service. The victim is then steered toward signing in or confirming account details, and anything typed goes to the operator instead of Spotify. The usual losses are the Spotify login itself and any other account that reuses the same password. Some variants also push a fake billing or subscription prompt to collect card details.

Evidence

Eight of 89 VirusTotal engines flagged the site on 2026-09-11: alphaMountain.ai, Emsisoft, Forcepoint ThreatSeeker, G-Data, Gridinsoft, Netcraft, Sophos and Webroot. That is a modest share of engines, but it comes from a spread of unrelated vendors rather than one outlier. urlscan.io independently returned a malicious verdict and recognised Spotify branding on the page. The domain is listed on the PhishDestroy blocklist.

Infrastructure

The page sat on a github.io subdomain, a free hosting space anyone can create in minutes without buying a domain. The hosting address resolves to GitHub's US-based Pages network, which is shared by a huge number of legitimate sites. Blocking that IP would therefore cause collateral damage, so defenders should block the specific hostname instead. The site going dark on the same day it was detected fits the disposable nature of a throwaway project page.

What to do

If you entered your Spotify credentials here, change your Spotify password right away and sign out of all sessions from your account settings. Also change the password anywhere else you reused it, and turn on two-factor authentication where available. Check your Spotify plan and payment history for changes you did not make. If you entered card details, contact your bank to block the card. Defenders should block the full hostname rather than the shared GitHub IP and report any reappearance to GitHub for takedown.

Useful links

urlscan.io scan and screenshotVirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review

Collected source details

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

URLScan · 2026-09-10T01:01:57Z

Observed: · Retrieved:

Uuid
01a088d5-d6ce-7740-80d8-390075fa8f99
Final url
https://syed-khasim.github.io/Spotify/
Status
200
Redirected
same-domain
Redirects
[
    {
        "to": "https://syed-khasim.github.io/Spotify/",
        "from": "https://syed-khasim.github.io/Spotify",
        "status": 301
    }
]
Ip
2606:50c0:8002::153
Contacted domains
[
    "cdnjs.cloudflare.com",
    "fonts.gstatic.com",
    "fonts.googleapis.com"
]
Contacted IP addresses
[
    "142.250.154.94",
    "2a00:1450:4001:c25::5f",
    "104.17.25.14",
    "2606:50c0:8002::153"
]
Asns
[
    "15169",
    "13335",
    "54113"
]
Countries
[
    "US",
    "DE"
]
Document hash
44bc516dcb35cdf4a2dbc672debcfbc6eb462e7e5fa8ef7d3148f220791cc7b9
Tls
{
    "san": [
        "*.github.com",
        "*.github.io",
        "*.githubusercontent.com",
        "github.com",
        "github.io",
        "githubusercontent.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YR1",
    "subject": "*.github.io",
    "protocol": "TLS 1.3",
    "valid_to": "2026-10-31T23:38:01Z",
    "valid_from": "2026-08-02T23:38:02Z"
}
Domain age days
151
Apex age days
151
Tls age days
38
Tls valid days
89
Requests
22
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 96,
        "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": "GitHub.com",
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=31556952"
}
Cloudflare Radar · 2026-09-11T03:30:38Z

Observed: · Retrieved:

Uuid
efc06add-6c77-4263-bb53-33532fba44ee
Final url
https://syed-khasim.github.io/
Status
404
History
[
    {
        "url": "https://syed-khasim.github.io/",
        "status": 404
    }
]
DOM structure hash
35bbdd99a249decabdc93f6b809b030db834533d4d78fe69529a214489fae670
Document hash
70d613e3acfba24fd2876fcbacaf639e1e111ef4d54baf70761c47673f37d6a3
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "syed-khasim.github.io",
        "type": "A",
        "value": "185.199.111.153"
    },
    {
        "name": "syed-khasim.github.io",
        "type": "A",
        "value": "185.199.108.153"
    },
    {
        "name": "syed-khasim.github.io",
        "type": "A",
        "value": "185.199.109.153"
    },
    {
        "name": "syed-khasim.github.io",
        "type": "A",
        "value": "185.199.110.153"
    },
    {
        "name": "syed-khasim.github.io",
        "type": "AAAA",
        "value": "2606:50c0:8000::153"
    },
    {
        "name": "syed-khasim.github.io",
        "type": "AAAA",
        "value": "2606:50c0:8001::153"
    },
    {
        "name": "syed-khasim.github.io",
        "type": "AAAA",
        "value": "2606:50c0:8002::153"
    },
    {
        "name": "syed-khasim.github.io",
        "type": "AAAA",
        "value": "2606:50c0:8003::153"
    }
]
Dnssec valid
false
Ip
185.199.111.153
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "created": "2013-03-08T19:12:48Z",
    "updated": "2026-08-12T09:08:04Z",
    "expires": "2027-03-08T19:12:48Z",
    "nameservers": [
        "ns-692.awsdns-22.net",
        "ns-1622.awsdns-10.co.uk",
        "dns1.p05.nsone.net",
        "dns2.p05.nsone.net",
        "dns3.p05.nsone.net"
    ]
}
VirusTotal · 2026-10-17T07:14:23Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 49,
    "malicious": 10,
    "suspicious": 0,
    "undetected": 33
}
Vendor labels
{
    "ESET": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "Emsisoft": "phishing",
    "Netcraft": "malicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Registrar
MarkMonitor Inc.
Created
2013-03-08T19:41:10Z
Expires
2027-03-08T19:12:48Z
Updated
2026-08-12T09:08:04Z
First seen
2026-09-09T04:10:53Z
DNS records
[
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "digicert.com"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "185.199.110.153"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "185.199.108.153"
    },
    {
        "ttl": 3600,
        "type": "AAAA",
        "value": "2606:50c0:8003::153"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "sectigo.com"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "letsencrypt.org"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "letsencrypt.org"
    },
    {
        "ttl": 3600,
        "type": "AAAA",
        "value": "2606:50c0:8000::153"
    },
    {
        "ttl": 3600,
        "type": "AAAA",
        "value": "2606:50c0:8001::153"
    },
    {
        "ttl": 3600,
        "type": "AAAA",
        "value": "2606:50c0:8002::153"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "sectigo.com"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "digicert.com"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "185.199.109.153"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "185.199.111.153"
    }
]
Dns at
2026-10-17T07:19:36Z
Jarm
29d3fd00029d29d00041d41d00041d6b5eefa2404a56c2ced79a0d16afe36c
Certificate
{
    "san": [
        "*.github.com",
        "*.github.io",
        "*.githubusercontent.com",
        "github.com",
        "github.io",
        "githubusercontent.com"
    ],
    "issuer": "Let's Encrypt / YR1",
    "serial": "6a65e5d3279ba564a4de74eb5d64478dbb8",
    "sha256": "f2f9a159ce50a0a168b3eaeaf2fced5addd49ba38e2bf63248f057a139fc7856",
    "subject": "*.github.io",
    "valid_to": "2026-12-29T23:44:45Z",
    "valid_from": "2026-09-30T23:44:46Z"
}
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "registrar_iana_id": "292",
    "registrar_url": "http://www.markmonitor.com",
    "created": "2013-03-08T19:12:48Z",
    "updated": "2025-02-25T20:53:31Z",
    "expires": "2027-03-08T00:00:00Z",
    "status": [
        "clientDeleteProhibited",
        "clientTransferProhibited",
        "clientUpdateProhibited"
    ],
    "nameservers": [
        "dns1.p05.nsone.net",
        "dns2.p05.nsone.net",
        "dns3.p05.nsone.net",
        "ns-1622.awsdns-10.co.uk",
        "ns-692.awsdns-22.net"
    ],
    "dnssec": "unsigned"
}

Questions about syed-khasim.github.io

Is syed-khasim.github.io legit?

No. PhishDestroy classifies syed-khasim.github.io as a Spotify impersonation page (risk: critical, 80/100); it was first detected on 2026-09-11. VirusTotal: 8/89 engines flag it. Treat the site as unsafe.

Is syed-khasim.github.io safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on syed-khasim.github.io. 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 syed-khasim.github.io?

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 · 4 captures

Primary capture 1 / 4
SourcePrimary capture
Recorded2026-09-11 03:24 UTC
StateStored capture
Position1 / 4
Open capture Wayback Download

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Spotify report ↗
IP Context GitHub Pages shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider GitHub Pages
Abuse contact["abusecomplaints@markmonitor.com", "5779f178b3e0e3c7s@"]
HTTP Status404 Not Found
Technical detailsProvenance & timestamps
First DetectedSep 11, 2026
Submitted URLhttp://syed-khasim.github.io/Spotify
Observed page title
Spotify web-music player
Automated brand references
Spotify
TLS Certificate
Issued by YR1 · stored validity ends in 8 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
185.199.111.153
Observed location
US
Server header
GitHub.com

Edge-IP reputation is not attributed to this domain.

Nameservers 5

  • ns-692.awsdns-22.net
  • ns-1622.awsdns-10.co.uk
  • dns1.p05.nsone.net
  • dns2.p05.nsone.net
  • dns3.p05.nsone.net

Location describes the IP network.

TLS certificate

Issuer
YR1
Valid from
2026-08-02 23:38:02
Valid until
2026-10-31 23:38:01
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintf2f9a159ce50a0a168b3eaeaf2fced5addd49ba38e2bf63248f057a139fc7856
Certificate names · 6 SANs
  • *.github.com
  • *.github.io
  • *.githubusercontent.com
  • github.com
  • github.io
  • githubusercontent.com

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

viewdns.info · 185.199.111.153rapiddns.io

Latest Classified Outcome 2026-10-23 01:23:36 UTC

Primary outcome Inactive reason: Http No Content 70% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Root path has no content Content: Absent At Root DNS: Stale Registration: Unknown
Latest HTTP observation Inactive Http No Content 70% 2026-10-23 01:23:36 UTC
RDAP registration Unknown
Observed timeline current episode first observed: 2026-10-09 01:25:19 UTC first terminal observation: 2026-10-01 01:38:57 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.
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

8 / 89 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
Emsisoft
Forcepoint ThreatSeeker
G-Data
Gridinsoft
Netcraft
Sophos
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of syed-khasim.github.io · checked Sep 11, 2026

100
Good
Performance
FCP
0.8s
First Contentful Paint
LCP
0.8s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.8s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details3

Availability observations

Outcome first observed
Observation window ends
Estimate basis
first_observation_only

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

Check for cloaking

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

Page titles differ

http_other: raw=http_404; http=404; via=http_proxy; server=GitHub.com

Browser
Spotify web-music player
Crawler
Site not found · GitHub Pages
syed-khasim.github.io
Saved result
Cloaked / Filtered
Stored observation history11

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→inactive

    http_no_content

  2. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  3. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  4. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  5. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

Earlier observations 6
  1. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  2. Availability monitor · Recorded state

    Unknown→inactive

    http_no_content

  3. Availability monitor · Recorded state

    Unknown→inactive

    hosting_placeholder · placeholder_page

  4. Availability monitor · Recorded state

    Unknown→inactive

    hosting_placeholder · placeholder_page

  5. Availability monitor · Recorded state

    Unknown→inactive

    hosting_placeholder · placeholder_page

  6. Availability monitor · Recorded state

    Reachable→Unavailable

Recorded activity

3 entries
  1. Google Safe Browsing

    No threat flag

    View source
  2. VirusTotal

    8/89 engine detections

    View source
  3. Added to PhishDestroy

    syed-khasim.github.io

    View source

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal 8 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

3 evidence signal groups linked 0 stored notification records Content unavailable

Listed domains receive at least one abuse report; this entry has no retained notification history.

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.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 →

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

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 syed-khasim.github.io)
  • 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

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

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

Live Threat Feed Appeal This Listing
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.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

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.

Request a correction or appeal How PhishDestroy works
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/syed-khasim.github.io"
  title="PhishDestroy threat report for syed-khasim.github.io"
  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>