liveupdt[.]com

PhishDestroy first observed liveupdt.com on Jan 5, 2026. The captured page title is “liveupdt.com is almost here!”. Current evidence score: 100/100 (critical).

Positive findings are stored from 4 sources: VirusTotal, CryptoFirewall, DNS security resolvers, and Cloudflare Radar. VirusTotal recorded 13 detections among 91 engines: ADMINUSLabs, alphaMountain.ai, BitDefender, Certego, Chong Lua Dao, Forcepoint ThreatSeeker, G-Data, Gridinsoft, Lionic, Lumu, Viettel Threat Intelligence, VIPRE, Webroot on Jul 27, 2026 at 02:32 UTC. CryptoFirewall listed the hostname in the separate external-blocklist snapshot on Aug 8, 2026 at 06:20 UTC. DNS security checks returned 5 blocking results across 14 tested policies: Cloudflare Family, Cloudflare Security, Control D Adblock, Control D Family, Control D Malware; no observation timestamp was retained. Cloudflare Radar classified the hostname as malicious and assigned the categories malware, command and control & botnet, and security threats; its verdict timestamp was not retained. Non-positive and contextual checks: Gridinsoft assigned a trust score of 1/100 (Suspicious); no observation timestamp was retained. AlienVault OTX listed 8 community pulse references (not vendor detections) on Mar 1, 2026 at 12:55 UTC. Google Safe Browsing returned no flag on Mar 2, 2026 at 20:25 UTC. URLScan completed without a malicious verdict (score 0) on Jul 29, 2026 at 02:55 UTC.

HTTP 301 was recorded on Aug 7, 2026 at 22:16 UTC. Registration records for the domain list GoDaddy.com, LLC as the registrar and Oct 24, 2019 as the creation date. At collection time, the hostname resolved to 67.205.42.190 on AS26347 (DREAMHOST-AS, US). The recorded endpoint location is Leesburg, US. The stored server header is Apache. DOM analysis on Mar 11, 2026 at 09:03 UTC returned 98/100. The evidence archive retains 2 visual captures from PhishDestroy and URLScan. TLS metadata lists R12 as the certificate issuer with validity through Jun 3, 2026; checked Mar 12, 2026 at 07:31 UTC.

The content indicators and 4 positive source findings support the current phishing classification. The stored fields do not identify an impersonated brand or victim interaction.