VirusTotal
6 / 89
Interpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“www.adobe.com”
Assessment based on the stored source evidence below. Review sources →
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
6 / 89
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
DBL_PHISH
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
4 community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: clean
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
stored report
Report A preserved page image documents what the collector received; a capture is not a safety verdict.
Analysis completed
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Stored narrative · generated . Provider checks below retain their own observation dates.
reply-adobe.us returned HTTP 301 in a check dated 2026-10-01, a recorded redirect response rather than page content. The same domain appears on the MetaMask and SEAL external blocklists, and it was first observed on 2026-08-31.
The HTTP check on 2026-10-01 recorded status 301 for reply-adobe.us. VirusTotal, checked 2026-09-14, reported 6 detections across 89 scanners. OTX, also checked 2026-09-14, listed 4 pulses, and the domain carries a phishdestroy internal listing. Registration occurred on 2026-07-21, while the SSL scan on 2026-08-31 named Google Trust Services / WE1 as issuer. The external blocklist count of 2 covers MetaMask and SEAL, and the IP address 104.21.13.249 sits with Cloudflare, Inc. in CA.
The named sources describe different aspects of reply-adobe.us: a redirect response, blocklist placements, scanner detections, OTX pulses, and a phishdestroy listing. Because the checks fall on separate dates, the records show what each source reported at its own point in time rather than a single combined picture. The chronology from first observation to the later checks is useful for ordering the records, but it does not establish that any condition changed.
Preserve the MetaMask and SEAL blocklist entries, the VirusTotal result, and the OTX pulses as separate records for reply-adobe.us. Compare those source records against future checks of the same domain rather than merging them into one judgment. Retain the phishdestroy internal listing alongside the external blocklist entries for later review.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: redirect: raw=redirect_301; http=301; via=https_proxy; location=https://adobe.com/; server=cloudflare
Edge-IP reputation is not attributed to this domain.
anastasia.ns.cloudflare.compete.ns.cloudflare.comemx.mail.rupriority 10Location describes the IP network.
0fda22f6411cb9a4f4dae8a995e4fcdbe9f4f09ed7294c6b3329f5230d6652a9Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
104.21.13.249.12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive