The domain chenrenxu.com was observed in a security context with a VirusTotal detection record dated 2026-10-11. The domain is also listed internally in the PhishDestroy catalogue, providing an additional reference point for analysis.
Recorded Evidence
VirusTotal checked chenrenxu.com on 2026-10-11 and recorded 5 detections out of 92 scanners. OTX observed the domain on 2026-10-12, documenting its inclusion in 34 OTX pulses. The domain was registered with DNSPod, Inc. on 2026-05-12 and first observed in records on 2026-10-11. PhishDestroy maintains an internal listing for chenrenxu.com as of the latest evidence.
Interpretation
VirusTotal provides a quantitative measurement of detections, reflecting how chenrenxu.com was evaluated by multiple security scanners. The PhishDestroy internal listing documents its catalogue inclusion, which serves as a reference for tracking. OTX records offer insight into the domain’s presence in external threat intelligence pulses. These observations collectively cover registration, detection, and catalogue inclusion, allowing for a broad review of the domain's recorded profile.
Recommended Actions
For chenrenxu.com, it is advisable to retain the VirusTotal detection record and the PhishDestroy internal listing for ongoing comparison. Preserve the OTX pulse record for reference in future threat intelligence reviews. These source records should be monitored for updates to maintain an accurate assessment of the domain’s security context.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observation内容在线Ordinary HTTP content served90%2026-10-13 01:35:44 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-13 01:35:44 UTClast content: 2026-10-13 01:35:44 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-12 11:19:29 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 101.34.218.216.
威胁响应 Pipeline
发现
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.
