Skip to security report
whatsappz.top favicon
Domain security and threat intelligence

whatsappz.top

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 whatsappz.top on 2026-11-22. Stored VirusTotal result: 14/92 engines flagged. Analysis time (as stored): 2026-11-20 22:02 UTC. Retrieved (as stored): 2026-11-22 10:35 UTC.

Page title: “页面跳转中...”

More about the sources
Recorded security signals

Stored VirusTotal result: 14/92 engines flagged. Analysis time (as stored): 2026-11-20 22:02 UTC. Retrieved (as stored): 2026-11-22 10:35 UTC. Use caution — do not enter credentials or personal information.

VirusTotal detections: 14/92 Young domain: 3 days old
Registrar
SwedenNameMart
Resolved IP
Hong Kong SAR China223.26.62.215CTG Server Limited
Registered
2026-11-19
First seen by PhishDestroy
2026-11-22
URLQuery
detections
OTX
community references
Page captures
open gallery
Reports sent
view timeline
OTX: 25 refs 2026-11-22 1 Report Sent

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 whatsappz.top on 2026-11-22. Stored VirusTotal result: 14/92 engines flagged. Analysis time (as stored): 2026-11-20 22:02 UTC. Retrieved (as stored): 2026-11-22 10:35 UTC. Risk: critical (evidence score 100/100). Registrar: NameMart. Status: Last known active. Hosting: CTG Server Limited. PhishDestroy sent 1 abuse report. Do not enter credentials or connect a wallet.

Critical
Status
Last known active
VirusTotal
14 / 92
Hosting
Hong Kong SAR China223.26.62.215CTG Server Limited
Registrar
SwedenNameMart
Registered
2026-11-19
OTX
25 community refs
Page captures
2

Recorded source summary

PhishDestroy first observed whatsappz.top on Nov 22, 2026. The captured page title is “页面跳转中...”. Current evidence score: 100/100 (critical).

Positive findings are stored from 2 sources: VirusTotal and URLQuery. VirusTotal recorded 14 detections among 92 engines: VIPRE, G-Data, Lionic, Sophos, Certego, CyRadar, Webroot, Fortinet, Kaspersky, BitDefender, Criminal IP, Chong Lua Dao, alphaMountain.ai, Forcepoint ThreatSeeker on Nov 20, 2026 at 22:02 UTC. URLQuery recorded 3 detections; no observation timestamp was retained. Additional recorded evidence: AlienVault OTX listed 25 community pulse references (not vendor detections) on Nov 22, 2026 at 10:35 UTC.

HTTP 200 was recorded on Nov 22, 2026 at 10:34 UTC. Registration records for the domain list NameMart Pte. Ltd. as the registrar and Sep 4, 2008 as the creation date. At collection time, the hostname resolved to 223.26.62.215 on AS152194 (CTG Server Limited). The recorded endpoint location is Hung Hom, HK. The stored server header is nginx. The evidence archive retains 2 visual captures from PhishDestroy and Cloudflare Radar. TLS metadata lists YR1 as the certificate issuer with validity through Feb 17, 2027.

The content indicators and 2 positive source findings support the current phishing classification.

Source evidenceVirusTotal 14 / 92 · OTX 25 references 5 sources

VirusTotal

14 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 14 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
14
Denominator
92
Vendors
Criminal IP, alphaMountain.ai, BitDefender, Certego, Chong Lua Dao, CyRadar, Forcepoint ThreatSeeker, Fortinet, G-Data, Kaspersky, Lionic, Sophos, VIPRE, Webroot
Observed at
2026-11-20 22:02:50
Checked at
2026-11-22 11:35:15
Fetched at
2026-11-22 10:35:16

OTX

25 community references

Open report

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: 24 fields

Mail configuration

SPF lookups
0

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Web archive observations

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

Page title and metadata

Page title
页面跳转中...

Trackers

Requests
11

Forms and mixed content

Scripts without SRI
  • https://tj.whastapps.cc/tj.js
Third-party scripts
1

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
0
Waiting
743
Download
0
Response time, ms
1378

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
  • 22
  • 80
  • 443
  • 3306

Carbon estimate

Bytes
349
CO₂, grams
0
Cleaner than, %
95

DNS servers

Nameservers
  • IP address
    38.114.114.183
    Host
    ns2.domainnamedns.com
  • IP address
    216.106.185.75
    Host
    ns1.domainnamedns.com
  • IP address
    67.220.72.51
    Host
    ns4.domainnamedns.com
  • IP address
    54.151.142.119
    Host
    ns3.domainnamedns.com
DNS zone
whatsappz.top

Page quality

Layout shift (CLS)
0.002
SEO score
66
Speed Index, s
5.07
First Contentful Paint (FCP), s
4.23
Largest Contentful Paint (LCP), s
4.23
Total Blocking Time (TBT), ms
0
Performance score
74
Accessibility score
93
Best practices score
58

Cookies

Cookies
  • Name
    wa_ul
    Secure
    Yes
    HTTP-only
    Yes
    SameSite
    Lax
  • Name
    wa_lang_pref
    Secure
    Yes
    SameSite
    Lax

Location

IP address
223.26.62.215
ASN
152194
Organization
CTG Server Limited
City
Hung Hom
Country
HK

TLS certificate

Subject alternative names
  • whatsappz.top
  • www.whatsappz.top
Key size, bits
2048
Certificate chain
  • www.whatsappz.top
  • YR1
  • Root YR
  • ISRG Root X1
Issuer
Let's Encrypt / YR1
Serial
0615EFF12394AB77CE7D53C4C80C421F3058
SHA-256
18e5e6fe34e83496a4e7d2499fae4add287578a2ca128a80568f42757d89b377
Subject
www.whatsappz.top
Valid until
Valid from

DNS records

A
  • 223.26.62.215
NS
  • ns1.domainnamedns.com
  • ns4.domainnamedns.com
  • ns3.domainnamedns.com
  • ns2.domainnamedns.com
SOA
Primary nameserver
ns1.domainnamedns.com
Hostmaster
support.namens.net
Serial
1795073241
Refresh, seconds
3600
Retry, seconds
1800
Expiry, seconds
1209600
Minimum TTL, seconds
180

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=31536000
Observation
HSTS header does not include all subdomains.

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=31536000
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
223.26.62.215
IP version
4

Redirects

Redirect chain
  • https://whatsappz.top

Subdomains

Count
1
Subdomains
  • www.whatsappz.top

Registration record

Registrar
NameMart Pte. Ltd.
Registrar IANA ID
4162
Registrar URL
http://www.namemart.com
Registered
Expires
Status
  • ok https://icann.org/epp
  • addPeriod https://icann.org/epp
Nameservers
  • ns1.domainnamedns.com
  • ns2.domainnamedns.com
DNSSEC
unsigned

HTTP headers

Response headers
Server
nginx
Content-Type
text/html
Strict-Transport-Security
max-age=31536000
Original source fields · JSON
Mail configuration
Spf lookups: 0
Protective DNS results
Resolvers: 12; Blocked count: 0
Web archive observations
Last: 2026-11-22T10:35:52Z; First: 2026-11-22T10:35:52Z; Changes: 0; Days archived: 1; Avg page bytes: 843
Page title and metadata
Title: 页面跳转中...
Trackers
Requests: 11
Forms and mixed content
No sri: https://tj.whastapps.cc/tj.js; Third party scripts: 1
Status
Up: ✓; Code: 200; Timings: DNS: 0; Wait: 743; Download: 0; Response ms: 1378
TLS connection
Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 22, 80, 443, 3306
Carbon
Bytes: 349; Co2 grams: 0; Cleaner than: 95
DNS server
NS: (IP: 38.114.114.183; Host: ns2.domainnamedns.com), (IP: 216.106.185.75; Host: ns1.domainnamedns.com), (IP: 67.220.72.51; Host: ns4.domainnamedns.com), (IP: 54.151.142.119; Host: ns3.domainnamedns.com); Zone: whatsappz.top
Quality
Cls: 0.002; Seo: 66; Si s: 5.07; Fcp s: 4.23; Lcp s: 4.23; Tbt ms: 0; Performance: 74; Accessibility: 93; Best practices: 58
Cookies
Cookies: (Name: Wa ul; Secure: ✓; HTTP only: ✓; Same site: Lax), (Name: Wa lang pref; Secure: ✓; Same site: Lax)
Location
IP: 223.26.62.215; ASN: 152194; Org: CTG Server Limited; City: Hung Hom; Country: HK
SSL
San: whatsappz.top, www.whatsappz.top; Bits: 2048; Chain: www.whatsappz.top, YR1, Root YR, ISRG Root X1; Issuer: Let's Encrypt / YR1; Serial: 0615EFF12394AB77CE7D53C4C80C421F3058; SHA256: 18e5e6fe34e83496a4e7d2499fae4add287578a2ca128a80568f42757d89b377; Subject: www.whatsappz.top; Valid to: 2027-02-17T06:43:37Z; Valid from: 2026-11-19T06:43:38Z
DNS records
A: 223.26.62.215; NS: ns1.domainnamedns.com, ns4.domainnamedns.com, ns3.domainnamedns.com, ns2.domainnamedns.com; Soa: Nsname: ns1.domainnamedns.com; Hostmaster: support.namens.net; Serial: 1795073241; Refresh: 3600; Retry: 1800; Expire: 1209600; Minttl: 180
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Hsts
Header: max-age=31536000; Message: HSTS header does not include all subdomains.
HTTP security policies
Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: ✗; Stricttransportpolicy: max-age=31536000; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Get IP
IP: 223.26.62.215; Family: 4
Redirects
Chain: https://whatsappz.top
Subdomains
Count: 1; Subdomains: www.whatsappz.top
Registration record
Registrar: NameMart Pte. Ltd.; Registrar iana ID: 4162; Registrar URL: http://www.namemart.com; Created: 2026-11-19T07:24:00Z; Expires: 2027-11-19T07:24:00Z; Status: ok https://icann.org/epp, addPeriod https://icann.org/epp; Nameservers: ns1.domainnamedns.com, ns2.domainnamedns.com; Dnssec: unsigned
HTTP headers
Headers: Server: nginx; Content type: text/html; Strict transport security: max-age=31536000

Questions about whatsappz.top

Is whatsappz.top legit?

PhishDestroy rates whatsappz.top as critical risk (evidence score 100/100) from the recorded evidence; it was first recorded on 2026-11-22. Stored VirusTotal result: 14/92 engines flagged. Analysis time (as stored): 2026-11-20 22:02 UTC. Retrieved (as stored): 2026-11-22 10:35 UTC. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is whatsappz.top safe to connect a wallet?

Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on whatsappz.top. A confirmed blockchain transaction cannot be reversed.

What should I do if I used whatsappz.top?

  • 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 (2)

All capture links and hashes (2)
Observed page title
页面跳转中...
TLS Certificate
Issued by YR1 · stored validity ends in 86 days

Domain details

Domain
OTX tags phishingphishing-databasethreatfox
Registrar NameMart SE(SE)
RegistrationCreated 2026-11-19 (3d · Brand New!) — Expires 2027-11-19
HTTP Status200
Technical detailsProvenance & timestamps
First Detected2026-11-22
Submitted URLhttps://whatsappz.top/
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.

Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
Hong Kong SAR China223.26.62.215
Network ASN
AS152194
Organization
CTG Server Limited
Observed location
Hong Kong SAR ChinaHung Hom, HK
Server header
nginx

Nameservers 4

  • ns1.domainnamedns.com
  • ns2.domainnamedns.com
  • ns3.domainnamedns.com
  • ns4.domainnamedns.com

SOA

  • nsname: ns1.domainnamedns.com
  • hostmaster: support.namens.net
  • serial: 1795073241
  • refresh: 3600
  • retry: 1800
  • expire: 1209600
  • minttl: 180

Location describes the IP network.

TLS certificate

Issuer
YR1
Valid from
2026-11-19 06:43:38
Valid until
2027-02-17 06:43:37
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint18e5e6fe34e83496a4e7d2499fae4add287578a2ca128a80568f42757d89b377
Certificate names · 2 SANs
  • whatsappz.top
  • www.whatsappz.top

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

Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • www.whatsappz.topDomain record

VirusTotal Analysis

14 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive result retrieved by PhishDestroy
VIPRE
G-Data
Lionic
Sophos
Certego
CyRadar
Webroot
Fortinet
Kaspersky
BitDefender
Criminal IP
Chong Lua Dao
alphaMountain.ai
Forcepoint ThreatSeeker

Archived Evidence

Wayback Machine Snapshot
View Archive

Saved snapshots 1

PageSpeed (mobile): 78

Google PageSpeed Insights — mobile performance audit of whatsappz.top ·

78
Needs Work
Performance
FCP
4.02 s
First Contentful Paint
LCP
4.02 s
Largest Contentful Paint
CLS
0.002
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
4.02 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
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: https://whatsappz.top/
页面跳转中...
Response
HTTP 200
HTML body
349 B
Compressed
297 B
Links
0 internal · 0 external
Detected technologies
nginx
Selected response headers
Server: nginx
Content-Type: text/html
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 10
Accept-Ranges
bytes
Alt-Svc
quic=":443"; h3=":443"; h3-29=":443"; h3-27=":443";h3-25=":443"; h3-T050=":443"; h3-Q050=":443";h3-Q049=":443";h3-Q048=":443"; h3-Q046=":443"; h3-Q043=":443"
Connection
keep-alive
Content-Length
349
Content-Type
text/html
Date
Sun, 22 Nov 2026 10:35:32 GMT
Etag
"6b029571-15d"
Last-Modified
Sun, 22 Nov 2026 07:10:41 GMT
Server
nginx
Strict-Transport-Security
max-age=31536000

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

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 data93
Open complete records

Captured network requests

Network requests: 6 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-11-22 10:35 UTC.

Open this scan on URLScan 01a202d1-5a3a-760c-865f-8790e9e2969d ↗

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 11:34:20.000000
    Evidence SHA-256
    81fdf43fd6a09d3e72f166eb7b314b2ad79731bb3c31cf567a40cc2abe23b390
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-22 11:34:20
  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 11:34:20.000000
    Evidence SHA-256
    81fdf43fd6a09d3e72f166eb7b314b2ad79731bb3c31cf567a40cc2abe23b390
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-22 11:34:20

Threat Response Pipeline

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

Recorded events: 10. 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
    whatsappz.top detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · OTX Community References · Forensic Evidence Collected recorded
Notification RecordsSent Report Recorded recorded
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: NameMart Pte. Ltd.. Abuse contacts: 1.
    • abuse@namemart.com
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

6 entries

Lifecycle

  1. Domain registered
  2. VirusTotal analysis with detections+38 h 38 min
  3. Added to PhishDestroy+36 h 31 min
  4. First abuse report sent+6 min

Reported 3 d 3 h after registration

  1. Abuse report sent

    PD-D6FDD27AABAA12BE342B

    abuse@namemart.com
    +5 min
  2. Wayback Machine

    Page archived

    same minute
  3. AlienVault OTX

    25 community references

    +1 min
  4. Added to PhishDestroy

    whatsappz.top

    same minute
  5. URLScan

    Page captured

    +36 h 31 min
  6. VirusTotal

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

whatsappz.top

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-D6FDD27AABAA12BE342B Recipient: abuse@namemart.com
Page title stored with report: Share on WhatsApp
PDF notice generated
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 whatsappz.top)
  • 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/whatsappz.top"
  title="PhishDestroy threat report for whatsappz.top"
  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>