The domain bavodex.com was included in a PhishDestroy internal listing on 2026-10-14, providing a dated reference from this publisher-specific source. Additionally, the domain was registered on 2026-10-10, which is documented in the available records.
Recorded Evidence
PhishDestroy recorded bavodex.com in its internal listing on 2026-10-14. VirusTotal checked the domain on 2026-10-14, reporting 0 detections from 92 total scanners. The registration date for bavodex.com is 2026-10-10, and the registrar is Dynadot Inc.
Interpretation
The PhishDestroy listing contains a technical entry for bavodex.com, documenting its presence in a publisher-owned catalogue as of the recorded date. VirusTotal provides a measurement of the domain’s status across multiple security scanners, offering a broad technical snapshot. These records together form a basis for comparing future observations from each source.
Recommended Actions
Preserve the PhishDestroy internal listing and VirusTotal scan results for bavodex.com as reference points. Use these records for comparison with any future evidence to monitor changes in the domain’s recorded status.
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.
Values retained by the collector; long values may be shortened during collection.
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-14 18:39:52 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 104.21.27.46.
威胁响应 Pipeline
发现
Analysis
Monitoring
5 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.
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
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.
(US)
