PhishDestroy first recorded rosaehessfrzimbra.vercel.app on 2026-10-26. Stored VirusTotal result: 17/92 engines flagged. Malicious: 16. Suspicious: 1. Analysis time (as stored): 2026-10-26 09:49 UTC. Retrieved (as stored): 2026-10-26 11:59 UTC.
Page title: “Zimbra Web Client Sign In”
More about the sources
Recorded security signals
Stored VirusTotal result: 17/92 engines flagged. Malicious: 16. Suspicious: 1. Analysis time (as stored): 2026-10-26 09:49 UTC. Retrieved (as stored): 2026-10-26 11:59 UTC. Use caution — do not enter credentials or personal information.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
Analysis
Domain summary
PhishDestroy first recorded rosaehessfrzimbra.vercel.app on 2026-10-26. Stored VirusTotal result: 17/92 engines flagged. Malicious: 16. Suspicious: 1. Analysis time (as stored): 2026-10-26 09:49 UTC. Retrieved (as stored): 2026-10-26 11:59 UTC. Risk: critical (evidence score 95/100). Status: Reachable · access restricted. Hosting: Amazon.com, Inc. Do not enter credentials or connect a wallet.
As observed on 2026-10-26, the captured screenshot shows a blue sign-in card headed Authentication EHESS with an E-mail field, a Mot De Passe password field, a Stay Logged In checkbox, a Sign In button, a Version dropdown set to Standard, and a footer naming Zimbra as a registered trademark of Synacor, Inc. PhishDestroy listed the domain after its automated assessment classified it as a credential phishing page, first seen on 2026-10-26.
How the scam works
The page imitates a Zimbra web mail sign-in so that a visitor arriving from a lure types a mailbox address and password into attacker-controlled fields. Because the form mirrors a familiar login, submitted credentials can be captured and replayed against the genuine mailbox, enabling account takeover and follow-on email abuse.
Evidence
The captured screenshot shows French-labelled login fields asking for E-mail and Mot De Passe beneath an Authentication EHESS heading, with a Zimbra trademark footer. urlscan returned a malicious verdict with an ML score of 99 and an overall phishing score of 100 on 2026-10-26, and its capture records a 307 redirect funnel from the plain HTTP form to the HTTPS form of the same host, with one tracker request observed. VirusTotal flagged the domain as malicious, while Spamhaus recorded no listing, Google Safe Browsing was not flagged, and OTX recorded 0 pulses, all checked on 2026-10-26. PhishFeed and PhishDestroy's internal blocklist flagged it on 2026-10-26, and one of twelve tested DNS resolvers, CloudFlare Family, blocked it.
Infrastructure
The page was served through Vercel infrastructure with the server header recording Vercel, and the TLS certificate is a wildcard issued for the hosting platform rather than for the displayed brand. Notable weaknesses: Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy and COOP/COEP/CORP are all absent while strict-transport-security carries a long max-age; DNSSEC unsigned; no email authentication with zero SPF lookups and no DKIM or DMARC recorded; CAA records present. Transport security used TLS 1.3, AES-128-GCM, forward secrecy and ALPN h2 as observed on 2026-10-26.
What to do
Anyone who entered credentials on rosaehessfrzimbra.vercel.app should immediately change the password on the genuine Zimbra mailbox and enable two-factor authentication. Review recent mail activity and sign-in history for unauthorized access, and treat the entered password as exposed wherever it was reused. Security teams should block rosaehessfrzimbra.vercel.app at proxy and DNS layers and hunt for similar lookalike sign-in pages.
This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.
PhishDestroy assesses rosaehessfrzimbra.vercel.app as a Zimbra credential phishing page captured on 2026-10-26.
AI summary
Overview As observed on 2026-10-26, the captured screenshot shows a blue sign-in card headed Authentication EHESS with an E-mail field, a Mot De Passe password field, a Stay Logged In checkbox, a Sign In button, a Version dropdown set to Standard, and a footer naming Zimbra as a registered trademark of Synacor, Inc. PhishDestroy listed the domain after its automated assessment classified it as a credential phishing page, first seen on 2026-10-26. How the scam works The page imitates a Zimbra web mail sign-in so that a visitor arriving from a lure types a mailbox address and password into attacker-controlled fields. Because the form mirrors a familiar login, submitted credentials can be captured and replayed against the genuine mailbox, enabling account takeover and follow-on email abuse. Evidence The captured screenshot shows French-labelled login fields asking for E-mail and Mot De Passe beneath an Authentication EHESS heading, with a Zimbra trademark footer. urlscan returned a malicious verdict with an ML score of 99 and an overall phishing score of 100 on 2026-10-26, and its capture records a 307 redirect funnel from the plain HTTP form to the HTTPS form of the same host, with one tracker request observed. VirusTotal flagged the domain as malicious, while Spamhaus recorded no listing, Google Safe Browsing was not flagged, and OTX recorded 0 pulses, all checked on 2026-10-26. PhishFeed and PhishDestroy's internal blocklist flagged it on 2026-10-26, and one of twelve tested DNS resolvers, CloudFlare Family, blocked it. Infrastructure The page was served through Vercel infrastructure with the server header recording Vercel, and the TLS certificate is a wildcard issued for the hosting platform rather than for the displayed brand. Notable weaknesses: Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy and COOP/COEP/CORP are all absent while strict-transport-security carries a long max-age; DNSSEC unsigned; no email authentication with zero SPF lookups and no DKIM or DMARC recorded; CAA records present. Transport security used TLS 1.3, AES-128-GCM, forward secrecy and ALPN h2 as observed on 2026-10-26. What to do Anyone who entered credentials on rosaehessfrzimbra.vercel.app should immediately change the password on the genuine Zimbra mailbox and enable two-factor authentication. Review recent mail activity and sign-in history for unauthorized access, and treat the entered password as exposed wherever it was reused. Security teams should block rosaehessfrzimbra.vercel.app at proxy and DNS layers and hunt for similar lookalike sign-in pages. Useful links urlscan.io scan and screenshot: https://urlscan.io/result/01a1780a-4769-75db-88b6-094032f6ea02/ Stored capture screenshot: https://i.ibb.co/5x2g6H6F/91a313f4a73c.png URLScan screenshot (2026-10-25T00:15:47Z): https://screenshots.phishdestroy.io/us/01a17069-c00a-72df-97f2-d902023ddfad.png URLScan capture report: https://urlscan.io/result/01a17069-c00a-72df-97f2-d902023ddfad/ URLScan screenshot (2026-10-26T01:04:14Z): https://screenshots.phishdestroy.io/us/01a175bc-741f-71bb-b644-387be4486d7a.png URLScan capture report: https://urlscan.io/result/01a175bc-741f-71bb-b644-387be4486d7a/ URLScan screenshot (2026-10-26T04:49:28Z): https://screenshots.phishdestroy.io/us/01a1768a-ac16-76df-92f4-2414a1284c59.png URLScan capture report: https://urlscan.io/result/01a1768a-ac16-76df-92f4-2414a1284c59/ URLScan screenshot (2026-10-26T07:40:55Z): https://screenshots.phishdestroy.io/us/01a17726-4208-71bc-af67-5d9d4a9c32f6.png URLScan capture report: https://urlscan.io/result/01a17726-4208-71bc-af67-5d9d4a9c32f6/ URLScan screenshot (2026-10-26T11:04:05Z): https://screenshots.phishdestroy.io/us/01a177e1-80c5-774d-936b-3b63c34c6559.png URLScan capture report: https://urlscan.io/result/01a177e1-80c5-774d-936b-3b63c34c6559/ URLScan screenshot (2026-10-26T11:46:32Z): https://screenshots.phishdestroy.io/us/01a17808-5c00-733a-825a-f02c03fd8071.png URLScan capture report: https://urlscan.io/result/01a17808-5c00-733a-825a-f02c03fd8071/ VirusTotal report: https://www.virustotal.com/gui/domain/rosaehessfrzimbra.vercel.app Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=rosaehessfrzimbra.vercel.app Archived copy: https://web.archive.org/web/20261026113936/https://rosaehessfrzimbra.vercel.app/ Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/ Site owner? Request a review: https://phishdestroy.io/appeals/
PhishDestroy rates rosaehessfrzimbra.vercel.app as critical risk (evidence score 95/100) from the recorded evidence; it was first recorded on 2026-10-26. Stored VirusTotal result: 17/92 engines flagged. Malicious: 16. Suspicious: 1. Analysis time (as stored): 2026-10-26 09:49 UTC. Retrieved (as stored): 2026-10-26 11:59 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Is rosaehessfrzimbra.vercel.app safe to connect a wallet?
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on rosaehessfrzimbra.vercel.app. A confirmed blockchain transaction cannot be reversed.
What should I do if I used rosaehessfrzimbra.vercel.app?
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Downloaded a file — do not open it and scan the device with security software
Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned. Step-by-step help: emergency guide.
What we count Raw elapsed time since the first stored abuse report. It is not a registrar response-time measurement. Latest observed status: Reachable · access restricted.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First Detected2026-10-26
DOM Analysisanalyzed 2026-10-26score 0/100
Submitted URLhttp://rosaehessfrzimbra.vercel.app/
Favicon Hash
Observed page title
Zimbra Web Client Sign In
TLS Certificate
Issued by WR1· stored validity ends in 5 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
64.29.17.131
Network ASN
AS16509
AS name
AMAZON-02 - Amazon.com, Inc., US
Organization
Amazon.com, Inc.
Observed location
Walnut, US
Server header
Vercel
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
TLS certificate
Issuer
WR1
Valid from
2026-08-29 19:48:09
Valid until
2026-11-27 19:48:08
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint8f46c4a0a289bfde4060d06986f2af761ee62d668dde972e6bef4687ee4f6093Certificate names · 1 SAN
*.vercel.app
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Observed timelinelast reachable: 2026-10-30 12:05 UTClast content: 2026-10-30 12:05 UTCcurrent episode first observed: 2026-10-30 23:53 UTCobserved RIP window: 2026-10-30 12:05 UTC → 2026-10-30 23:53 UTC · 11.80hmidpoint estimate ≈ 2026-10-30 17:59 UTC · precision medium · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-10-29 01:56 UTC.
Recorded events: 11. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Hours from detection to the first unavailable observation: 108
Monitoring Continues
The domain remains reachable or access-restricted; future checks may update this observation.
ongoing
Recorded activity
4 entries
Lifecycle
Domain registered
VirusTotal analysis with detections+2463 d 6 h
Added to PhishDestroy+2 h 1 min
Added to PhishDestroy
rosaehessfrzimbra.vercel.app
same minute
URLScan
Page captured
+10 min
Wayback Machine
Page archived
+1 h 50 min
VirusTotal
17/92 engine detections
How we investigate & report
Public scans, evidence and abuse channels
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.
01Public scans & evidence collection10 sources and tool groups
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
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.
Supporting signal — Shares a page feature, infrastructure or a collector label; not proof of one operator.
Each spoke is one reason a domain is linked to this report. Node size marks VirusTotal detections, dashed nodes are already offline, and the full lists follow below. Full list of related reports
Content matches4
Same favicon file hash, or a recorded page title that starts with the same 20 characters. A content match does not establish a shared phishing kit or owner.
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.
Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
Downloaded a file — do not open it and scan the device with security software
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed
What information should I collect for my report?
FBI guidelines
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including rosaehessfrzimbra.vercel.app)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
About this reportSources, observation dates and corrections
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.