inflorescenceflowers[.]com

PhishDestroy first observed inflorescenceflowers.com on Sep 2, 2026. Current evidence score: 95/100 (critical).

Positive findings are stored from 3 sources: VirusTotal, Cloudflare Radar, and URLQuery. VirusTotal recorded 17 detections among 91 engines: alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, Kaspersky, Lionic, Seclookup, SOCRadar, Sophos, VIPRE, Webroot on Sep 2, 2026 at 23:56 UTC. Cloudflare Radar classified the hostname as malicious and placed it in the malware category; its verdict timestamp was not retained. URLQuery recorded 2 detections; no observation timestamp was retained. Non-positive and contextual checks: On Sep 2, 2026 at 23:57 UTC, AlienVault OTX listed 5 community pulse references (not vendor detections); Google Safe Browsing returned no flag. The separate external-blocklist snapshot contained no matches on Sep 2, 2026 at 22:20 UTC. URLScan completed without a malicious verdict (score 0) on Sep 2, 2026 at 23:08 UTC.

The collector marked the hostname reachable on Sep 2, 2026 at 20:33 UTC, but did not retain the HTTP response code. Registration records for the domain list ENOM, INC. as the registrar and Nov 6, 2019 as the creation date. At collection time, the hostname resolved to 15.197.172.60 on AS16509 (Amazon.com, Inc.). The recorded endpoint location is Montreal, CA. The stored server header is openresty. The evidence archive retains 2 visual captures from PhishDestroy and URLScan; no page title was retained, so the captures preserve the landing-page appearance. TLS metadata lists GoDaddy.com as the certificate issuer with validity through Jan 9, 2027; checked Sep 2, 2026 at 22:02 UTC.

The record contains 3 positive source findings supporting the current phishing classification. The stored fields do not identify an impersonated brand or victim interaction.