Skip to security report
Analytics Dashboard
Domain security report
poncakeswap.finance favicon

poncakeswap.finance

“CloudFlare - Verify that you are a human”

Threat verdict
CriticalDomain Appeal
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 16/89 Spamhaus DBL: DBL_PHISH Stored blocklist matches: 3 URLQuery threat systems: 1 alert Automated brand label: Cloudflare
OTX: 4 refs Aug 31, 2026 Cloudflare 1 Report Sent CDN
API
Registrar
Dynadot
Resolved IP
54.215.31.113
Registered
Aug 28, 2026
3 sources
The capture source is temporarily unavailable.
1 / 3
Source
Primary capture
Collected · UTC
Open capture
In this reportGet help
This domain has been flagged as malicious
Security engines reporting a detection: 16. Public blocklists reporting a match: 3. Exercise extreme caution — do not enter credentials or personal information.
ABUSE NOTICE · 7D+ OPEN Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence

The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@dynadot.com. The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.

ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.

Elapsed since first report
1 month
Reports sent
1
Latest case ID
PD-20260831-32742F
Current status
HTTP 301 at latest stored check

Additional indicators at a glance

Spamhaus DBL
DBL_PHISH
VirusTotal
VirusTotal
16 det.
URLQuery
URLQuery
1 threat alert
OTX references
4 community refs
URLScan
URLScan
Report ↗
ScamAdviser
Scamadviser
80/100Likely Safe
TLS Certificate
Within stored validity dates
Let's Encrypt · Hostname coverage not recorded
Age
2 mo New
Observed status
Last known active 301
PhishDestroy
DestroyList
Listed
Reports Sent
1

Source evidence

10 · 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.

VirusTotal

16 / 89

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

URLQuery

1 threat-system alert

Report
Interpretation & limits

Alerts refer to the preserved scan. They do not describe the current state of the site.

Public blocklists

3 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Spamhaus DBL

DBL_PHISH

Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

OTX

4 community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

CF Radar

provider verdict: clean

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLScan capture

stored report

View stored capture ↗
Report
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

URLScan verdict

Analysis completed

Report
Interpretation & limits

This is the recorded automated analysis. Completion alone is not a safety verdict.

Scamadviser

80/100

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Google Safe Browsing

Checked; no threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Network Security Intelligence
Threat Detection Systems 1 alert
Detection System Indicator Verdict Alert
DNS4EU pancackeswap.org malicious Sinkholed
Stored URLQuery scan evidence · Aug 31, 2026 08:06 UTC Open source report

Evidence Summary

Critical
VirusTotal
16/89
OTX
4 community refs
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

Assessment

Stored evidence for poncakeswap.finance: VirusTotal recorded 4 detections among 91 scanners on 2026-08-31. That ratio reproduces the stored check in its original units and is not converted into another measure. MetaMask and SEAL appear as named external blocklist observations for poncakeswap.finance. Each item in this report remains at the scope supplied by its dated source record.

Detection Evidence

VirusTotal records 4 detections among 91 scanners in the stored snapshot dated 2026-08-31. The numerator describes scanners that produced detections, while the denominator describes scanners included in that check. The reverse order would materially alter the stored result. The VirusTotal snapshot dated 2026-08-31 supplies no common rationale covering the included scanners, and this report adds none. A later VirusTotal snapshot may contain different values, so any comparison should preserve the exact ratio and date of each snapshot.

Source Context

MetaMask and SEAL are recorded as named external blocklist observations for poncakeswap.finance in the snapshot dated 2026-08-31. The stored MetaMask and SEAL blocklist records supply names and entries, but they supply no shared method or common rationale. PhishDestroy’s catalogue also contains poncakeswap.finance as a publisher record. That PhishDestroy record is counted separately from the MetaMask and SEAL external blocklist observations. This separation keeps the origin of every entry visible and prevents a single stored item from being counted again under another source label.

Reachability and Timeline

The record first observed poncakeswap.finance on 2026-08-31. The MetaMask and SEAL blocklist snapshot is dated 2026-08-31 and remains a separate event in the stored timeline. The registration date is separately recorded as 2026-08-28. A URLScan reference was stored on 2026-08-31 as a dated artifact for review. Each timestamp qualifies only the adjacent observation in this timeline. Later collection results should be compared with these dated values without replacing the earlier snapshot.

Registration and Infrastructure

For poncakeswap.finance, the registrar field records Dynadot Inc; this is kept as an exact source value. The source stores 54.215.31.113 as the observed address in this record. The registration date for poncakeswap.finance is recorded as 2026-08-28. These fields preserve registration, network, and certificate context stored in this record. The report preserves each label and number as a separate source value instead of combining them into an invented aggregate. Keeping the fields separate leaves every infrastructure value traceable to the record that supplied it.

Conclusion

The poncakeswap.finance record states that VirusTotal recorded 4 detections among 91 scanners on 2026-08-31. MetaMask and SEAL remain named blocklist observations from the snapshot dated 2026-08-31. PhishDestroy remains a separate publisher catalogue entry in the stored record. For poncakeswap.finance, the registrar field records Dynadot Inc; this remains separate from the other source fields. The observed address field in this record contains 54.215.31.113. The supported conclusion is bounded to the exact stored observations for poncakeswap.finance. Any statement beyond those source values would require additional dated material.

Recommended Actions

Avoid submitting sensitive information to poncakeswap.finance during review. Use a known service address obtained separately from this report for any necessary access. Defenders can retain poncakeswap.finance as an exact indicator and preserve relevant DNS, proxy, and endpoint records. Compare later VirusTotal snapshots and MetaMask and SEAL blocklist records with the dated values above instead of replacing them. Keep each later observation with its source date so changes remain visible during follow-up review. If a defensive rule is needed, keep its scope to poncakeswap.finance. The stored record does not justify extending that rule to 54.215.31.113 or to other infrastructure records.

Data coverage & collection

23 · datasets with records / 8 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
16 / 89 · engine detections
URLScan analysis
Automated verdict retained
URLQuery
2 · recorded detections / alerts
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
4 · community references
External blocklists
3 · external matches
Cloudflare Radar
cleanCollection time not recorded
Scamadviser
80/100 · provider trust scoreCollection time not recorded
Spamhaus DBL
DBL_PHISH
Domain registration
Dynadot IncCollection time not recorded
Network & DNS
54.215.31.113 · 2 · nameserversCollection time not recorded
TLS certificate
Let's Encrypt
Page captures
3 · retained captures
Page analysis
0 · automated brand labels
Observed indicators
0 · wallet / Telegram indicators
Detection & evasion
Stored browser and crawler comparison
PageSpeed performance
99/100 · mobile performance
Response records
1 · outgoing report records
Availability history
30 · stored state changes
Source observation history
1 · stored source events
Lookalike relationships
100 · retained relationshipsCollection time not recorded
Chainabuse records
2 · recorded reports
IP reputation
Network-level observations
Not recorded in this report 8

These checks have no retained result. This does not mean they passed or that a scan is running.

  • PhishStats
  • DNS security filters
  • Gridinsoft
  • HTML archives
  • Site configuration files
  • Recorded subdomains
  • Community reports
  • Wayback archive
Download the dated observations and supporting metadata.

Blocklist records

3 · external source matches

Public Blocklist Status

Domain, network & archive

Dynadot Inc · 54.215.31.113 · DNS, TLS and retained responses

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-08activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Dynadot (Unknown)
Abuse contactabuse@dynadot.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for poncakeswap.finance →
RegistrationCreated Aug 28, 2026 (50d · New) — Expires Aug 28, 2027
HTTP Status301 Moved Permanently
Technical detailsProvenance & timestamps
First DetectedAug 31, 2026
DOM Analysisanalyzed Oct 9, 2026score 100/100
Submitted URLhttp://poncakeswap.finance/
Favicon Hash
Case ID
ICANN OVERSIGHT

Accreditation and RAA context
Registrar accreditation and DNS abuse obligations

For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
54.215.31.113
Network ASN
AS16509
Organization
AWS EC2 (us-west-1)
Observed location
San Jose, US
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2
  • ns1.dyna-ns.net
  • ns2.dyna-ns.net

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt
Valid from
2026-08-28 15:41:40
Valid until
2026-11-26 15:41:39
Hostname coverage
Hostname coverage not recorded
Validity
Within stored validity dates
Collection time
2026-10-10 22:02:44 UTC
Collection source
PhishDestroy collector
Certificate fingerprint59af53172c5b884671e3ae57a4680ae6c06cabf9d36a953c703d65fc3cdb84a5

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

viewdns.info · 54.215.31.113rapiddns.io

Latest Classified Outcome 2026-10-17 10:29:38 UTC

Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-17 10:29:38 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-17 10:29:38 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.
Technologies · 4 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

16 / 89 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 8 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
SOCRadar
Sophos
VIPRE
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of poncakeswap.finance · checked Aug 31, 2026

99
Good
Performance
FCP
1.55s
First Contentful Paint
LCP
1.55s
Largest Contentful Paint
CLS
0.013
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.08s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details2

Availability observations

Last reachable observation
Estimate basis
Currently reachable

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Detection & evasion checks

Stored browser and crawler observations

Detection-evasion analysis

Cloaking and traffic-distribution check

Not yet scanned No crawler-versus-browser difference has been recorded yet

Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.

Stored cloaking flag
Not yet scanned
Last cloaking scan

Scanner note: redirect: raw=redirect_301; http=301; via=https_proxy; location=https://pancekeswap.finance

Live TDS fingerprint check
Seven Keitaro fingerprints and a browser-versus-crawler comparison. A new scan starts only when you press the button.
Saved result
Cloaked / Filtered

Timeline & response

1 · outbound report records

Forensic History & Detection Timeline

ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
  1. Threat First Observed 2026-08-31 07:58:32 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as alive pointing to IP 54.215.31.113.
Stored observation history31

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  2. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  3. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  4. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  5. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

Earlier observations 26
  1. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  2. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  3. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  4. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  5. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  6. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  7. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  8. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  9. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  10. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  11. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  12. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  13. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  14. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  15. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  16. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  17. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  18. Availability monitor · Recorded state

    redirected→Unknown

    stale_current_evidence

  19. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  20. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  21. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  22. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  23. Availability monitor · Recorded state

    redirected→Unknown

    probe_inconclusive

  24. Availability monitor · Recorded state

    Unknown→redirected

    http_redirect

  25. Availability monitor · Recorded state

    Unknown

    probe_inconclusive

  26. Availability monitor · First collection record

    Reachable

Threat Response Pipeline

Discovery
Analysis
Notifications
Monitoring

12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Threat Ingested
poncakeswap.finance detected and queued for full analysis
Aug 31, 2026
Spamhaus DBL
Spamhaus DBL recorded DBL_PHISH
Sep 30, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Aug 31, 2026
Cloudflare Radar Report
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
VirusTotal
16/89 recorded on VirusTotal
Sep 12, 2026
Blocklist Detection
Found in 3 blocklists: MetaMask, ScamSniffer, SEAL
Oct 17, 2026
OTX Community References
4 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Oct 5, 2026
Brand Impersonation
Impersonation of Cloudflare
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
Aug 31, 2026
Technical Analysis Recorded
The report contains stored technology or forensic-analysis results.
Oct 17, 2026
Sent Report Recorded
Stored outgoing record associated with registrar Dynadot Inc, 1 abuse contact
abuse@dynadot.com
Aug 31, 2026
DestroyList Published
Listed in the public PhishDestroy/DestroyList repository
Aug 31, 2026
Monitoring Continues
The domain remains reachable or access-restricted; future checks may update this observation.
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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Related infrastructure

Shared hosting, registrar records and related domains

Lookalike domains

142 stored lookalike domains

c.loudflare.com subdomain claudflare.com vowel-swap cloadflare.com vowel-swap cloduflare.com transposition cloodflare.com vowel-swap clou.dflare.com subdomain cloudf.lare.com subdomain cloudfalre.com transposition cloudfla.re.com subdomain cloudflaer.com transposition cloudflarecom.com various cloudflore.com vowel-swap
Show all (88)
cloudflrae.com transposition cloudflure.com vowel-swap cloudflwre.com replacement cloudlfare.com transposition cloufdlare.com transposition cluodflare.com transposition coludflare.com transposition c1oudf1are.com homoglyph c1oudflare.com homoglyph ccloudflare.com repetition cioudfiare.com homoglyph cioudflare.com homoglyph ckoudflare.com replacement cl0udfiare.com homoglyph cliudflare.com replacement clludflare.com replacement clo-udflare.com hyphenation clodflare.com omission clohdflare.com replacement cloidflare.com replacement clooudflare.com insertion cloubflare.com homoglyph clouclflare.com homoglyph cloud-flare.com hyphenation cloudcflare.com insertion cloudclare.com replacement clouddflare.com insertion cloudfare.com omission cloudfflare.com insertion cloudfiare.com homoglyph cloudfla1re.com insertion cloudflaare.com repetition cloudflae.com omission cloudflaee.com replacement cloudflar.com omission cloudflarr.com replacement cloudflarre.com repetition cloudflarz.com replacement cloudflate.com replacement cloudfllare.com repetition cloudflre.com omission cloudflsre.com replacement cloudiflare.com homoglyph cloudlare.com omission cloudlflare.com homoglyph cloudsflare.com insertion cloudtflare.com insertion cloudtlare.com replacement cloudvflare.com insertion cloudxflare.com insertion cloufflare.com bitsquatting clouflare.com omission cloulflare.com bitsquatting clourflare.com replacement clousflare.com replacement cloutflare.com bitsquatting clouudflare.com repetition clowdflare.com bitsquatting cloydflare.com replacement clpudflare.com replacement cludflare.com omission cmoudflare.com bitsquatting cnoudflare.com bitsquatting coudflare.com omission dloudflare.com homoglyph doudflare.com homoglyph gloudflare.com bitsquatting kloudflare.com bitsquatting loudflare.com omission sloudflare.com bitsquatting xn--clodflare-is7d.com homoglyph xn--cloudflae-7fe.com homoglyph xn--cloudflae-7n6d.com homoglyph xn--cloudflar-3f7d.com homoglyph xn--cloudflar-j4a.com homoglyph xn--cloudflre-676d.com homoglyph xn--clouflare-t05d.com homoglyph xn--cludflare-6x3d.com homoglyph xn--cludflare-ml7d.com homoglyph xn--coudflare-0sb.com homoglyph aloudflare.com bitsquatting bloudflare.com bitsquatting cdoudflare.com bitsquatting choudflare.com bitsquatting clgudflare.com bitsquatting clkudflare.com bitsquatting clmudflare.com bitsquatting clnudflare.com bitsquatting

Showing 100 of 142

Community records

Retained community reports and observations

Community intelligence

2 community reports

CategoryPHISHING

The PhishFort Detection System has flagged this as a domain threat, classified as phishing. Associated tags: brand impersonation. Threat detected at 2024-01-20T10:06:36.429Z.

Evidence & investigation tools

Original reports, independent checks and evidence links

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 16 det. ChainPatrol ChainAbuse 2 reports URLQuery 1 threat alert Scamadviser 80 trust SSL Labs Hostname coverage not recorded CF Radar Open report OTX 4 refs WOT Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Third-Party Detection — ChainAbuse
2 reports filed for poncakeswap.finance · category: Phishing · source checked
Flagged by PhishFort Detection System on Jan 20, 2024 — automated submission, not a user testimony. Source: ChainAbuse (TRM Labs).
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20260831-32742F Recipient: abuse@dynadot.com
Page title stored with report: CloudFlare - Verify that you are a human
PDF notice generated Notice text archived (291 chars)
Abuse notice text as sent to the provider 
Registrar: Dynadot LLC / Dynadot Inc (United States)
Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains
Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

7 evidence signal groups linked 1 stored notification records Last known active
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.

Immediate steps Find reporting contacts
Official reporting routes
PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 →
Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

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 poncakeswap.finance)
  • 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)
  • Europol — European cybercrime reporting (EU)
  • 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

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
Read the evidence in context

About This Report: poncakeswap.finance

Stored evidence snapshot. Source timestamps appear where available.

Captured title: “CloudFlare - Verify that you are a human”. Apparent target: Cloudflare.

VirusTotal detections for poncakeswap.finance: 16 (2026-09-12 02:16:24 UTC).

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

submit an appeal or review the FAQ page.

Embed this report

A compact widget with a link to the evidence

HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/poncakeswap.finance"
  title="PhishDestroy threat report for poncakeswap.finance"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>