VirusTotal
10 / 89
ReportInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“Site not found · GitHub Pages”
Assessment based on the stored source evidence below. Review sources →
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
10 / 89
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
malicious
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
no community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: clean
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
stored report
View stored capture ↗ ReportA preserved page image documents what the collector received; a capture is not a safety verdict.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
0 external matches
DetailsA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Stored narrative · generated . Provider checks below retain their own observation dates.
On 2026-10-01, jatinyadav378113-alt.github.io returned HTTP status 404 in a recorded check, and the domain was first observed on 2026-09-07. A separate PageSpeed check on 2026-09-07 recorded a performance score of 100, while the PhishDestroy internal listing marks the domain as listed.
The HTTP check on 2026-10-01 recorded status 404 for jatinyadav378113-alt.github.io. The domain was first observed on 2026-09-07, and a PageSpeed check on the same date recorded a performance score of 100. The SSL certificate was scanned on 2026-09-07 and its issuer was recorded as Let's Encrypt / YR1. VirusTotal on 2026-09-11 recorded 10 detections across 89 scanners. The domain resolves to IP address 185.199.108.153, associated with AS54113 Fastly, Inc. in the US.
The HTTP, PageSpeed and SSL observations all fall on 2026-09-07 or 2026-10-01, while the VirusTotal scan is dated 2026-09-11, so the records span several days and cannot be treated as a single snapshot. The PhishDestroy internal listing and the VirusTotal detections are separate named sources with their own collection dates, which limits direct comparison between them. The recorded HTTP status reflects only the response captured on that date, and the PageSpeed score reflects only the performance measurement taken on its own date.
Retain the dated records for jatinyadav378113-alt.github.io, including the HTTP, PageSpeed, SSL and VirusTotal observations, so later checks can be compared against the same fields. When reviewing the domain, compare each new observation with the corresponding dated source rather than mixing fields from different dates. Avoid submitting passwords, payment details or other sensitive information while the review is in progress.
What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.
These checks have no retained result. This does not mean they passed or that a scan is running.
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 jatinyadav378113-alt.github.io · checked Sep 7, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
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
185.199.108.153.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
inactive→Unknown
stale_current_evidence
Unknown→inactive
http_no_content
inactive→Unknown
stale_current_evidence
Unknown→inactive
http_no_content
inactive→Unknown
stale_current_evidence
Unknown→inactive
http_no_content
inactive→Unknown
stale_current_evidence
Unknown→inactive
hosting_placeholder · placeholder_page
inactive→Unknown
stale_current_evidence
Unknown→inactive
hosting_placeholder · placeholder_page
Unknown
stale_current_evidence
Unknown→inactive
hosting_placeholder · placeholder_page
Reachable→Unavailable
9→10
8→9
1→8
0→1
Reachable
16 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