Skip to security report
vote-proposal-3.pages.dev favicon
Domain security and threat intelligence

vote-proposal-3.pages.dev

I was scammed — help me write a report
Share / download report
Post on X Send in Telegram Check via API
In short

PhishDestroy first recorded vote-proposal-3.pages.dev on 2026-11-22. Listed by external blocklists: ScamSniffer.

Page title: “The Blockchain for Trading | Sei”

More about the sources
Recorded security signals

Listed by external blocklists: ScamSniffer. Use caution — do not enter credentials or personal information.

Stored blocklist matches: 1
Registrar
United StatesCloudflare
Resolved IP
Canada172.66.44.87Cloudflare, Inc. · CDN
First seen by PhishDestroy
2026-11-22
Page captures
open gallery
2026-11-22 CDN

Risk score, higher = worse · How this score works

What to do right now

Pick what happened and tick the steps as you go. The ticks are kept only in this browser.

Entered a password0/3
Paid or entered card or bank details0/2
Downloaded a file0/2
Shared a seed phrase or private key0/3
Approved token spending (approve / permit)0/3
Connected a wallet but signed nothing0/2
Sent crypto0/3
Write a police report

Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.

Analysis

Domain summary

PhishDestroy first recorded vote-proposal-3.pages.dev on 2026-11-22. Listed by external blocklists: ScamSniffer. Risk: high (evidence score 65/100). Registrar: Cloudflare. Status: Last known active. Hosting: Cloudflare, Inc. Do not enter credentials or connect a wallet.

High
Status
Last known active
Blocklist matches
1 external + PhishDestroy list
Hosting
Canada172.66.44.87Cloudflare, Inc. · CDN
Registrar
United StatesCloudflare
Page captures
3

Recorded source summary

vote-proposal-3.pages.dev is a tenant hostname on Cloudflare, not a separately registered domain. PhishDestroy first observed the hostname on Nov 22, 2026. Stored content metadata identifies Sei as the apparent target. The captured page title is “The Blockchain for Trading | Sei”. Current evidence score: 65/100 (high).

One source contains a positive finding: ScamSniffer. ScamSniffer listed the hostname in the separate external-blocklist snapshot on Nov 22, 2026 at 11:20 UTC. Additional recorded evidence: VirusTotal recorded 0 detections among 92 engines on Nov 17, 2026 at 21:45 UTC.

HTTP 200 was recorded on Nov 22, 2026 at 11:17 UTC. Cloudflare is the hosting platform for this tenant, not its registrar. At collection time, the hostname resolved to 172.66.44.87 on AS13335 (Cloudflare, Inc.). The IP and ASN identify shared Cloudflare infrastructure, not the tenant operator. The evidence archive retains 3 visual captures from PhishDestroy, URLScan, and Cloudflare Radar. The platform TLS certificate was issued by YE2 with validity through Feb 8, 2027.

Stored content provides classification context alongside the positive source finding. The target field identifies Sei.

Source evidence 2 sources

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
VirusTotalOriginal source recordObserved: 12 fields
Open complete records
Website checksOriginal source recordRetrieved: 23 fields

Mail configuration

SPF lookups
0

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Page title and metadata

Open Graph URL
https://www.sei.io
Page title
The Blockchain for Trading | Sei
Indexing directives
index, follow
Open Graph image
https://www.sei.io/opengraph-image.jpg
Open Graph title
The Blockchain for Trading | Sei
Description
Sei is designed for the world's most demanding markets, trusted by the global firms, funds, and infrastructure providers that drive modern finance
Twitter card
summary
Open Graph description
Sei is designed for the world's most demanding markets, trusted by the global firms, funds, and infrastructure providers that drive modern finance

Trackers

Requests
3

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
0
Waiting
121
Download
2146
Response time, ms
2304

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443
  • 8080

Carbon estimate

Bytes
9255520
CO₂, grams
0.3385
Cleaner than, %
1

DNS servers

Nameservers
  • IP address
    162.159.38.68
    Host
    addyson.ns.cloudflare.com
  • IP address
    108.162.195.120
    Host
    amos.ns.cloudflare.com
DNS zone
vote-proposal-3.pages.dev

Page quality

Layout shift (CLS)
0
SEO score
83
Speed Index, s
33.23
First Contentful Paint (FCP), s
33.23
Largest Contentful Paint (LCP), s
33.33
Total Blocking Time (TBT), ms
287
Performance score
49
Accessibility score
91
Best practices score
92

Location

IP address
2606:4700:310c::ac42:2fa9
ASN
13335
Organization
Cloudflare, Inc.
City
Montreal
Country
CA

TLS certificate

Subject alternative names
  • *.vote-proposal-3.pages.dev
  • vote-proposal-3.pages.dev
Key size, bits
256
Certificate chain
  • vote-proposal-3.pages.dev
  • YE2
  • Root YE
  • ISRG Root X2
  • ISRG Root X1
Issuer
Let's Encrypt / YE2
Serial
053F8FE20D19643911D0C0D1673E89B4E719
SHA-256
05693417d1cf149f79ed9cfe289254e2a04b2bcb44677f1ddacf9e91ba2342eb
Subject
vote-proposal-3.pages.dev
Valid until
Valid from

DNS records

A
  • 172.66.44.87
  • 172.66.47.169
NS
  • addyson.ns.cloudflare.com
  • amos.ns.cloudflare.com
SOA
Primary nameserver
addyson.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2419821621
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800
AAAA
  • 2606:4700:310c::ac42:2fa9
  • 2606:4700:310c::ac42:2c57

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

HTTP security policies

X-Frame-Options
No
Referrer-Policy
strict-origin-when-cross-origin
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
nosniff
Content-Security-Policy
No
Strict-Transport-Security
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2606:4700:310c::ac42:2fa9
IP version
6

Redirects

Redirect chain
  • https://vote-proposal-3.pages.dev

Technology stack

Technologies
  • Tailwind CSS
  • PayPal
  • HSTS
  • Google Tag Manager
  • Priority Hints
  • Cloudflare
  • Open Graph
  • HTTP/3

Page links

External link addresses
  • https://dashboard.sei.io/
  • https://www.sei.io/
  • https://www.sei.io/ecosystem
  • https://docs.sei.io/
  • https://blog.sei.io/research/autobahn-sei-gigas-multi-proposer-approach-to-blockchain-consensus/
  • https://blog.sei.io/
  • https://seiresearch.io/articles/autobahn-sei-giga-s-multi-proposer-approach-to-blockchain-consensus
  • https://blog.sei.io/sei-labs-publishes-whitepaper-for-sei-giga-the-first-multi-proposer-evm-layer-1-blockchain/
  • https://t.me/+KZdhZ1eE-G01NmZk
  • https://www.seifdn.org/
  • https://blog.sei.io/announcements/toku-launches-sei-native-stablecoin-payroll/
  • https://blog.sei.io/introducing-the-us-based-sei-development-foundation/
  • https://seiresearch.io/articles/the-generations-of-consensus-from-safety-first-to-instant-finality
  • https://fortune.com/2025/04/01/23andme-for-sale-interested-buyers-nucleus-sei-foundation/
  • https://dashboard.sei.io/bridge
  • https://coinmarketcap.com/currencies/sei/
  • https://www.seifdn.org/blog/the-sdf-manifesto-innovation-on-the-endless-frontier
  • https://www.seifdn.org/blog/introducing-the-us-based-sei-development-foundation
  • https://x.com/CryptoAmerica_
  • https://jobs.ashbyhq.com/seifoundation
  • https://www.seilabs.io/
  • https://github.com/sei-protocol/sei-chain/blob/main/whitepaper/Sei_Giga.pdf
  • https://seiresearch.io/
  • https://www.0xmonaco.com/
  • https://jobs.ashbyhq.com/sei-labs
External links
34

HTTP headers

Response headers
Server
cloudflare
Content-Type
text/html; charset=utf-8
X-Content-Type-Options
nosniff
Referrer-Policy
strict-origin-when-cross-origin
Original source fields · JSON
Mail configuration
Spf lookups: 0
Protective DNS results
Resolvers: 12; Blocked count: 0
Page title and metadata
Ogurl: https://www.sei.io; Title: The Blockchain for Trading | Sei; Robots: index, follow; Ogimage: https://www.sei.io/opengraph-image.jpg; Ogtitle: The Blockchain for Trading | Sei; Description: Sei is designed for the world's most demanding markets, trusted by the global firms, funds, and infrastructure providers that drive modern finance; Twittercard: summary; Ogdescription: Sei is designed for the world's most demanding markets, trusted by the global firms, funds, and infrastructure providers that drive modern finance
Trackers
Requests: 3
Forms and mixed content
Third party scripts: 0
Status
Up: ✓; Code: 200; Timings: DNS: 0; Wait: 121; Download: 2146; Response ms: 2304
TLS connection
Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 80, 443, 8080
Carbon
Bytes: 9255520; Co2 grams: 0.3385; Cleaner than: 1
DNS server
NS: (IP: 162.159.38.68; Host: addyson.ns.cloudflare.com), (IP: 108.162.195.120; Host: amos.ns.cloudflare.com); Zone: vote-proposal-3.pages.dev
Quality
Cls: 0; Seo: 83; Si s: 33.23; Fcp s: 33.23; Lcp s: 33.33; Tbt ms: 287; Performance: 49; Accessibility: 91; Best practices: 92
Location
IP: 2606:4700:310c::ac42:2fa9; ASN: 13335; Org: Cloudflare, Inc.; City: Montreal; Country: CA
SSL
San: *.vote-proposal-3.pages.dev, vote-proposal-3.pages.dev; Bits: 256; Chain: vote-proposal-3.pages.dev, YE2, Root YE, ISRG Root X2, ISRG Root X1; Issuer: Let's Encrypt / YE2; Serial: 053F8FE20D19643911D0C0D1673E89B4E719; SHA256: 05693417d1cf149f79ed9cfe289254e2a04b2bcb44677f1ddacf9e91ba2342eb; Subject: vote-proposal-3.pages.dev; Valid to: 2027-02-08T17:39:54Z; Valid from: 2026-11-10T17:39:55Z
DNS records
A: 172.66.44.87, 172.66.47.169; NS: addyson.ns.cloudflare.com, amos.ns.cloudflare.com; Soa: Nsname: addyson.ns.cloudflare.com; Hostmaster: dns.cloudflare.com; Serial: 2419821621; Refresh: 10000; Retry: 2400; Expire: 604800; Minttl: 1800; Aaaa: 2606:4700:310c::ac42:2fa9, 2606:4700:310c::ac42:2c57
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Hsts
Message: Site does not serve any HSTS headers.
HTTP security policies
Xframeoptions: ✗; Referrerpolicy: strict-origin-when-cross-origin; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: nosniff; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Firewall
Waf: Cloudflare; Has waf: ✓
Get IP
IP: 2606:4700:310c::ac42:2fa9; Family: 6
Redirects
Chain: https://vote-proposal-3.pages.dev
Tech stack
Technologies: Tailwind CSS, PayPal, HSTS, Google Tag Manager, Priority Hints, Cloudflare, Open Graph, HTTP/3
Page links
External: https://dashboard.sei.io/, https://www.sei.io/, https://www.sei.io/ecosystem, https://docs.sei.io/, https://blog.sei.io/research/autobahn-sei-gigas-multi-proposer-approach-to-blockchain-consensus/, https://blog.sei.io/, https://seiresearch.io/articles/autobahn-sei-giga-s-multi-proposer-approach-to-blockchain-consensus, https://blog.sei.io/sei-labs-publishes-whitepaper-for-sei-giga-the-first-multi-proposer-evm-layer-1-blockchain/, https://t.me/+KZdhZ1eE-G01NmZk, https://www.seifdn.org/, https://blog.sei.io/announcements/toku-launches-sei-native-stablecoin-payroll/, https://blog.sei.io/introducing-the-us-based-sei-development-foundation/, https://seiresearch.io/articles/the-generations-of-consensus-from-safety-first-to-instant-finality, https://fortune.com/2025/04/01/23andme-for-sale-interested-buyers-nucleus-sei-foundation/, https://dashboard.sei.io/bridge, https://coinmarketcap.com/currencies/sei/, https://www.seifdn.org/blog/the-sdf-manifesto-innovation-on-the-endless-frontier, https://www.seifdn.org/blog/introducing-the-us-based-sei-development-foundation, https://x.com/CryptoAmerica_, https://jobs.ashbyhq.com/seifoundation, https://www.seilabs.io/, https://github.com/sei-protocol/sei-chain/blob/main/whitepaper/Sei_Giga.pdf, https://seiresearch.io/, https://www.0xmonaco.com/, https://jobs.ashbyhq.com/sei-labs; External count: 34
HTTP headers
Headers: Server: cloudflare; Content type: text/html; charset=utf-8; X content type options: nosniff; Referrer policy: strict-origin-when-cross-origin

Questions about vote-proposal-3.pages.dev

Is vote-proposal-3.pages.dev legit?

PhishDestroy rates vote-proposal-3.pages.dev as high risk (evidence score 65/100) from the recorded evidence; it was first recorded on 2026-11-22. Listed by external blocklists: ScamSniffer. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is vote-proposal-3.pages.dev safe to connect a wallet?

Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on vote-proposal-3.pages.dev. A confirmed blockchain transaction cannot be reversed.

What should I do if I used vote-proposal-3.pages.dev?

  • 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.

Explore

Blocklist matches1 external + PhishDestroy list · ScamSniffer · PhishDestroy 1
ScamSniffer Listed View source
PhishDestroy PhishDestroy list View source

Last checked

Page captures (3)

All capture links and hashes (3)

Domain details

Domain
IP Context Canada172.66.44.87 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider Cloudflare US(US)
HTTP Status200
Technical detailsProvenance & timestamps
First Detected2026-11-22
Submitted URLhttp://vote-proposal-3.pages.dev/
Favicon Hash
Observed page title
The Blockchain for Trading | Sei
TLS Certificate
Issued by YE2 · stored validity ends in 78 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Canada172.66.44.87
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
CanadaToronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • adi.ns.cloudflare.com
  • karl.ns.cloudflare.com

SOA

  • nsname: addyson.ns.cloudflare.com
  • hostmaster: dns.cloudflare.com
  • serial: 2419821621
  • refresh: 10000
  • retry: 2400
  • expire: 604800
  • minttl: 1800

Location describes the IP network.

TLS certificate

Issuer
YE2
Valid from
2026-11-10 17:39:55
Valid until
2027-02-08 17:39:54
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint05693417d1cf149f79ed9cfe289254e2a04b2bcb44677f1ddacf9e91ba2342eb
Certificate names · 2 SANs
  • *.vote-proposal-3.pages.dev
  • vote-proposal-3.pages.dev

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

Technologies · 4 identified
Open complete records
PageSpeed (mobile): 49

Google PageSpeed Insights — mobile performance audit of vote-proposal-3.pages.dev ·

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

Availability observations

Last reachable observation

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

All stored data89
Open complete records

Captured network requests

Network requests: 89 SHA-256 hashes: 60 URLScan scan:

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-11-22 11:18 UTC.

Open this scan on URLScan 01a202f8-f7db-711e-ae99-975d3e7669ee ↗

Stored observation history1

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

  1. Domain monitor · First collection record

    Reachable

All retained availability observations2

Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.

  1. Current state backfill
    Observation source
    Current state backfill
    Cause
    Http 2xx unclassified
    DNS state
    stale
    Recorded HTTP status
    200
    Monitor confidence
    40
    Provider action verified
    ✗
    Registrar mechanism verified
    ✗
    Linked to a report
    ✗
    Original source timestamp
    2026-11-22 12:17:56.000000
    Evidence SHA-256
    3bfaacc30b89e04fd50ed16565a75ef75b9df3da35d34d4282155548dcb1b6c8
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-22 12:17:56
  2. Http observation
    Observation source
    Http observation
    Cause
    Http 2xx unclassified
    Recorded HTTP status
    200
    Monitor confidence
    40
    Provider action verified
    ✗
    Registrar mechanism verified
    ✗
    Linked to a report
    ✗
    Original source timestamp
    2026-11-22 12:17:56.000000
    Evidence SHA-256
    3bfaacc30b89e04fd50ed16565a75ef75b9df3da35d34d4282155548dcb1b6c8
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-22 12:17:56

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · in progress

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

Pre-emptive Discovery & IngestionThreat Ingested recorded
  • Threat Ingested
    vote-proposal-3.pages.dev detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Blocklist Detection · Automated brand label: Sei · Forensic Evidence Collected · Technical Analysis Recorded recorded
Publication & AvailabilityDestroyList Published · Monitoring Continues ongoing
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.
    ongoing

Recorded activity

2 entries

Lifecycle

  1. Domain registered
  2. Added to PhishDestroy+2272 d 8 h
  1. Added to PhishDestroy

    vote-proposal-3.pages.dev

    same minute
  2. URLScan

    Page captured

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.

All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

vote-proposal-3.pages.dev

Evidence & External Reports

Deep Analysis

Were You Affected by This Site?

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.

Where to report

The draft stays only with you.

First secure your money: call your bank or revoke wallet approvals. Immediate steps →

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

Emergency help from security researchers when a crypto wallet is being drained right now.

FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

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.

  • 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 vote-proposal-3.pages.dev)
  • 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

Stay Informed, Stay Safe

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

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.

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.

Embed this reportA 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/vote-proposal-3.pages.dev"
  title="PhishDestroy threat report for vote-proposal-3.pages.dev"
  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>