Skip to security report
Dangerous

Phishing copy of Microsoft

20000k.vercel.app favicon
Domain security and threat intelligence

20000k.vercel.app

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

On 2026-10-28, 20000k.vercel.app displayed a page presenting Microsoft branding, including the Microsoft logo and a footer reading © 2026 Microsoft with Privacy & Cookies and Terms of use links. The centered card is headed "Security verification" with the subtitle "Continue to account settings" and shows a location line reading Boston, United States alongside an IP address.

Page title: “Security verification - Microsoft account”

More about the sources
Recorded security signals

Stored VirusTotal result: 4/92 engines flagged. Analysis time (as stored): 2026-10-28 12:09 UTC. Retrieved (as stored): 2026-10-29 01:22 UTC. Use caution — do not enter credentials or personal information.

VirusTotal detections: 4/92 Last known active Google Safe Browsing: threat flag recorded
Resolved IP
United States216.198.79.195Amazon.com, Inc. · CDN
First seen by PhishDestroy
2026-10-29
Page captures
open gallery
2026-10-29 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 20000k.vercel.app on 2026-10-29. Stored VirusTotal result: 4/92 engines flagged. Analysis time (as stored): 2026-10-28 12:09 UTC. Retrieved (as stored): 2026-10-29 01:22 UTC. Google Safe Browsing flags it. Risk: critical (evidence score 100/100). Status: Reachable · access restricted. Hosting: Amazon.com, Inc. Do not enter credentials or connect a wallet.

Critical
Status
Reachable · access restricted
VirusTotal
4 / 92
Scam type (automated label)
Impersonation
Hosting
United States216.198.79.195Amazon.com, Inc. · CDN
Page captures
8

URLScan capture · 2026-10-28 16:30 UTC · SHA-256 d8a07849…f35ee97

PhishDestroy analysis, reviewed version

On 2026-10-28, 20000k.vercel.app displayed a page presenting Microsoft branding, including the Microsoft logo and a footer reading © 2026 Microsoft with Privacy & Cookies and Terms of use links. The centered card is headed "Security verification" with the subtitle "Continue to account settings" and shows a location line reading Boston, United States alongside an IP address.

The form provides a field labeled "Email, phone, or Skype" with the placeholder someone@example.com, plus links for "No account? Create one!" and "Can't access your account?" A blue "Next" button sits below the field. These are visible page elements and branding claims; no affiliation or current behavior is established by this capture.

Source evidenceVirusTotal 4 / 92 · Google Safe Browsing: flagged 5 sources

VirusTotal

4 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 13 fields
Separate collector summary

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.

Source
VirusTotal
Result state
observed
Numerator
20
Denominator
92
Vendors
alphaMountain.ai, BitDefender, Ermes, ESET, Emsisoft, Forcepoint ThreatSeeker, Fortinet, G-Data, Google Safe Browsing, Gridinsoft, Kaspersky, LevelBlue, Lionic, MalwareURL, Netcraft, SOCRadar, Sophos, URLQuery, VIPRE, Webroot
Checked at
2026-11-05 04:05:51
Fetched at
2026-11-05 03:05:52

Google Safe Browsing

Threat flag recorded

Open report

URLScan

Malicious

SHA-256 ff3f3412…eb8850c

Open report
URLScanOriginal source recordObserved: 20 fields
Separate monitor record · 2026-10-29 04:30 UTC

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

UUID
01a18521-cdf6-7063-9a5c-45fad0108650
Score
100
Malicious
✓
Result at
2026-10-29T04:30:19Z
Enriched at
2026-10-29T09:13:35Z
Source timestamps
Urlscan result at: 2026-10-29 05:30:19; Urlscan enriched at: 2026-10-29 10:13:35

PhishDestroy DOM

40 / 100 · heuristic score · 1 brand reference · 1 classification

Content heuristic only; not the final score

Open report
Page code check by a separate monitor · 40 / 100 · 2026-10-29 03:20 UTC

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

Heuristic score
40
Analyzed at
2026-10-29T03:20:24Z
Source timestamp
2026-10-29 04:20:24
Technical metadata

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

AI title
20000k.vercel.app: Microsoft-branded security verification sign-in form
AI description
PhishDestroy records that 20000k.vercel.app displays a Microsoft-branded security verification page with an email, phone, or Skype sign-in field and a Next button.
AI summary
On 2026-10-28, 20000k.vercel.app displayed a page presenting Microsoft branding, including the Microsoft logo and a footer reading © 2026 Microsoft with Privacy & Cookies and Terms of use links. The centered card is headed "Security verification" with the subtitle "Continue to account settings" and shows a location line reading Boston, United States alongside an IP address. The form provides a field labeled "Email, phone, or Skype" with the placeholder someone@example.com, plus links for "No account? Create one!" and "Can't access your account?" A blue "Next" button sits below the field. These are visible page elements and branding claims; no affiliation or current behavior is established by this capture.
AI generated by
threat-v6-mimo
AI generated at
2026-11-12T09:01:25Z
Revision
03a1c9fd66b6e5a468e028800bf55476f80b552a586f40588d201728713f1390
Mode
reviewed
Interpretation
Selected public package; text generation time is separate from source observation dates.

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
Website checksOriginal source recordRetrieved: 21 fields

Mail configuration

SPF lookups
0

CAA records

Count
2
Domain
vercel.app
Allowed issuers
  • pki.goog
  • letsencrypt.org

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
5492

Page title and metadata

Page title
Security verification - Microsoft account

Trackers

Requests
6
Observed services
  • Name
    Akamai Technologies
    Company
    Akamai Technologies
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    Google APIs
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    1
  • Name
    ipify
    Company
    ipify
    Category
    Misc
    Requests
    1
  • Name
    Microsoft Services
    Company
    Microsoft
    Country
    US
    Category
    Misc
    Requests
    1
  • Name
    ipapi
    Company
    Kloudend
    Country
    US
    Category
    Site Analytics
    Requests
    1

Forms and mixed content

Scripts without SRI
  • https://ajax.googleapis.com/ajax/libs/jquery/3.6.0/jquery.min.js
Third-party scripts
1

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
27
TLS
50
Waiting
60
Connection
6
Download
1
Response time, ms
144

TLS connection

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

Ports

Open ports
  • 80
  • 443

Carbon estimate

Bytes
16021
CO₂, grams
0.0006
Cleaner than, %
62

DNS servers

Nameservers
  • IP address
    205.251.193.92
    Host
    ns1.vercel-dns-3.com
  • IP address
    205.251.194.149
    Host
    ns2.vercel-dns-3.com
  • IP address
    205.251.197.116
    Host
    ns3.vercel-dns-3.com
  • IP address
    205.251.199.60
    Host
    ns4.vercel-dns-3.com
DNS zone
vercel.app

Location

IP address
64.29.17.3
ASN
16509
Organization
Amazon.com, Inc.
City
Walnut
Country
US

TLS certificate

Issuer
Google Trust Services / WR1
Subject
*.vercel.app

DNS records

A
  • 216.198.79.3
  • 64.29.17.3

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=63072000; includeSubDomains; preload
Observation
Site is compatible with the HSTS preload list!
Preload compatible
Yes

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
max-age=63072000; includeSubDomains; preload
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
216.198.79.3
IP version
4

Redirects

Redirect chain
  • https://20000k.vercel.app

HTTP headers

Response headers
Server
Vercel
Content-Type
text/html; charset=utf-8
Strict-Transport-Security
max-age=63072000; includeSubDomains; preload
Original source fields · JSON
Mail configuration
Spf lookups: 0
Caa records
Count: 2; Domain: vercel.app; Issuers: pki.goog, letsencrypt.org
Protective DNS results
Resolvers: 12; Blocked by: CloudFlare Family; Blocked count: 1
Web archive observations
Last: 2026-10-29T00:40:37Z; First: 2026-10-29T00:40:37Z; Changes: 0; Days archived: 1; Avg page bytes: 5492
Page title and metadata
Title: Security verification - Microsoft account
Trackers
Requests: 6; Trackers: (Name: Akamai Technologies; Company: Akamai Technologies; Country: US; Category: Hosting; Requests: 1), (Name: Google APIs; Company: Google; Country: US; Category: Hosting; Requests: 1), (Name: ipify; Company: ipify; Category: Misc; Requests: 1), (Name: Microsoft Services; Company: Microsoft; Country: US; Category: Misc; Requests: 1), (Name: ipapi; Company: Kloudend; Country: US; Category: Site Analytics; Requests: 1)
Forms and mixed content
No sri: https://ajax.googleapis.com/ajax/libs/jquery/3.6.0/jquery.min.js; Third party scripts: 1
Status
Up: ✓; Code: 200; Timings: DNS: 27; TLS: 50; Wait: 60; Connect: 6; Download: 1; Response ms: 144
TLS connection
Alpn: h2; Cipher: TLS_AES_128_GCM_SHA256; Protocol: TLSv1.3; Versions: TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 80, 443
Carbon
Bytes: 16021; Co2 grams: 0.0006; Cleaner than: 62
DNS server
NS: (IP: 205.251.193.92; Host: ns1.vercel-dns-3.com), (IP: 205.251.194.149; Host: ns2.vercel-dns-3.com), (IP: 205.251.197.116; Host: ns3.vercel-dns-3.com), (IP: 205.251.199.60; Host: ns4.vercel-dns-3.com); Zone: vercel.app
Location
IP: 64.29.17.3; ASN: 16509; Org: Amazon.com, Inc.; City: Walnut; Country: US
SSL
Issuer: Google Trust Services / WR1; Subject: *.vercel.app
DNS records
A: 216.198.79.3, 64.29.17.3
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Hsts
Header: max-age=63072000; includeSubDomains; preload; Message: Site is compatible with the HSTS preload list!; Compatible: ✓
HTTP security policies
Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: ✗; Stricttransportpolicy: max-age=63072000; includeSubDomains; preload; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Get IP
IP: 216.198.79.3; Family: 4
Redirects
Chain: https://20000k.vercel.app
HTTP headers
Headers: Server: Vercel; Content type: text/html; charset=utf-8; Strict transport security: max-age=63072000; includeSubDomains; preload

Questions about 20000k.vercel.app

Is 20000k.vercel.app legit?

PhishDestroy rates 20000k.vercel.app as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-10-29. Stored VirusTotal result: 4/92 engines flagged. Analysis time (as stored): 2026-10-28 12:09 UTC. Retrieved (as stored): 2026-10-29 01:22 UTC. Google Safe Browsing flags it. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is 20000k.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 20000k.vercel.app. A confirmed blockchain transaction cannot be reversed.

What should I do if I used 20000k.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.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Page captures (8)

All capture links and hashes (8)
20000k.vercel.app: Phishing site — Flagged by Google Safe Browsing. PhishDestroy risk score 80/100 (critical).
Social preview card 20000k.vercel.app: Phishing site — Flagged by Google Safe Browsing. PhishDestroy risk score 80/100 (critical). v 5c58f8ffa582

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Genericemailbrand: Microsoft report ↗
Google Safe Browsing Flagged Social engineering checked 2026-11-11
IP Context United States216.198.79.195 Vercel shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider vercel.app
Abuse contactabuse@vercel.com
Hosting abuse contact abuse@vercel.com Amazon.com, Inc. · AS16509
HTTP Status451 Unavailable For Legal Reasons
Elapsed Since First Report 24 days
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.
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First Detected2026-10-29
DOM Analysisanalyzed 2026-10-29score 40/1001 brand signal
Submitted URLhttp://20000k.vercel.app/
Favicon Hash
Observed page title
Security verification - Microsoft account
Automated brand references
Microsoft
TLS Certificate
Issued by Google Trust Services / WR1 · stored validity ends in 5 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United States216.198.79.195
Network ASN
AS16509
AS name
AMAZON-02 - Amazon.com, Inc., US
Organization
Amazon.com, Inc.
Observed location
United StatesWalnut, US
Server header
Vercel

Edge-IP reputation is not attributed to this domain.

Nameservers 1

  • ns4.vercel-dns-3.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / 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 fingerprint8f46c4a0a289bfde4060d06986f2af761ee62d668dde972e6bef4687ee4f6093
Certificate 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.

Latest Classified Outcome 2026-11-21 23:29 UTC

The latest check was inconclusive.

Technical details
Primary outcome Provider block observed reason: Vercel Deployment Disabled 95% confidence
Attribution Vercel mechanism: Deployment Disabled source: Current Http Probe
Evidence layers Availability: Provider blocked Content: Provider blocked DNS: Stale
Latest HTTP observation Provider block observed Vercel Deployment Disabled Vercel Deployment Disabled 95% provider marker verified 2026-11-21 23:29 UTC
RDAP registration
Observed timeline last reachable: 2026-11-21 11:33 UTC last content: 2026-11-21 11:33 UTC current episode first observed: 2026-11-21 23:29 UTC observed RIP window: 2026-11-21 11:33 UTC → 2026-11-21 23:29 UTC · 11.93h midpoint estimate ≈ 2026-11-21 17:31 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.

VirusTotal Analysis

4 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive result retrieved by PhishDestroy
DNS8
SOCRadar
Gridinsoft
alphaMountain.ai

Archived Evidence

Wayback Machine Snapshot
View Archive

Saved snapshots 1

Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://20000k.vercel.app/
Final URL: https://20000k.vercel.app/
Security verification - Microsoft account
Response
HTTP 200
HTML body
15.6 KB
Compressed
4.5 KB
Links
0 internal · 0 external
Detected technologies
jquery
Selected response headers
Cache-Control: public, max-age=0, must-revalidate
Content-Encoding: gzip
Content-Type: text/html; charset=utf-8
Server: Vercel
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 14
Access-Control-Allow-Origin
*
Age
132461
Cache-Control
public, max-age=0, must-revalidate
Content-Disposition
inline
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Thu, 29 Oct 2026 00:41:59 GMT
Etag
W/"f239b1174689ac30147c2dbc4e0b97c0"
Last-Modified
Tue, 27 Oct 2026 11:14:16 GMT
Server
Vercel
Strict-Transport-Security
max-age=63072000; includeSubDomains; preload
Transfer-Encoding
chunked
X-Vercel-Cache
HIT
X-Vercel-Id
fra1::zh9w6-1793234519560-7745da1c256e

Values retained by the collector; long values may be shortened during collection.

Registration & observation details9

Availability observations

Last reachable observation
Last content observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
11.93
Estimate basis
Bounded by observations
Estimate precision
Medium

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

All stored data111
Open complete records

Captured network requests

Network requests: 5 SHA-256 hashes: 5 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-10-29 01:52 UTC.

Open this scan on URLScan 01a18521-cdf6-7063-9a5c-45fad0108650 ↗

Stored observation history7

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

    Serving page content→Blocked

    Vercel deployment disabled · Vercel · Deployment disabled

  2. Domain monitor · Recorded state

    Reachable→Unavailable

  3. Availability monitor · Recorded state

    Serving page content

    page content returned

  4. Availability monitor · Recorded state

    Serving page content

    page content returned

  5. Availability monitor · Recorded state

    Serving page content

    page content returned

Earlier observations 2
  1. Google Safe Browsing · Threat flag

    No flag recorded→Flag recorded

  2. Domain monitor · First collection record

    Reachable

All retained availability observations76
Open complete records

Threat Response Pipeline

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

Recorded events: 12. 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
    20000k.vercel.app detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Web Archive · VirusTotal · Google Safe Browsing · Automated brand label: Microsoft · Forensic Evidence Collected · Technical Analysis Recorded · Content Observed Unavailable recorded
Publication & AvailabilityDestroyList Published · Time to First Unavailability · Monitoring Continues ongoing
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Time to First Unavailability
    Hours from detection to the first unavailable observation: 574
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.
    ongoing

Recorded activity

5 entries

Lifecycle

  1. Domain registered
  2. VirusTotal analysis with detections+2465 d 9 h
  3. Added to PhishDestroy+12 h 41 min
  1. Google Safe Browsing

    Threat flag recorded

    +12 d 22 h
  2. Added to PhishDestroy

    20000k.vercel.app

    same minute
  3. URLScan

    Page captured

    +9 min
  4. Wayback Machine

    Page archived

    +12 h 31 min
  5. VirusTotal

    4/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
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.

20000k.vercel.app

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 20000k.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)
  • 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.

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.

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/20000k.vercel.app"
  title="PhishDestroy threat report for 20000k.vercel.app"
  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>