srinivasgubba-2006.github.io is a free GitHub Pages site that PhishDestroy classified as an impersonation phishing page posing as Amazon and aimed at Amazon account holders. We first flagged it on 2026-09-06. It has been offline since 2026-09-11, and on our last check on 2026-10-19 the root returned no content. The page now shows the title "Site not found · GitHub Pages", which is GitHub's default for a removed or empty project, while our classification reflects the Amazon impersonation found while it was live.
How the scam works
Amazon impersonation pages copy the look of the real sign-in or account screens and are spread through links in emails or texts about orders, deliveries, refunds or account locks. A victim who types an email and password hands them straight to the operator, who can then take over the account, place orders with saved cards, or reuse the password elsewhere. Many such pages go on to ask for card numbers or one-time codes under the pretext of verifying the account. Using a github.io address lets the lure borrow the credibility of a well-known platform instead of a freshly registered lookalike domain.
Evidence
On 2026-09-11, the day it went offline, 14 of 89 VirusTotal engines flagged the site, including BitDefender, ESET, Emsisoft, G-Data, Forcepoint ThreatSeeker, alphaMountain.ai, CyRadar and Gridinsoft. That is a meaningful spread of independent vendors for a short-lived page. urlscan.io returned a malicious verdict and detected Amazon branding on the page, which directly supports the impersonation classification. The domain is listed on the PhishDestroy blocklist.
Infrastructure
There was no domain to register. The operator simply created a GitHub Pages project, which is why GitHub, Inc. appears as the registrar and the site resolves to Fastly's US network that serves all GitHub Pages content. Such throwaway subdomains cost nothing and can be spun up and abandoned quickly. This one lasted about five days between our first detection and going dark.
What to do
If you entered your Amazon email and password on this page, change your Amazon password immediately, enable two-step verification, and change the password on any other account that shared it. Review your Amazon order history, saved addresses and payment methods for anything you did not add. If you typed in card details, contact your bank to block the card and dispute unfamiliar charges. Defenders should block the hostname, search mail logs for messages linking to it, and treat other github.io pages carrying Amazon branding as suspect.
颁发者 Let's Encrypt· stored validity ends in 53 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
185.199.108.153
Network ASN
AS54113
Organization
Fastly, Inc.
Observed location
San Francisco, US
Server header
GitHub.com
Edge-IP 声誉不属于此域。
Location describes the IP network.
TLS 证书
Issuer
Let's Encrypt
Valid from
2026-08-02 23:38:02
Valid until
2026-10-31 23:38:01
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-09-06 16:02:03 UTC
Collection source
PhishDestroy collector
Certificate fingerprint71f1077db377fd7b8d68380da66fa68238a303b2911bcb770b3b2a426693cf84Certificate names · 3 SANs
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.
Fastly is a cloud computing services provider. Fastly's cloud platform provides a content delivery network, Internet security services, load balancing, and video & streaming services.
Template-based draft · optional AI wording assistance requires separate consent
AI辅助草稿——事件详细信息由AI提供商处理 · 自行审核并提交
After a phishing incident
针对受害者的建议与指导
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.
更改所有密码 — 电子邮件、Exchange 账户，以及任何使用同一密码的账户
启用双因素认证 使用身份验证器应用（而非短信）。禁用基于短信的恢复功能
冻结卡片 如果您在钓鱼网站上输入了银行信息
我应该为报告收集哪些信息？
联邦调查局（FBI）指南
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.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
当地警方 — 即使无法立即采取行动，也能留下正式记录
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?
虚假网站 — 与正规网站完全一致的克隆网站，仅域名略有改动
猪的屠宰 — 通过Telegram/WhatsApp/交友软件花数周时间建立信任，随后钱被骗走
退款诈骗 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
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.
(US)
