PhishDestroy first recorded 69d74f2529518e1292b8c6c5--thriving-macaron-9e8f94.netlify.app on 2026-10-22. Stored VirusTotal result: 18/92 engines flagged. Malicious: 16. Suspicious: 2. Analysis time (as stored): 2026-10-22 09:03 UTC. Retrieved (as stored): 2026-10-22 22:03 UTC.
Page title: “Email Server”
More about the sources
Recorded security signals
Stored VirusTotal result: 18/92 engines flagged. Malicious: 16. Suspicious: 2. Analysis time (as stored): 2026-10-22 09:03 UTC. Retrieved (as stored): 2026-10-22 22:03 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 69d74f2529518e1292b8c6c5--thriving-macaron-9e8f94.netlify.app on 2026-10-22. Stored VirusTotal result: 18/92 engines flagged. Malicious: 16. Suspicious: 2. Analysis time (as stored): 2026-10-22 09:03 UTC. Retrieved (as stored): 2026-10-22 22:03 UTC. Risk: critical (evidence score 100/100). Status: Last known active. Hosting: AMAZON-02 - Amazon.com, Inc., US. Do not enter credentials or connect a wallet.
PhishDestroy’s intake AI recorded a malicious verdict on 2026-10-19 because the page displayed a Roundcube Webmail‑style login form that requested a username and password. The domain was first seen by PhishDestroy on 2026-10-22 and an HTTP 200 response was captured on 2026-10-26.
How the scam works
Attackers host a replica of a webmail login page and brand it as Roundcube to trick users into entering their credentials. Harvested usernames and passwords can be reused to compromise the victims’ real email accounts or sold on underground markets.
Evidence
VirusTotal scanned the domain on 2026-10-22 and returned 18 detections from 92 engines, with 16 classified as malicious and 2 as suspicious. Google Safe Browsing checked on 2026-10-25 and did not flag the site. urlscan captured the page on 2026-10-22, its engine gave a malicious score of 99 and applied phishing‑related tags, while the overall verdict was non‑malicious. PhishDestroy’s internal blocklist marks the domain as malicious; external blocklists reported zero hits, Spamhaus DBL listed it as clean, and OTX showed no pulses as of 2026-10-23.
Infrastructure
The recorded IP was 63.176.8.218, belonging to Amazon.com, Inc. in Germany, and the site was served through Netlify’s *.netlify.app CDN. The TLS certificate observed on 2026-10-23 was issued by DigiCert Global G2 TLS RSA SHA256 2020 CA1, valid from 2026-02-16 to 2027-03-19, and the domain and TLS were 196 and 248 days old respectively at the time of capture.
What to do
Anyone who may have entered credentials should change the associated email password immediately and enable multi‑factor authentication. Organizations should block the exact Netlify subdomain at their perimeter devices and monitor authentication logs for suspicious activity while continuing to watch threat‑intel feeds for any reuse of the same infrastructure.
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 flagged 69d74f2529518e1292b8c6c5--thriving-macaron-9e8f94.netlify.app as malicious for a Roundcube Webmail login asking for username and password.
AI summary
Overview PhishDestroy’s intake AI recorded a malicious verdict on 2026-10-19 because the page displayed a Roundcube Webmail‑style login form that requested a username and password. The domain was first seen by PhishDestroy on 2026-10-22 and an HTTP 200 response was captured on 2026-10-26. How the scam works Attackers host a replica of a webmail login page and brand it as Roundcube to trick users into entering their credentials. Harvested usernames and passwords can be reused to compromise the victims’ real email accounts or sold on underground markets. Evidence VirusTotal scanned the domain on 2026-10-22 and returned 18 detections from 92 engines, with 16 classified as malicious and 2 as suspicious. Google Safe Browsing checked on 2026-10-25 and did not flag the site. urlscan captured the page on 2026-10-22, its engine gave a malicious score of 99 and applied phishing‑related tags, while the overall verdict was non‑malicious. PhishDestroy’s internal blocklist marks the domain as malicious; external blocklists reported zero hits, Spamhaus DBL listed it as clean, and OTX showed no pulses as of 2026-10-23. Infrastructure The recorded IP was 63.176.8.218, belonging to Amazon.com, Inc. in Germany, and the site was served through Netlify’s *.netlify.app CDN. The TLS certificate observed on 2026-10-23 was issued by DigiCert Global G2 TLS RSA SHA256 2020 CA1, valid from 2026-02-16 to 2027-03-19, and the domain and TLS were 196 and 248 days old respectively at the time of capture. What to do Anyone who may have entered credentials should change the associated email password immediately and enable multi‑factor authentication. Organizations should block the exact Netlify subdomain at their perimeter devices and monitor authentication logs for suspicious activity while continuing to watch threat‑intel feeds for any reuse of the same infrastructure. Useful links urlscan.io scan and screenshot: https://urlscan.io/result/01a16597-84c3-7761-b68e-0a45a2fed77b/ Stored capture screenshot: https://urlscan.io/screenshots/01a16597-84c3-7761-b68e-0a45a2fed77b.png URLScan screenshot (2026-10-19T20:18:09Z): https://screenshots.phishdestroy.io/us/01a155d0-6671-7683-ad0e-5db67fa7d5bd.png URLScan capture report: https://urlscan.io/result/01a155d0-6671-7683-ad0e-5db67fa7d5bd/ VirusTotal report: https://www.virustotal.com/gui/domain/69d74f2529518e1292b8c6c5--thriving-macaron-9e8f94.netlify.app Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=69d74f2529518e1292b8c6c5--thriving-macaron-9e8f94.netlify.app Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/ Site owner? Request a review: https://phishdestroy.io/appeals/
Questions about 69d74f2529518e1292b8c6c5--thriving-macaron-9e8f94.netlify.app
Is 69d74f2529518e1292b8c6c5--thriving-macaron-9e8f94.netlify.app legit?
PhishDestroy rates 69d74f2529518e1292b8c6c5--thriving-macaron-9e8f94.netlify.app as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-10-22. Stored VirusTotal result: 18/92 engines flagged. Malicious: 16. Suspicious: 2. Analysis time (as stored): 2026-10-22 09:03 UTC. Retrieved (as stored): 2026-10-22 22:03 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Is 69d74f2529518e1292b8c6c5--thriving-macaron-9e8f94.netlify.app safe to connect a wallet?
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on 69d74f2529518e1292b8c6c5--thriving-macaron-9e8f94.netlify.app. A confirmed blockchain transaction cannot be reversed.
What should I do if I used 69d74f2529518e1292b8c6c5--thriving-macaron-9e8f94.netlify.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.
Certificate fingerprintbc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478Certificate names · 2 SANs
*.netlify.app
netlify.app
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: Stale
Latest HTTP observationLive contentOrdinary HTTP content served90%2026-11-22 11:41 UTC
RDAP registration
Observed timelinelast reachable: 2026-11-22 11:41 UTClast content: 2026-11-22 11:41 UTC
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 02:01 UTC.
Recorded events: 7. 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.
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 matches5
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 69d74f2529518e1292b8c6c5--thriving-macaron-9e8f94.netlify.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.