ddsffhtttxfinrru[.]weebly[.]com

ddsffhtttxfinrru.weebly.com is a subdomain of weebly.com. PhishDestroy first observed the hostname on Jun 29, 2026. Stored content metadata identifies Google as the apparent target. The captured page title is “Home”. Current evidence score: 89/100 (critical).

Positive findings are stored from 4 sources: VirusTotal, Google Safe Browsing, Cloudflare Radar, and URLScan. VirusTotal recorded 13 detections among 91 engines: alphaMountain.ai, BitDefender, CyRadar, ESET, Emsisoft, Fortinet, G-Data, Google Safebrowsing, Gridinsoft, Kaspersky, Lionic, OpenPhish, Sophos on Jul 18, 2026 at 16:45 UTC. Google Safe Browsing flagged the domain: Social Engineering on Jun 29, 2026 at 13:35 UTC. Cloudflare Radar classified the hostname as malicious and placed it in the phishing category; its verdict timestamp was not retained. URLScan returned a malicious verdict with score 100; scan metadata linked the capture to Xfinity and assigned phishing as its category on Jul 29, 2026 at 03:01 UTC. Non-positive and contextual checks: The external blocklist snapshot contained no matches on Aug 7, 2026 at 18:20 UTC.

HTTP 404 was recorded on Aug 7, 2026 at 01:01 UTC; content was unavailable. Registration records for the registrable domain weebly.com list MarkMonitor, Inc. as the registrar and Mar 28, 2006 as the creation date. At collection time, the hostname resolved to 74.115.51.8 on AS27647 (WEEBLY - Weebly, Inc., US). The IP and ASN identify shared Cloudflare edge infrastructure; the origin server is not established by this address. DOM analysis on Jun 29, 2026 at 14:20 UTC returned 0/100; the source detections above were recorded separately. The evidence archive retains 2 visual captures from PhishDestroy and URLScan. TLS metadata lists Let's Encrypt / YE1 as the certificate issuer with validity through Sep 8, 2026; checked Jun 29, 2026 at 16:00 UTC.

The content indicators and 4 positive source findings support the current Google impersonation and phishing classification. The target field identifies Google, but the record does not establish whether the page requested credentials, a seed phrase, or a wallet connection.