fjcbdae[.]pilot45[.]com

fjcbdae.pilot45.com is a subdomain of pilot45.com. PhishDestroy first recorded this hostname on Nov 16, 2025. The assembled evidence scores 97/100 (critical).

Two independent sources are positive: VirusTotal and Cloudflare Radar. VirusTotal recorded 14 detections among 95 engines: BitDefender, CyRadar, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data, Kaspersky, Lionic, Phishing Database, Seclookup, SOCRadar, Sophos, VIPRE, Webroot on Feb 23, 2026 at 06:45 UTC. Cloudflare Radar classified the hostname as malicious and assigned the categories phishing and security threats; its verdict timestamp was not retained. The evidence is not unanimous. The external blocklist snapshot contained no matches on Aug 7, 2026 at 14:20 UTC. URLQuery recorded no positive detection. Google Safe Browsing returned no flag on Mar 3, 2026 at 04:14 UTC. URLScan completed without a malicious verdict (score 0) on Mar 1, 2026 at 01:13 UTC.

HTTP 502 was recorded on Aug 7, 2026 at 01:15 UTC; content was unavailable. Registration records for the registrable domain pilot45.com list Gname.com Pte. Ltd. as the registrar and Dec 23, 2024 as the creation date. At collection time, the hostname resolved to 104.21.2.72 on AS13335 (CLOUDFLARENET, US). The associated network metadata labels the endpoint as AS13335 Cloudflare, Inc. in San Francisco, US. The stored server header is cloudflare. Captured page title: “网站筹建中”. DOM analysis completed on Jul 29, 2026 at 04:16 UTC; stored DOM score 0/100. The evidence archive retains 2 visual captures from PhishDestroy and URLScan. IoC extraction completed on Aug 2, 2026 at 04:25 UTC; stored 0 format-validated wallet addresses and 0 Telegram indicators.

No target brand has been confirmed from stored page content; hostname wording alone is not treated as brand evidence. The 0/100 DOM score means that the DOM pass stored no scored indicators; it does not negate the independent source findings. Taken together, the page content and independent findings support classifying this hostname as phishing. The stored record does not establish the post-click interaction, and it does not claim a confirmed wallet-draining transaction or credential submission.