VirusTotal
12 / 89 engine detections
보고서 열기“Amazon Project”
aishwarya-rathore.github.io — 콘텐츠를 사용할 수 없음 (HTTP 404). 브랜드 사칭: Amazon; 사기 유형: Impersonation. 증거 요약: VirusTotal 12/89 (alphaMountain.ai, BitDefender, ESET, Emsisoft, Forcepoint ThreatSeeker); URLScan malicious verdict; PhishDestroy score 86/100. 등록기관: MarkMonitor.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
12 / 89 engine detections
보고서 열기악성
보고서 열기no community references
보고서 열기provider verdict: clean
보고서 열기No threat flag
보고서 열기Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
AI-assisted evidence review
aishwarya-rathore.github.io is a phishing page that impersonates Amazon and is aimed at people who shop or sell on the platform. PhishDestroy first flagged it on 2026-09-11. It went offline that same day. When checked again on 2026-10-19, the address still served no content at its root.
The page carried the title "Amazon Project" and copied Amazon's look so that visitors would treat it as a genuine Amazon sign-in or account page. Pages like this usually ask for an Amazon email and password, and sometimes for card details or a one-time code. Whatever is typed goes to the operator, who can then take over the account, place orders with saved payment methods or reuse the password on other services. The title reads like a hobby or demo project, but urlscan.io and several security vendors judged the page itself to be malicious Amazon impersonation, and we classified it the same way.
On 2026-09-16, 12 of 89 VirusTotal engines flagged the site. They included BitDefender, ESET, Emsisoft, G-Data, Forcepoint ThreatSeeker, alphaMountain.ai, Gridinsoft and Lionic. That is a minority of engines, but the vendors are independent of each other and agree on the verdict. urlscan.io rated the page malicious and recognised Amazon branding on it. The domain is listed on the PhishDestroy blocklist.
The page sat on a user subdomain of GitHub Pages. The 2013-03-08 registration date and the MarkMonitor, Inc. registrar belong to github.io itself, not to whoever built this page. Traffic was served from Fastly's network (AS54113) in the US, the content delivery network GitHub uses for Pages. Free developer hosting like this lets anyone put up a branded lookalike in minutes, and the page inherits the trusted github.io name and a valid certificate.
If you entered your Amazon password on this page, change it right away on Amazon's real site or app, and change it anywhere else you used the same password. Turn on two-step verification and sign out of all other devices. Check your recent orders, saved addresses and payment methods for anything you don't recognise. If you entered card details, ask your bank to block the card and dispute any unfamiliar charges. Defenders should block the hostname, search mail and proxy logs for visits since 2026-09-11, and report any similar lookalike pages to GitHub and to Amazon's abuse team.
urlscan.io scan and screenshot: https://urlscan.io/result/01a08dfd-9151-7228-b1c0-4c5fbf6ddcf7/
VirusTotal report: https://www.virustotal.com/gui/domain/aishwarya-rathore.github.io
Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=aishwarya-rathore.github.io
Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/
Site owner? Request a review: https://phishdestroy.io/appeals/
Edge-IP 평판은 이 도메인에 귀속되지 않습니다.
Location describes the IP network.
Saved 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 aishwarya-rathore.github.io · checked Sep 11, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
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
aishwarya-rathore.github.io
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
알 수 없음→inactive
http_no_content
알 수 없음→inactive
http_no_content
알 수 없음→inactive
http_no_content
알 수 없음→inactive
http_no_content
알 수 없음→inactive
http_no_content
알 수 없음→inactive
hosting_placeholder · placeholder_page
알 수 없음→inactive
hosting_placeholder · placeholder_page
알 수 없음→inactive
hosting_placeholder · placeholder_page
11→12
8→11
접속 가능→이용 불가
이용 불가
No threat flag
View source12/89 engine detections
View sourceaishwarya-rathore.github.io
View sourceListed domains receive at least one abuse report; this entry has no retained notification history.
계정 자격 증명, 개인 정보 또는 결제 정보를 입력했거나 이 도메인에서 파일을 다운로드한 경우 즉시 조치를 취하세요. 다음은 사건을 신고하고 자신을 보호하는 데 도움이 되는 리소스입니다.
공식 사이버 범죄 연락처 또는 불만사항 초안 작성 →를 받으려면 국가를 선택하세요.
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 ↗
aishwarya-rathore.github.io)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
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
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.