recursos[.]adobeexperience[.]com[.]br

recursos.adobeexperience.com.br is a subdomain of adobeexperience.com.br. PhishDestroy first observed the hostname on Jan 24, 2026. The captured page title is “ADOBE”. Current evidence score: 100/100 (critical).

Positive findings are stored from 4 sources: VirusTotal, Spamhaus DBL, DNS security resolvers, and Cloudflare Radar. VirusTotal recorded 16 detections among 91 engines: ADMINUSLabs, BitDefender, Chong Lua Dao, CyRadar, ESET, Emsisoft, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, Kaspersky, Lionic, Netcraft, Sophos, VIPRE, Webroot on Jul 26, 2026 at 03:44 UTC. Spamhaus DBL: DBL_PHISH on Jul 14, 2026 at 10:38 UTC. DNS security checks returned 5 blocking results across 15 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 security threats and phishing; its verdict timestamp was not retained. Non-positive and contextual checks: The external blocklist snapshot contained no matches on Aug 8, 2026 at 02:20 UTC. URLQuery recorded no positive detection; no observation timestamp was retained. Google Safe Browsing returned no flag on Mar 2, 2026 at 20:21 UTC. URLScan completed without a malicious verdict (score 0) on Jul 29, 2026 at 02:55 UTC. PhishStats returned no feed match on Mar 1, 2026 at 16:10 UTC.

HTTP 302 was recorded on Aug 7, 2026 at 22:22 UTC. Registration records for the registrable domain adobeexperience.com.br list GoDaddy.com, LLC as the registrar. At collection time, the hostname resolved to 203.161.35.179 on AS22612 (Namecheap, Inc.). The recorded endpoint location is Phoenix, US. The stored server header is nginx. DOM analysis on Jul 9, 2026 at 02:21 UTC returned 88/100. The evidence archive retains 2 visual captures from PhishDestroy and URLScan. TLS metadata lists R12 as the certificate issuer with validity through May 17, 2026; checked Mar 15, 2026 at 05:45 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.