com-secure[.]us

PhishDestroy first recorded com-secure.us on Dec 4, 2025. This English evidence brief is rebuilt from the current structured observations stored for the report. The current evidence score, computed from those stored observations, is 77/100.

The latest stored availability state is “Last known active” on Aug 2, 2026 at 00:13 UTC. No conclusive HTTP response is stored, so current availability remains unverified.

VirusTotal returned 4 detections from 91 scanners in the stored check on Aug 1, 2026 at 04:20 UTC. The independent blocklist snapshot recorded 0 matches across 10 configured external sources on Aug 2, 2026 at 00:20 UTC. PhishDestroy's own listing is excluded from that count. A zero-match snapshot is not a safety verdict.

Other stored evidence. Google Safe Browsing stored no positive flag on Jun 27, 2026 at 03:38 UTC. This time-bound result is not evidence of safety. AlienVault OTX stored 0 pulse references on Mar 1, 2026 at 16:54 UTC. OTX pulses are community-intelligence references, not vendor verdicts. The Spamhaus DBL snapshot stored no positive result on Jul 14, 2026 at 16:36 UTC. That result is not evidence of safety. A URLScan capture is stored from Feb 27, 2026 at 02:21 UTC.

Stored context lists registrar Key-Systems GmbH, IP address 172.67.214.107, registration date Nov 30, 2025, apparent target X.com. Except for the registration date, these fields do not share a source timestamp in this report and may change.

Treat these as stored, time-bound observations rather than a live safety guarantee. Source verdicts and reachability can change, and zero or missing vendor matches never prove that a domain is safe. Avoid interacting with the domain while uncertainty remains, and use the appeal process if this report is inaccurate.