sumansanand.github.io returned HTTP status 404 on 2026-10-01, the date of the recorded HTTP check. A separate source, PhishDestroy, listed the domain in its internal catalogue, and VirusTotal recorded 10 detections across 89 scanners on 2026-09-11.
Recorded Evidence
The HTTP check on 2026-10-01 recorded status 404 for sumansanand.github.io. PhishDestroy's internal listing was recorded as true. VirusTotal recorded 10 detections out of 89 total scanners on 2026-09-11. The domain was first observed on 2026-09-11, the same date as the PageSpeed check, which returned a performance score of 100. The resolved IP address 185.199.109.153 is associated with GitHub, Inc in the US.
Interpretation
The recorded HTTP 404 describes only the response captured on the check date, not the full history or present state of the domain. The PhishDestroy catalogue entry and the VirusTotal detection count are separate source observations, each with its own measurement context, and they should not be merged into a single conclusion. The first-observed and PageSpeed dates coincide, but that shared calendar date does not establish simultaneous measurement or direct comparability between those sources.
Recommended Actions
Preserve the HTTP response record for sumansanand.github.io alongside the PhishDestroy catalogue entry and the VirusTotal detection record, since each documents a distinct observation. Compare the HTTP status record against future checks of the same domain to see whether the recorded response changes. Review the PhishDestroy listing and VirusTotal record separately, as they capture different kinds of source data. Re-check the domain's HTTP response before relying on the recorded status for any decision.
Analisis deteksi dan penghindaran
Diduga terjadi cloaking: judul pada pemindai dan pengunjung berbeda
Belum dipindaiBelum ada perbedaan yang tercatat antara crawler dan browser
Data pengamatan perbandingan crawler versus browser yang telah disimpan untuk host ini, ditambah pemeriksaan sidik jari secara real-time untuk sistem distribusi lalu lintas bergaya Keitaro.
Hostname coverage not recorded·
Diterbitkan oleh YR1
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
185.199.109.153
Network ASN
AS54113
Organization
GitHub, Inc
Observed location
San Francisco, US
Server header
GitHub.com
Reputasi Edge-IP tidak dikaitkan dengan domain ini.
Location describes the IP network.
Sertifikat TLS
Issuer
YR1
Hostname coverage
Hostname coverage not recorded
Collection source
PhishDestroy collector
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeTidak aktifreason: Http No Content70% confidence
Attributionsource: Current Http Probe
Evidence layersAvailability: Root path has no contentContent: Absent At RootDNS: StaleRegistration: Unknown
Latest HTTP observationTidak aktifHttp No Content70%2026-10-13 01:15:45 UTC
RDAP registrationTidak diketahui
Observed timelinecurrent episode first observed: 2026-10-09 01:25:25 UTCfirst terminal observation: 2026-10-01 01:39:06 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
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.
Google PageSpeed Insights — mobile performance audit of sumansanand.github.io· checked Sep 11, 2026
100
Good
Performance
FCP
0.8s
First Contentful Paint
LCP
0.8s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.8s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Domain Status Transition2026-09-11 10:00:15 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-09-11 09:34:40 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 185.199.109.153.
Alur Tanggapan Ancaman Pipeline
Penemuan
Analysis
Monitoring
11 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Ancaman Telah Diterima
sumansanand.github.io telah terdeteksi dan dimasukkan ke dalam antrian untuk analisis menyeluruh
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
Pemeriksaan terakhir yang disimpan menunjukkan bahwa konten yang dilaporkan tidak tersedia; ini tidak menentukan siapa atau apa yang menyebabkan perubahan tersebut.
11/09/2026
How we investigate & report
Public scans, evidence and abuse channels
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.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
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.
3 evidence signal groups linked0 reports recordedKonten tidak tersedia
If credentials were compromised, report immediately. Do not engage with recovery scammers.
Jika Anda memasukkan kredensial akun, informasi pribadi atau pembayaran, atau mengunduh file dari domain ini, segera ambil tindakan. Di bawah ini adalah sumber daya untuk membantu Anda melaporkan insiden tersebut dan melindungi diri Anda sendiri.
Waspadalah terhadap penipu yang mengatasnamakan pemulihan! Penjahat dapat menghubungi korban lagi sambil berpura-pura menjadi penyelidik, pengacara, atau agen pemulihan. Jangan membayar biaya di muka atau membagikan kredensial.Pelajari lebih lanjut tentang penipuan dalam proses pemulihan →
Laporkan kepada Pihak Berwenang di Daerah Anda
Pilih negara Anda untuk mendapatkan kontak resmi kejahatan dunia maya, atau membuat draf pengaduan →.
Direktori 97 negara
Template-based draft · optional AI wording assistance requires separate consent
Draf yang dibantu AI — detail insiden diproses oleh penyedia AI · Tinjau dan kirimkan sendiri
Infrastruktur dan Laporan Terkait
Hubungan yang disimpan dikelompokkan berdasarkan atribut pencocokan tepat. Penyedia atau registrar bersama saja tidak membuktikan kepemilikan bersama.
Tautan langsung Menggunakan pendaftaran yang sama atau perangkat phishing yang identik.
Sinyal pendukung Berbagi infrastruktur atau merek sasaran; bukan bukti adanya satu operator.
Hanya untuk penemuan Terdaftar untuk navigasi; tidak ada atribut yang sama dengan host ini.
Peta infrastruktur · sumansanand.github.io
Setiap jalur merupakan salah satu alasan mengapa sebuah domain terhubung ke host ini. Ukuran node menandai deteksi VirusTotal, sedangkan node bergaris putus-putus menunjukkan bahwa node tersebut sudah offline. Daftar lengkapnya tercantum di bawah ini.
Konten cocok2
Hash favicon yang sama atau judul halaman yang sama dengan host ini.
Laporan-laporan ini diselesaikan dengan IP edge bersama yang sama. Mereka membantu penemuan laporan tetapi tidak menyiratkan kepemilikan bersama atau server asal bersama.
Didaftarkan melalui penyedia layanan pendaftaran yang sama. Sebuah penyedia layanan pendaftaran melayani jutaan pelanggan yang tidak saling terkait, sehingga hal ini sekadar mengelompokkan laporan-laporan tersebut, bukan membuktikan adanya hubungan.
