On 2026-10-09, zhzlcy.com was observed by VirusTotal with 16 detections out of 92 scanners, indicating its presence in security monitoring on that date. The domain was also included in the PhishDestroy internal listing, reflecting additional tracking by monitoring sources.
Recorded Evidence
VirusTotal checked zhzlcy.com on 2026-10-09, reporting 16 detections from 92 total scanners. OTX referenced the domain in five pulses as of 2026-10-09. A urlscan report was available on 2026-10-09, and PhishDestroy included zhzlcy.com in its internal listing. The domain was registered through Gname.com Pte. Ltd. on 2020-08-17.
Interpretation
The records from VirusTotal, OTX, and PhishDestroy indicate that zhzlcy.com was noted by several security platforms on the same date. The availability of a urlscan report and its inclusion in the internal listing show that the domain was of interest to multiple monitoring systems at that time.
Recommended Actions
Review the urlscan report and VirusTotal findings for zhzlcy.com to understand the recorded detections. Preserve OTX pulse records and the PhishDestroy internal listing for ongoing comparison. Use these dated records to inform any future analysis of the domain.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not yet scanned
Last cloaking scan
Scanner note:timeout: raw=timeout; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='zhzlcy.com', port=80): Max retries exceeded with url: / (Caused by ConnectTimeoutError(<SO
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-13 10:45:34 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-10-13 02:19:40 UTClast content: 2026-10-09 11:03:00 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.
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-09 03:07:27 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 201.5.67.20.
Threat Response Pipeline
Discovery
Analysis
Monitoring
10 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.
4 evidence signal groups linked0 reports recordedUnverified
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · zhzlcy.com
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Same registrar: Gname6
Registered through the same registrar. A registrar serves millions of unrelated customers, so this groups reports rather than proving a link.
(SG)
