dpd[.]ppzke[.]cyou

dpd.ppzke.cyou is a subdomain of ppzke.cyou. PhishDestroy first observed the hostname on Aug 31, 2026. The hostname explicitly references Dpd; stored content metadata identifies the same apparent target. The captured page title is “DPD Local”. Current evidence score: 100/100 (critical).

Positive findings are stored from 7 sources: VirusTotal, Phishunt, Google Safe Browsing, Spamhaus DBL, Cloudflare Radar, URLQuery, and URLScan. VirusTotal recorded 12 detections among 91 engines: Cluster25, CRDF, ESET, Emsisoft, Fortinet, G-Data, Google Safe Browsing, Gridinsoft, LevelBlue, Netcraft, SOCRadar, Sophos on Aug 31, 2026 at 08:00 UTC. Phishunt listed the hostname in the separate external-blocklist snapshot on Aug 31, 2026 at 10:20 UTC. Google Safe Browsing flagged the domain: Social Engineering on Aug 31, 2026 at 10:50 UTC. Spamhaus DBL: DBL_SPAM on Aug 31, 2026 at 10:30 UTC. Cloudflare Radar classified the hostname as malicious and placed it in the phishing category; its verdict timestamp was not retained. URLQuery recorded 2 detections; no observation timestamp was retained. URLScan returned a malicious verdict with score 100; scan metadata linked the capture to Dpd and assigned phishing as its category on Aug 31, 2026 at 11:09 UTC.

The collector marked the hostname reachable on Aug 31, 2026 at 07:55 UTC, but did not retain the HTTP response code. Registration records for the registrable domain ppzke.cyou list Dominet (HK) Limited as the registrar and Aug 22, 2026 as the creation date. Registration preceded first observation by 9 days. At collection time, the hostname resolved to 188.114.96.3 on AS13335 (Cloudflare, Inc.). The IP and ASN identify shared Cloudflare edge infrastructure; the origin server is not established by this address. The evidence archive retains 2 visual captures from PhishDestroy and URLScan. TLS metadata lists Google Trust Services as the certificate issuer with validity through Nov 27, 2026; checked Aug 31, 2026 at 10:02 UTC.

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