SUSPICIOUS — FLAGGED
m-saitharun[.]github[.]io
0 of 91 security engines flagged the domain; the latest stored check returned HTTP 404.
- VirusTotal
- 0/91
- Blocklists
- No stored match
- उपलब्धता
- सामग्री अनुपलब्ध · HTTP 404
Do not enter credentials, seed phrases, payment details, or personal information on this domain.
Jump to section
m-saitharun.github.io — सामग्री अनुपलब्ध (HTTP 404). साक्ष्य सारांश: VirusTotal 0/91; PhishDestroy score 68/100. रजिस्ट्रार: GitHub.
मूल फॉरेंसिक रिकॉर्ड सुरक्षित रखने के लिए नीचे का विस्तृत PhishDestroy AI विश्लेषण अंग्रेज़ी में रखा गया है।
Evidence Digest
m-saitharun.github.io is classified flagged with an evidence score of 68/100. 0 of 91 security engines flagged the domain. Registration metadata recorded via GitHub, Inc., hosted on 185.199.110.153 (Fastly, Inc., US). The latest stored check on 9 Aug 2026 returned HTTP 404 and includes a capture.
Stored generated summary (templated)cerebras · 15/07/2026
Retained for the record. This text repeats stored detection facts and is not presented as authored analysis.
Analysis of the domain m-saitharun.github.io indicates that it is hosted on the GitHub Pages service, as evidenced by its DNS resolution to the IP address 185.199.110.153, which is owned by GitHub, Inc. The domain was registered through GitHub, Inc., and its authoritative name server information is currently unavailable (NS_NOT_FOUND). The domain remains active as of the report date, July 15, 2026, and no public takedown or suspension has been observed. VirusTotal records show that the domain was submitted to 91 scanning engines, none of which returned a detection at the time of analysis; this absence of detections does not constitute assurance of safety. No additional infrastructure details, such as ASN or geographic location, are disclosed beyond the hosting IP. The publicly available intelligence does not include a page title, targeted brand, or observed phishing kit, leaving the exact malicious intent of the site undefined. Given the classification as a generic phishing infrastructure under investigation, defenders should consider adding the domain to block lists, monitoring DNS queries for repeated resolution, and employing sinkholing where feasible. Continuous re‑assessment is advised, as the threat actor may later deploy credential‑harvesting pages or redirect traffic to other malicious resources.
डेटा कवरेज12 recorded checks
धमकी प्रतिक्रिया पाइपलाइन
सार्वजनिक ब्लॉकलिस्ट स्थिति
वायरसटोटल विश्लेषण
साक्ष्य और बाहरी रिपोर्टेंIndependent lookups and source reports
Victim safety and official reportingImmediate actions and verified reporting channels
यदि आपने खाता क्रेडेंशियल, व्यक्तिगत या भुगतान जानकारी दर्ज की है, या इस डोमेन से कोई फ़ाइल डाउनलोड की है, तो तुरंत कार्रवाई करें। घटना की रिपोर्ट करने और अपनी सुरक्षा करने में आपकी सहायता के लिए नीचे संसाधन दिए गए हैं।
अपने स्थानीय अधिकारियों को रिपोर्ट करें
आधिकारिक साइबर अपराध संपर्क, या एक शिकायत ड्राफ्ट बनाएं → प्राप्त करने के लिए अपना देश चुनें।