pancakeswap-pancake.webflow.io is a PancakeSwap impersonation page detected by PhishDestroy on 2026-09-12. Risk: high (65/100). Registrar: Webflow. Status: Content unavailable. Hosting: Cloudflare, Inc. VirusTotal: 4/89 engines flag it. Do not enter credentials or connect a wallet.
“404 - Page not found”
Registrar
Webflow
Resolved IP
172.64.151.8
Registered
May 8, 2013
PhishDestroy assessment
High65/100Evidence score
Availability
Content unavailableContent was unavailable in the latest observationObserved · HTTP probe
pancakeswap-pancake.webflow.io is an impersonation phishing page that borrowed the PancakeSwap name to lure traders of the decentralized exchange. It sat on a free Webflow subdomain, where anyone can publish a site in minutes under a name that looks official at a glance. PhishDestroy first saw it on 2026-09-12. The site has been dead since 2026-09-19 and was still offline at the last check on 2026-10-19, with nothing served at the root.
How the scam works
Fake PancakeSwap pages usually copy the exchange's swap interface and ask visitors to connect a wallet. They then push the victim to sign a token approval or transaction that hands their funds to the attacker, or to type a recovery phrase under the pretext of fixing a sync or connection error. Either way, the victim can lose the tokens in that wallet, and with a leaked seed phrase they lose the whole wallet. The page title now reads "404 - Page not found", while we classified the site as PancakeSwap impersonation phishing.
Evidence
On 2026-09-20 four of 89 VirusTotal engines flagged the address: alphaMountain.ai, Fortinet, PhishFort and VIPRE. That is a small share, but PhishFort focuses on crypto brand abuse, which makes its verdict relevant here. PhishDestroy lists the domain on its own blocklist. The low count means many browsers and security tools may never have warned visitors while the page was live.
Infrastructure
The operation used no domain of its own. It ran as a subdomain of Webflow's hosting platform, so the registrar is Webflow, and traffic was served through Cloudflare's network from an address geolocated to Canada. This kind of setup is cheap and disposable. A phisher can abandon the subdomain and stand up a new one with a fresh PancakeSwap-style name, which fits the roughly one week between our first sighting and the site going offline.
What to do
If you connected a wallet to this page, open a token-approval checker for the networks you use and revoke any approvals you don't recognize. Do this before moving any more funds. If you typed your recovery phrase, treat that wallet as compromised and move your assets to a new wallet with a newly generated seed. Reach PancakeSwap only through a bookmark you saved yourself, never through links in ads, DMs or search results. Defenders should block this subdomain and watch for new Webflow subdomains that combine "pancakeswap" with other words.
No. PhishDestroy classifies pancakeswap-pancake.webflow.io as a PancakeSwap impersonation page (risk: high, 65/100); it was first detected on 2026-09-12. VirusTotal: 4/89 engines flag it. Treat the site as unsafe.
Is pancakeswap-pancake.webflow.io safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on pancakeswap-pancake.webflow.io. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
What should I do if I used pancakeswap-pancake.webflow.io?
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
Registration (base domain)webflow.io · Created May 8, 2013 —Expires May 8, 2028
HTTP Status404 Not Found
Time to First Unavailability7 days
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
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 DetectedSep 12, 2026
Observed page title
404 - Page not found
Automated brand references
PancakeSwap
TLS Certificate
Issued by Google Trust Services / WE1
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
172.64.151.8
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Nameservers 2
journey.ns.cloudflare.com
lamar.ns.cloudflare.com
Location describes the IP network.
TLS certificate
Issuer
Google Trust Services / WE1
Valid from
2026-07-25 02:21:21
Valid until
2026-10-23 03:21:05
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprinta4ffdefa8d99689893e2aafdf9588b6f8f2f8ec47698ea534dbfa409dbbde19dCertificate names · 2 SANs
webflow.io
*.webflow.io
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches4
Same favicon hash or the same page title as this host.
2 evidence signal groups linked0 stored notification recordsContent unavailable
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
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 →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident
Recommendations & Advice for Victims
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.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
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 pancakeswap-pancake.webflow.io)
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
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.
(US)
