VirusTotal
12 / 89
“Site not found · GitHub Pages”
On 2026-10-01, amitvaland1492.github.io was observed returning an HTTP 404 status, indicating that the requested page was not found at that time. The domain also achieved a PageSpeed performance score of 100 during a separate check, suggesting optimal technical performance on 2026-09-06.
PhishDestroy recorded an internal listing for the domain, and its first observation was made on 2026-09-06. VirusTotal reported 12 detections out of 89 scanners when it checked the domain on 2026-09-11. The SSL certificate for amitvaland1492.github.io, issued by Let's Encrypt / YR1, was scanned on 2026-09-06.
The evidence from PhishDestroy, VirusTotal, and SSL scans was collected on different dates, which means each source reflects the domain's status at distinct points in time. This separation in observation dates allows for comparison between technical performance, security findings, and listing status without conflating their results.
To review amitvaland1492.github.io, retain all dated evidence for future reference and comparison. When monitoring new activity, compare subsequent observations to those recorded on 2026-09-06, 2026-09-11, and 2026-10-01. Avoid submitting sensitive information to the domain while its status is under review.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
GitHub.comScanner note: http_other: raw=http_404; http=404; via=http_proxy; server=GitHub.com
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
71f1077db377fd7b8d68380da66fa68238a303b2911bcb770b3b2a426693cf84github.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 amitvaland1492.github.io · checked Sep 6, 2026
185.199.108.153. 15 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
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
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