VirusTotal
9 / 89 engine detections
Open reportsimran201864.github.io is a Netflix impersonation page detected by PhishDestroy on 2026-09-14. Risk: critical (80/100). Registrar: GitHub Pages. Status: Content unavailable. Hosting: Fastly, Inc. VirusTotal: 9/89 engines flag it. Do not enter credentials or connect a wallet.
“Netflix Clone”
9 / 89 engine detections
Open reportMalicious
Open reportno community references
Open reportprovider verdict: clean
Open reportNo threat flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
simran201864.github.io is a GitHub Pages site that copied the look of Netflix and was flagged as an impersonation phishing page aimed at Netflix subscribers. PhishDestroy first saw it on 2026-09-14. It went offline on 2026-09-15, and on 2026-10-19 the address still served no content at its root.
The page carried the title "Netflix Clone", a name typical of student coding exercises, while we classified it as impersonation phishing because it reproduced Netflix branding closely enough to be used against real users. Netflix lookalikes usually reach victims through messages about a failed payment, an expired subscription or a locked account. The fake page then asks for the email and password, and often a card number for "billing verification." A stolen login lets the attacker take over or resell the streaming account, and card details are typically used for fraudulent charges.
On 2026-09-14, the day we first saw the site, 9 of 89 VirusTotal engines flagged it. The vendors named include alphaMountain.ai, ESET, Emsisoft, Fortinet, G-Data, Gridinsoft, Netcraft and Sophos. That count is modest, but these are independent engines, several of them phishing-focused, and they reached the same verdict within a day. urlscan.io also rated the page malicious and recognized Netflix as the imitated brand. PhishDestroy lists the domain on its blocklist.
The site sat on a free github.io subdomain, so no domain registration was involved and anyone with a GitHub account could publish it in minutes. Traffic was served from 185.199.110.153 on Fastly, Inc. in the US, the shared delivery network behind GitHub Pages. That setup gives a phishing page a trusted-looking hostname and valid HTTPS at no cost. It also makes takedown fast, which matches the one-day gap between first detection and the site going dark.
If you entered your Netflix login here, change that password immediately, along with any other account that used the same password. Then review the signed-in devices on your Netflix account and sign out of all of them. If you typed in card details, call your bank to block the card and dispute any unfamiliar charges. Treat follow-up emails or texts about your Netflix billing with suspicion, and open the app directly instead of tapping links. Defenders should block the hostname and search mail logs for messages linking to it around 2026-09-14.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a09f9e-64ea-77b5-be44-41795c924f59 |
|---|---|
| Final url | https://simran201864.github.io/netflix/ |
| Status | 200 |
| Redirected | same-domain |
| Redirects | [
{
"to": "https://simran201864.github.io/netflix/",
"from": "https://simran201864.github.io/netflix",
"status": 301
}
] |
| Ip | 2606:50c0:8001::153 |
| Contacted domains | [
"images.unsplash.com"
] |
| Contacted IP addresses | [
"2a04:4e42:400::720",
"2606:50c0:8001::153"
] |
| Asns | [
"54113"
] |
| Countries | [
"US"
] |
| Document hash | d56ae62ed345a28e07d9dacee17fa1a683c4c9c80f12558900388a281f987ed8 |
| 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 | 2 |
| Apex age days | 2 |
| Tls age days | 42 |
| Tls valid days | 89 |
| Requests | 13 |
| 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"
} |
Observed: · Retrieved:
| Uuid | eb9f602c-3a61-4941-913c-09982188a102 |
|---|---|
| Final url | https://simran201864.github.io/ |
| Status | 404 |
| History | [
{
"url": "https://simran201864.github.io/",
"status": 404
}
] |
| DOM structure hash | 35bbdd99a249decabdc93f6b809b030db834533d4d78fe69529a214489fae670 |
| Document hash | 70d613e3acfba24fd2876fcbacaf639e1e111ef4d54baf70761c47673f37d6a3 |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "simran201864.github.io",
"type": "A",
"value": "185.199.110.153"
},
{
"name": "simran201864.github.io",
"type": "A",
"value": "185.199.111.153"
},
{
"name": "simran201864.github.io",
"type": "A",
"value": "185.199.108.153"
},
{
"name": "simran201864.github.io",
"type": "A",
"value": "185.199.109.153"
},
{
"name": "simran201864.github.io",
"type": "AAAA",
"value": "2606:50c0:8002::153"
},
{
"name": "simran201864.github.io",
"type": "AAAA",
"value": "2606:50c0:8001::153"
},
{
"name": "simran201864.github.io",
"type": "AAAA",
"value": "2606:50c0:8000::153"
},
{
"name": "simran201864.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"
]
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 48,
"malicious": 12,
"suspicious": 0,
"undetected": 32
} |
|---|---|
| Vendor labels | {
"ESET": "phishing",
"VIPRE": "malware",
"Lionic": "phishing",
"Sophos": "phishing",
"Webroot": "malicious",
"Emsisoft": "phishing",
"Fortinet": "phishing",
"Netcraft": "malicious",
"Gridinsoft": "phishing",
"MalwareURL": "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-13T09:11:10Z |
| DNS records | [
{
"ttl": 3600,
"type": "A",
"value": "185.199.110.153"
},
{
"ttl": 3600,
"type": "CAA",
"value": "sectigo.com"
},
{
"ttl": 3600,
"type": "CAA",
"value": "letsencrypt.org"
},
{
"ttl": 3600,
"type": "CAA",
"value": "digicert.com"
},
{
"ttl": 3600,
"type": "AAAA",
"value": "2606:50c0:8001::153"
},
{
"ttl": 3600,
"type": "A",
"value": "185.199.109.153"
},
{
"ttl": 3600,
"type": "A",
"value": "185.199.111.153"
},
{
"ttl": 3600,
"type": "CAA",
"value": "sectigo.com"
},
{
"ttl": 3600,
"type": "CAA",
"value": "letsencrypt.org"
},
{
"ttl": 3600,
"type": "AAAA",
"value": "2606:50c0:8000::153"
},
{
"ttl": 3600,
"type": "CAA",
"value": "digicert.com"
},
{
"ttl": 3600,
"type": "AAAA",
"value": "2606:50c0:8003::153"
},
{
"ttl": 3600,
"type": "AAAA",
"value": "2606:50c0:8002::153"
},
{
"ttl": 3600,
"type": "A",
"value": "185.199.108.153"
}
] |
| Dns at | 2026-10-19T05:47:40Z |
| 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"
} |
No. PhishDestroy classifies simran201864.github.io as a Netflix impersonation page (risk: critical, 80/100); it was first detected on 2026-09-14. VirusTotal: 9/89 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on simran201864.github.io. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
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.
Edge-IP reputation is not attributed to this domain.
ns-692.awsdns-22.netns-1622.awsdns-10.co.ukdns1.p05.nsone.netdns2.p05.nsone.netdns3.p05.nsone.netLocation describes the IP network.
f2f9a159ce50a0a168b3eaeaf2fced5addd49ba38e2bf63248f057a139fc7856*.github.com*.github.io*.githubusercontent.comgithub.comgithub.iogithubusercontent.comSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of simran201864.github.io · checked Sep 14, 2026
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
http_other: raw=http_404; http=404; via=http_proxy; server=GitHub.com
simran201864.github.io
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→inactive
http_no_content
Unknown→inactive
http_no_content
Unknown→inactive
http_no_content
Unknown→inactive
http_no_content
Unknown→inactive
http_no_content
Unknown→inactive
http_no_content
Unknown→inactive
http_no_content
Unknown→inactive
hosting_placeholder · placeholder_page
Unknown→inactive
hosting_placeholder · placeholder_page
Unknown→inactive
hosting_placeholder · placeholder_page
Reachable→Unavailable
No threat flag
View source9/89 engine detections
View sourcesimran201864.github.io
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
simran201864.github.io)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.