salehaeman[.]github[.]io

salehaeman.github.io is a tenant hostname on Fastly, not a separately registered domain. PhishDestroy first recorded this hostname on Jul 10, 2026. Stored content metadata identifies Amazon as the apparent target. The assembled evidence scores 97/100 (critical).

Two independent sources are positive: Cloudflare Radar and URLScan. Cloudflare Radar classified the hostname as malicious and placed it in the phishing category; its verdict timestamp was not retained. URLScan returned a malicious verdict with score 100 on Jul 11, 2026 at 08:12 UTC. The evidence is not unanimous. The external blocklist snapshot contained no matches on Aug 7, 2026 at 14:20 UTC. Google Safe Browsing returned no flag on Jul 10, 2026 at 12:35 UTC. VirusTotal was checked, but a reliable engine total is unavailable on Jul 18, 2026 at 20:45 UTC.

HTTP 404 was recorded on Aug 7, 2026 at 01:06 UTC; content was unavailable. Fastly is the hosting platform for this tenant, not its registrar. At collection time, the hostname resolved to 185.199.109.153 on AS54113 (FASTLY - Fastly, Inc., US). The associated network metadata labels the endpoint as AS54113 Fastly, Inc. in San Francisco, US. This is shared platform infrastructure; the IP and ASN are hosting context, not attribution to unrelated tenants. The stored server header is GitHub.com. Captured page title: “Amazon”. DOM analysis completed on Jul 10, 2026 at 14:20 UTC; stored DOM score 0/100. The evidence archive retains 2 visual captures from PhishDestroy and URLScan. IoC extraction completed on Jul 29, 2026 at 02:48 UTC; stored 0 format-validated wallet addresses and 0 Telegram indicators. The platform TLS certificate was issued by Let's Encrypt / YR2 with validity through Sep 2, 2026; checked Jul 10, 2026 at 13:00 UTC.

The 0/100 DOM score means that the DOM pass stored no scored indicators; it does not negate the independent source findings. Taken together, the page content and independent findings support classifying this hostname as Amazon impersonation and phishing. The stored record does not establish the post-click interaction, and it does not claim a confirmed wallet-draining transaction or credential submission.