Skip to security report
Analytics Dashboard
Domain security and threat intelligence
satyam-kumar-mishra.github.io favicon

satyam-kumar-mishra.github.io

In short

satyam-kumar-mishra.github.io is a Netflix impersonation page detected by PhishDestroy on 2026-09-14. Risk: critical (100/100). Registrar: GitHub Pages. Status: Content unavailable. Hosting: Fastly, Inc. VirusTotal: 9/89 engines flag it. Google Safe Browsing flags it. Do not enter credentials or connect a wallet.

“Document”

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

VirusTotal

9 / 89 engine detections

Open report

Google Safe Browsing

Threat flag recorded

Open report

OTX

no community references

Open report

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

Analysis

Critical
VirusTotal
9 / 89
Page captures
7
Page captures Source results Registration record

PhishDestroy threat report

Overview

satyam-kumar-mishra.github.io is a phishing page that impersonated Netflix and targeted subscribers who could be persuaded to sign in or update their account. It was hosted as a personal project site on GitHub Pages. PhishDestroy first saw it on 2026-09-14, and it went offline the next day, 2026-09-15. A check on 2026-10-19 found the site still dead, with no content served at the root.

How the scam works

Netflix lures usually arrive as emails or texts claiming a payment failed or the account is about to be suspended. They link to a copy of the Netflix sign-in or billing page. Anything typed there, such as email, password and often full card details, goes straight to the operator. The stolen data is then used to take over accounts, resell logins or run card fraud. The page carried the generic browser title "Document", which is the default in many HTML templates, while its content was classified as Netflix impersonation.

Evidence

Nine of 89 VirusTotal engines flagged the site on 2026-09-14. Among them were Google Safe Browsing, Netcraft, Fortinet, Sophos, Emsisoft, G-Data, Gridinsoft and alphaMountain.ai. That is a modest count, but the vendors span browser protection, anti-phishing feeds and endpoint security, so the verdicts are independent of each other. Google Safe Browsing labeled it SOCIAL_ENGINEERING. urlscan.io returned a malicious verdict and identified Netflix as the imitated brand. The site is also on the PhishDestroy blocklist.

Infrastructure

The operator did not register a domain. The page ran as a subdomain of GitHub's free static hosting, which costs nothing and borrows the reputation of a trusted platform. It resolved to GitHub Pages' shared Fastly network in the United States, the same front end that serves countless legitimate project sites. Because this setup is so cheap, it can be abandoned and recreated under a new account within minutes, and the page did go dark a day after detection.

What to do

If you entered your Netflix password here, change it now, and also change it on any other service where you reused it. Then sign out of all devices from your Netflix account settings. If you submitted card details, call your bank to block the card and dispute any charges you don't recognize. Be wary of follow-up messages about your account, and always reach Netflix by typing its address yourself. Defenders should block this hostname and report any copies to GitHub and to Netflix's security team, since similar pages tend to reappear under fresh usernames.

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-14T11:12:41Z

Observed: · Retrieved:

Uuid
01a09f9e-6a8a-71c8-8002-b9e27a37f81f
Final url
https://satyam-kumar-mishra.github.io/CLONE1/
Status
200
Redirected
same-domain
Redirects
[
    {
        "to": "https://satyam-kumar-mishra.github.io/CLONE1/",
        "from": "https://satyam-kumar-mishra.github.io/CLONE1",
        "status": 301
    }
]
Ip
185.199.109.153
Ptr
cdn-185-199-109-153.github.com
Contacted domains
[
    "cdnjs.cloudflare.com"
]
Contacted IP addresses
[
    "104.17.24.14",
    "185.199.109.153"
]
Asns
[
    "13335",
    "54113"
]
Countries
[
    "US"
]
Document hash
4fc1dd6a81193fbf4fb880c4d19cdf215dd9e78d33d44a8a8caa6ac4155f6ced
Script hashes
[
    "c07e3ee923625fd1670f00b4f06518dbb2948222d76c33ecbacf0d43a937bc7c"
]
Globals
[
    "ques1"
]
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
1
Apex age days
1
Tls age days
42
Tls valid days
89
Requests
18
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 100,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "netflix"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Netflix"
        ],
        "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-14T13:52:11Z

Observed: · Retrieved:

Uuid
24c2119c-451c-4a8d-992f-5e9aa62b6744
Final url
https://satyam-kumar-mishra.github.io/
Status
404
History
[
    {
        "url": "https://satyam-kumar-mishra.github.io/",
        "status": 404
    }
]
DOM structure hash
35bbdd99a249decabdc93f6b809b030db834533d4d78fe69529a214489fae670
Document hash
70d613e3acfba24fd2876fcbacaf639e1e111ef4d54baf70761c47673f37d6a3
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "satyam-kumar-mishra.github.io",
        "type": "A",
        "value": "185.199.110.153"
    },
    {
        "name": "satyam-kumar-mishra.github.io",
        "type": "A",
        "value": "185.199.109.153"
    },
    {
        "name": "satyam-kumar-mishra.github.io",
        "type": "A",
        "value": "185.199.111.153"
    },
    {
        "name": "satyam-kumar-mishra.github.io",
        "type": "A",
        "value": "185.199.108.153"
    },
    {
        "name": "satyam-kumar-mishra.github.io",
        "type": "AAAA",
        "value": "2606:50c0:8001::153"
    },
    {
        "name": "satyam-kumar-mishra.github.io",
        "type": "AAAA",
        "value": "2606:50c0:8002::153"
    },
    {
        "name": "satyam-kumar-mishra.github.io",
        "type": "AAAA",
        "value": "2606:50c0:8000::153"
    },
    {
        "name": "satyam-kumar-mishra.github.io",
        "type": "AAAA",
        "value": "2606:50c0:8003::153"
    }
]
Dnssec valid
false
Ip
185.199.110.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-18T17:20:00Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 49,
    "malicious": 10,
    "suspicious": 1,
    "undetected": 32
}
Vendor labels
{
    "ESET": "suspicious",
    "VIPRE": "malware",
    "Lionic": "phishing",
    "Webroot": "malicious",
    "Emsisoft": "phishing",
    "Fortinet": "phishing",
    "Netcraft": "malicious",
    "Gridinsoft": "phishing",
    "MalwareURL": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
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-13T08:41:43Z
DNS records
[
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "letsencrypt.org"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "digicert.com"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "185.199.109.153"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "185.199.110.153"
    },
    {
        "ttl": 3600,
        "type": "AAAA",
        "value": "2606:50c0:8001::153"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "185.199.111.153"
    },
    {
        "ttl": 3600,
        "type": "A",
        "value": "185.199.108.153"
    },
    {
        "ttl": 3600,
        "type": "AAAA",
        "value": "2606:50c0:8002::153"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "sectigo.com"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "letsencrypt.org"
    },
    {
        "ttl": 3600,
        "type": "AAAA",
        "value": "2606:50c0:8003::153"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "sectigo.com"
    },
    {
        "ttl": 3600,
        "type": "AAAA",
        "value": "2606:50c0:8000::153"
    },
    {
        "ttl": 3600,
        "type": "CAA",
        "value": "digicert.com"
    }
]
Dns at
2026-10-18T17:20:29Z
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 satyam-kumar-mishra.github.io

Is satyam-kumar-mishra.github.io legit?

No. PhishDestroy classifies satyam-kumar-mishra.github.io as a Netflix impersonation page (risk: critical, 100/100); it was first detected on 2026-09-14. VirusTotal: 9/89 engines flag it. Google Safe Browsing flags it. Treat the site as unsafe.

Is satyam-kumar-mishra.github.io safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on satyam-kumar-mishra.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 satyam-kumar-mishra.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 · 7 captures

Primary capture 1 / 7
SourcePrimary capture
Recorded2026-09-14 13:49 UTC
StateStored capture
Position1 / 7
Open capture Wayback Download

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Netflix report ↗
Google Safe Browsing Flagged Social engineering checked Sep 14, 2026
IP Context Fastly 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
Time to First Unavailability 8h
What we count Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedSep 14, 2026
Submitted URLhttp://satyam-kumar-mishra.github.io/CLONE1
Observed page title
Document
Automated brand references
Netflix
TLS Certificate
Issued by YR1 · stored validity ends in 9 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
185.199.110.153
Network ASN
AS54113
Organization
GitHub, Inc
Observed location
San Francisco, 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.110.153rapiddns.io
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

9 / 89 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
Emsisoft
Fortinet
G-Data
Google Safe Browsing
Gridinsoft
Netcraft
Sophos
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of satyam-kumar-mishra.github.io · checked Sep 14, 2026

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

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
Document
Crawler
Site not found · GitHub Pages
satyam-kumar-mishra.github.io
Saved result
Cloaked / Filtered
Stored observation history12

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

  7. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

Recorded activity

3 entries
  1. Google Safe Browsing

    Threat flag recorded

    View source
  2. VirusTotal

    9/89 engine detections

    View source
  3. Added to PhishDestroy

    satyam-kumar-mishra.github.io

    View source

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal 9 det. ChainPatrol URLQuery Google SB Flagged 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 satyam-kumar-mishra.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/satyam-kumar-mishra.github.io"
  title="PhishDestroy threat report for satyam-kumar-mishra.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>