anandhospital.co.in was observed with a PhishFeed blocklist entry on 2026-10-13, marking a recorded external indicator for the domain. Additionally, a PageSpeed performance score of 62 was measured on the same date, providing a technical context for its infrastructure.
Recorded Evidence
On 2026-10-13, the domain was listed on the PhishFeed blocklist. VirusTotal checked anandhospital.co.in on 2026-10-12, recording 9 detections from 92 scanners. The domain also appeared in a PhishDestroy internal listing on 2026-10-13. A PageSpeed check was performed on 2026-10-13, resulting in a performance score of 62.
Interpretation
The VirusTotal record contains a scan-based measurement, documenting how many security vendors detected issues with anandhospital.co.in. The PhishFeed blocklist entry provides an external listing, showing the domain's presence in a blocklist on the recorded date. These sources offer distinct types of evidence, with VirusTotal aggregating scanner results and PhishFeed noting blocklist status. The evidence spans two close dates, which allows for comparison of recorded security intelligence.
Recommended Actions
For anandhospital.co.in, preserve the VirusTotal and PhishFeed records for ongoing security reviews. Compare the PhishDestroy internal listing and PageSpeed performance results with any future data collected. Use these source records to track changes in blocklist status and detection counts over time.
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.
Google PageSpeed Insights — mobile performance audit of anandhospital.co.in· checked Oct 13, 2026
62
Needs Work
Performance
FCP
3.9s
First Contentful Paint
LCP
7.44s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
32ms
Total Blocking Time
SI
6.61s
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.
Threat First Observed2026-10-12 23:28:12 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 192.185.129.218.
威胁响应 Pipeline
发现
Analysis
Monitoring
6 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
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.
