Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 17. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
cn.ember-whatsapp.com favicon

cn.ember-whatsapp.com

In short

cn.ember-whatsapp.com is a WhatsApp impersonation page detected by PhishDestroy on 2026-10-24. Risk: critical (100/100). Registrar: Guizhou Zhongyu Zhike …. Status: Last known active. Hosting: CloudFLARENET-EU. PhishDestroy sent 1 abuse report. VirusTotal: 17/92 engines flag it. Do not enter credentials or connect a wallet.

“Preparing Secure Connection...”

Review the evidence
Registrar
Guizhou Zhongyu Zhike …
Resolved IP
United Kingdom188.114.96.3CloudFLARENET-EU · CDN
Registered
Sep 8, 2026
First observed
Oct 24, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 17/92 Stored blocklist matches: 1 Automated brand label: WhatsApp Scam type: Impersonation
VirusTotal
17 / 92
engine detections ·
Blocklist matches
1
Phishunt
Page captures
9
open gallery
Domain age
49 days
Reports sent
1
view timeline
Oct 24, 2026 1 Report Sent CDN
X Telegram API
ABUSE NOTICE · 72H+ 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 abuse3814@brandfocus.cn. The latest stored availability evidence still shows the domain reachable; 3 days 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
3 days
Reports sent
1
Latest case ID
PD-20261024-3EB53B
Current status
HTTP 200 at latest stored check

Questions about cn.ember-whatsapp.com

Is cn.ember-whatsapp.com legit?

No. PhishDestroy classifies cn.ember-whatsapp.com as a WhatsApp impersonation page (risk: critical, 100/100); it was first detected on 2026-10-24. VirusTotal: 17/92 engines flag it. Treat the site as unsafe.

Is cn.ember-whatsapp.com safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on cn.ember-whatsapp.com. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used cn.ember-whatsapp.com?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Source evidenceVirusTotal 17 / 92 8 sources

VirusTotal

17 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
44
Malicious
16
Suspicious
1
Undetected
31

Vendor labels

CRDF
malicious
DNS8
phishing
ESET
phishing
VIPRE
phishing
G-Data
phishing
Lionic
phishing
Sophos
malware
CyRadar
phishing
Webroot
malicious
Fortinet
phishing
SOCRadar
phishing
Seclookup
malicious
Gridinsoft
phishing
MalwareURL
phishing
BitDefender
phishing
alphaMountain.ai
suspicious
Forcepoint ThreatSeeker
phishing

Reputation score

0

Registrar

Guizhou Zhongyu Zhike Network Technology Co., Ltd.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    172.67.150.88
  • TTL, seconds
    300
    Type
    A
    Value
    104.21.57.221
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3036::ac43:9658
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3032::6815:39dd

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • ember-whatsapp.com
  • *.ember-whatsapp.com
Issuer
Google Trust Services / WE1
Serial
c60f4a37b3a1c3a4134fc25827b1465d
SHA-256
c97c180e9306bc996985846e4840ab203ba02ea563c54f94d6ef2966d09570e9
Subject
ember-whatsapp.com
Valid until
Valid from

Registration record

Registrar
Guizhou Zhongyu Zhike Network Technology Co., Ltd.
Registrar IANA ID
3814
Registrar URL
http://www.zuuq.cn
Registered
Updated
Expires
Status
  • ok
Nameservers
  • dana.ns.cloudflare.com
  • pedro.ns.cloudflare.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 44,
    "malicious": 16,
    "suspicious": 1,
    "undetected": 31
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "phishing",
    "ESET": "phishing",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "malware",
    "CyRadar": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "SOCRadar": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "phishing",
    "MalwareURL": "phishing",
    "BitDefender": "phishing",
    "alphaMountain.ai": "suspicious",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Registrar
Guizhou Zhongyu Zhike Network Technology Co., Ltd.
Created
2026-09-08T06:43:15Z
Expires
2027-09-08T06:43:15Z
Updated
2026-09-08T15:53:11Z
First seen
2026-09-22T19:30:29Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.150.88"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.57.221"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3036::ac43:9658"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3032::6815:39dd"
    }
]
Dns at
2026-10-25T06:30:08Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "ember-whatsapp.com",
        "*.ember-whatsapp.com"
    ],
    "issuer": "Google Trust Services / WE1",
    "serial": "c60f4a37b3a1c3a4134fc25827b1465d",
    "sha256": "c97c180e9306bc996985846e4840ab203ba02ea563c54f94d6ef2966d09570e9",
    "subject": "ember-whatsapp.com",
    "valid_to": "2026-12-07T15:53:51Z",
    "valid_from": "2026-09-08T14:55:58Z"
}
Registration record
{
    "registrar": "Guizhou Zhongyu Zhike Network Technology Co., Ltd.",
    "registrar_iana_id": "3814",
    "registrar_url": "http://www.zuuq.cn",
    "created": "2026-09-08T06:43:15Z",
    "updated": "2026-09-08T15:53:11Z",
    "expires": "2027-09-08T06:43:15Z",
    "status": [
        "ok"
    ],
    "nameservers": [
        "dana.ns.cloudflare.com",
        "pedro.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Separate source record · 16 malicious + 1 suspicious / 92 · 2026-10-25 06:24:46 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-25T06:24:46Z
fetched_at
2026-10-28T01:10:19Z
stats
{"timeout":0,"harmless":44,"malicious":16,"suspicious":1,"undetected":31}

OTX

no community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Report ID

ab24772a-85ea-4505-a573-a793de60ed69

Final URL

https://web.whatsapp.com/

HTTP response

200

Navigation history

  • URL
    https://cn.ember-whatsapp.com/
    Status
    200
  • URL
    https://web.whatsapp.com/
    Status
    200

DOM structure hash

8287c458b2bb17f7934d0641593108c0798175cb15ff74bd99ff30ffeb826d92

Document hash

f47e7fe0ed22d5e4f9e30e661bd0428774565feec942cfa23ce484021d0bd68c

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    web.whatsapp.com
    Type
    CNAME
    Value
    mmx-ds.cdn.whatsapp.net
  • Name
    web.whatsapp.com
    Type
    CNAME
    Value
    mmx-ds.cdn.whatsapp.net

DNSSEC valid

No

IP address

57.144.217.32

Registration record

Registrar
RegistrarSafe, LLC
Registered
Updated
Expires
Nameservers
  • a.ns.whatsapp.net
  • b.ns.whatsapp.net
  • c.ns.whatsapp.net
  • d.ns.whatsapp.net
Original source fields · JSON
Uuid
ab24772a-85ea-4505-a573-a793de60ed69
Final url
https://web.whatsapp.com/
Status
200
History
[
    {
        "url": "https://cn.ember-whatsapp.com/",
        "status": 200
    },
    {
        "url": "https://web.whatsapp.com/",
        "status": 200
    }
]
DOM structure hash
8287c458b2bb17f7934d0641593108c0798175cb15ff74bd99ff30ffeb826d92
Document hash
f47e7fe0ed22d5e4f9e30e661bd0428774565feec942cfa23ce484021d0bd68c
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "web.whatsapp.com",
        "type": "CNAME",
        "value": "mmx-ds.cdn.whatsapp.net"
    },
    {
        "name": "web.whatsapp.com",
        "type": "CNAME",
        "value": "mmx-ds.cdn.whatsapp.net"
    }
]
Dnssec valid
false
Ip
57.144.217.32
Registration record
{
    "registrar": "RegistrarSafe, LLC",
    "created": "2008-09-04T12:39:12Z",
    "updated": "2025-09-24T19:10:25Z",
    "expires": "2034-09-04T12:39:12Z",
    "nameservers": [
        "a.ns.whatsapp.net",
        "b.ns.whatsapp.net",
        "c.ns.whatsapp.net",
        "d.ns.whatsapp.net"
    ]
}

Google Safe Browsing

No threat flag

Open report

URLScan

No malicious flag

SHA-256 2da387cca83715279e9acc7b27878f14909e7ba1663b2526a4abcf99f43038dc

Open report
URLScanOriginal source recordObserved: 24 fields

Observed: · Retrieved:

Report ID

01a16e64-b7eb-7270-84e2-b2160546f970

Final URL

https://web.whatsapp.com/

HTTP response

200

Redirect type

off-domain

Redirects

  • To
    https://cn.ember-whatsapp.com/
    From
    http://cn.ember-whatsapp.com/
    Status
    307
  • To
    https://web.whatsapp.com/
    From
    https://cn.ember-whatsapp.com/

IP address

57.144.71.32

Reverse DNS (PTR)

whatsapp-cdn-shv-01-xxc1.fbcdn.net

Contacted domains

  • static.whatsapp.net
  • static.cloudflareinsights.com
  • cn.ember-whatsapp.com

Contacted IP addresses

  • 57.144.71.32
  • 104.16.80.73
  • 172.67.150.88

Autonomous systems (ASN)

  • 32934
  • 13335

Server countries

  • US

Document hash

f47e7fe0ed22d5e4f9e30e661bd0428774565feec942cfa23ce484021d0bd68c

JavaScript globals

  • dataElement
  • copyVariables
  • variables
  • Env
  • __annotator
  • __d
  • requireLazy
  • _btldr
  • _nowInl
  • _qplInl
  • THEME_KEY
  • SYSTEM_THEME_MODE
  • splashscreenVariableMap
  • prefersColorSchemeMode
  • prefersDark
  • prefersLight
  • systemThemeModeSet
  • configuredTheme
  • generator
  • getIterables
  • polyfillIteratorFunctions
  • __t
  • __w
  • __bodyWrapper
  • __DEV__
  • emptyFunction
  • FB_enumerate
  • babelHelpers
  • define
  • require
  • requireInterop
  • importDefault
  • importNamespace
  • requireDynamic
  • __onBeforeModuleFactory
  • __onAfterModuleFactory
  • $RefreshReg$
  • $RefreshSig$
  • getErrorSafe
  • ErrorGuard

Cookies

  • wa_ul

Browser storage keys

  • __test__1792853462439
  • Session
  • check_quota
  • mutex_falco_queue_log^$^#^#0^#hmac_ttl.1792853461.AR3teJIKu3t9s9NfRfev65u0-lSBiU
  • mutex_falco_queue_immediately^$^#^#0^#hmac_ttl.1792853461.AR3teJIKu3t9s9NfRfev65
  • mutex_falco_queue_critical^$^#^#0^#hmac_ttl.1792853461.AR3teJIKu3t9s9NfRfev65u0-
  • RSTData
  • storage_test
  • wa_crash_recent_load_times
  • __test__1792853462806
  • TabId
  • mutex_banzai
  • WAUnknownID
  • banzai:last_storage_flush

TLS session and certificate

Subject alternative names
  • ember-whatsapp.com
  • *.ember-whatsapp.com
Cipher
AES_128_GCM
Issuer
WE1
Subject
ember-whatsapp.com
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

4360

Registered domain age, days

4829

Certificate age, days

83

Certificate validity, days

90

Cisco Umbrella rank

1332

Page requests

32

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
-99
Malicious
No
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
cloudflare
Content-type
text/html; charset=UTF-8
Original source fields · JSON
Uuid
01a16e64-b7eb-7270-84e2-b2160546f970
Final url
https://web.whatsapp.com/
Status
200
Redirected
off-domain
Redirects
[
    {
        "to": "https://cn.ember-whatsapp.com/",
        "from": "http://cn.ember-whatsapp.com/",
        "status": 307
    },
    {
        "to": "https://web.whatsapp.com/",
        "from": "https://cn.ember-whatsapp.com/"
    }
]
Ip
57.144.71.32
Ptr
whatsapp-cdn-shv-01-xxc1.fbcdn.net
Contacted domains
[
    "static.whatsapp.net",
    "static.cloudflareinsights.com",
    "cn.ember-whatsapp.com"
]
Contacted IP addresses
[
    "57.144.71.32",
    "104.16.80.73",
    "172.67.150.88"
]
Asns
[
    "32934",
    "13335"
]
Countries
[
    "US"
]
Document hash
f47e7fe0ed22d5e4f9e30e661bd0428774565feec942cfa23ce484021d0bd68c
Globals
[
    "dataElement",
    "copyVariables",
    "variables",
    "Env",
    "__annotator",
    "__d",
    "requireLazy",
    "_btldr",
    "_nowInl",
    "_qplInl",
    "THEME_KEY",
    "SYSTEM_THEME_MODE",
    "splashscreenVariableMap",
    "prefersColorSchemeMode",
    "prefersDark",
    "prefersLight",
    "systemThemeModeSet",
    "configuredTheme",
    "generator",
    "getIterables",
    "polyfillIteratorFunctions",
    "__t",
    "__w",
    "__bodyWrapper",
    "__DEV__",
    "emptyFunction",
    "FB_enumerate",
    "babelHelpers",
    "define",
    "require",
    "requireInterop",
    "importDefault",
    "importNamespace",
    "requireDynamic",
    "__onBeforeModuleFactory",
    "__onAfterModuleFactory",
    "$RefreshReg$",
    "$RefreshSig$",
    "getErrorSafe",
    "ErrorGuard"
]
Cookies
[
    "wa_ul"
]
Storage keys
[
    "__test__1792853462439",
    "Session",
    "check_quota",
    "mutex_falco_queue_log^$^#^#0^#hmac_ttl.1792853461.AR3teJIKu3t9s9NfRfev65u0-lSBiU",
    "mutex_falco_queue_immediately^$^#^#0^#hmac_ttl.1792853461.AR3teJIKu3t9s9NfRfev65",
    "mutex_falco_queue_critical^$^#^#0^#hmac_ttl.1792853461.AR3teJIKu3t9s9NfRfev65u0-",
    "RSTData",
    "storage_test",
    "wa_crash_recent_load_times",
    "__test__1792853462806",
    "TabId",
    "mutex_banzai",
    "WAUnknownID",
    "banzai:last_storage_flush"
]
Tls
{
    "san": [
        "ember-whatsapp.com",
        "*.ember-whatsapp.com"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "ember-whatsapp.com",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-07T15:53:51Z",
    "valid_from": "2026-09-08T14:55:58Z"
}
Domain age days
4360
Apex age days
4829
Tls age days
83
Tls valid days
90
Umbrella rank
1332
Requests
32
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": -99,
        "malicious": false
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=UTF-8"
}
Separate monitor record · 2026-10-24 19:22 UTC

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

record_source
domain_monitor.urlscan
uuid
01a16e64-b7eb-7270-84e2-b2160546f970
score
0
malicious
false
result_at
2026-10-24T19:22:36Z
enriched_at
2026-10-25T09:14:24Z
source_timestamps
{"urlscan_result_at":"2026-10-24 21:22:36","urlscan_enriched_at":"2026-10-25 10:14:24"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

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

Open report
Separate monitor score · 25 / 100 · 2026-10-24T18:20:17Z

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

record_source
domain_monitor.dom_analysis
heuristic_score
25
analyzed_at
2026-10-24T18:20:17Z
source_timestamp
2026-10-24 20:20:17
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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

CAA records

Domain
cn.ember-whatsapp.com

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
1587

Page title and metadata

Page title
Preparing Secure Connection...

Trackers

Requests
1

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
3
TLS
17
Waiting
33
Connection
7
Download
1
Response time, ms
61

TLS connection

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

Ports

Open ports
  • 80
  • 443
  • 8080

Carbon estimate

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

DNS servers

Nameservers
  • IP address
    108.162.195.183
    Host
    pedro.ns.cloudflare.com
  • IP address
    108.162.192.105
    Host
    dana.ns.cloudflare.com
DNS zone
ember-whatsapp.com

Location

IP address
2a06:98c1:3121::3
ASN
13335
Organization
CloudFLARENET-EU
City
London
Country
GB

TLS certificate

Issuer
Google Trust Services / WE1
Subject
ember-whatsapp.com

DNS records

A
  • 188.114.96.3
  • 188.114.97.3
AAAA
  • 2a06:98c1:3121::3
  • 2a06:98c1:3120::3

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
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
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
2a06:98c1:3121::3
IP version
6

Redirects

Redirect chain
  • https://cn.ember-whatsapp.com

Registration record

Registrar
Guizhou Zhongyu Zhike Network Technology Co., Ltd.
Registered
Updated
Expires
Status
  • ok https://icann.org/epp
Nameservers
  • dana.ns.cloudflare.com
  • pedro.ns.cloudflare.com

HTTP headers

Response headers
Server
cloudflare
Content-type
text/html; charset=UTF-8
Original source fields · JSON
Caa records
{
    "domain": "cn.ember-whatsapp.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-24T14:53:33Z",
    "first": "2026-10-24T14:53:33Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 1587
}
Page title and metadata
{
    "title": "Preparing Secure Connection..."
}
Trackers
{
    "requests": 1
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 3,
        "tls": 17,
        "wait": 33,
        "connect": 7,
        "download": 1
    },
    "response_ms": 61
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Carbon
{
    "bytes": 424,
    "co2_grams": 0,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "108.162.195.183",
            "host": "pedro.ns.cloudflare.com"
        },
        {
            "ip": "108.162.192.105",
            "host": "dana.ns.cloudflare.com"
        }
    ],
    "zone": "ember-whatsapp.com"
}
Location
{
    "ip": "2a06:98c1:3121::3",
    "asn": "13335",
    "org": "CloudFLARENET-EU",
    "city": "London",
    "country": "GB"
}
Ssl
{
    "issuer": "Google Trust Services / WE1",
    "subject": "ember-whatsapp.com"
}
DNS records
{
    "A": [
        "188.114.96.3",
        "188.114.97.3"
    ],
    "AAAA": [
        "2a06:98c1:3121::3",
        "2a06:98c1:3120::3"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2a06:98c1:3121::3",
    "family": 6
}
Redirects
{
    "chain": [
        "https://cn.ember-whatsapp.com"
    ]
}
Registration record
{
    "registrar": "Guizhou Zhongyu Zhike Network Technology Co., Ltd.",
    "created": "2026-09-08T06:43:15Z",
    "updated": "2026-09-08T15:53:11Z",
    "expires": "2027-09-08T06:43:15Z",
    "status": [
        "ok https://icann.org/epp"
    ],
    "nameservers": [
        "dana.ns.cloudflare.com",
        "pedro.ns.cloudflare.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html; charset=UTF-8"
    }
}
Blocklist matchesPhishDestroy · Phishunt · no match in the other 10 2
PhishDestroy PhishDestroy list View source
Phishunt Listed View source

Checked, no match

Last checked

Stored Capture · 9 captures

Primary capture 1 / 9
SourcePrimary capture
Recorded
StateStored capture
Position1 / 9
Open capture Wayback Download
All capture links and hashes (9)
cn.ember-whatsapp.com: Whatsapp impersonation — Flagged by Phishunt, 17/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card cn.ember-whatsapp.com: Whatsapp impersonation — Flagged by Phishunt, 17/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v 81bc383587b2

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context United Kingdom188.114.96.3 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) Guizhou Zhongyu Zhike …
Abuse contactabuse3814@brandfocus.cn
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for ember-whatsapp.com →
Registration (base domain)ember-whatsapp.com · Created Sep 8, 2026 (49d · New) — Expires Sep 8, 2027
WHOIS statusok
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 24, 2026
DOM Analysisanalyzed Oct 24, 2026score 88/1001 brand signal
Submitted URLhttp://cn.ember-whatsapp.com/
Favicon Hash
Case ID
Observed page title
Preparing Secure Connection...
Automated brand references
WhatsApp
TLS Certificate
Issued by Google Trust Services / WE1 · stored validity ends in 40 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United Kingdom188.114.96.3
Network ASN
AS13335
Organization
CloudFLARENET-EU
Observed location
United KingdomLondon, GB
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • dana.ns.cloudflare.com
  • pedro.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-09-08 14:55:58
Valid until
2026-12-07 15:53:51
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintc97c180e9306bc996985846e4840ab203ba02ea563c54f94d6ef2966d09570e9
Certificate names · 2 SANs
  • ember-whatsapp.com
  • *.ember-whatsapp.com

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

viewdns.info · 188.114.96.3rapiddns.io

Latest Classified Outcome 2026-10-27 11:05:15 UTC

The site was reachable but behind an access challenge at the latest check.

Technical details
Primary outcome Reachable but protected reason: Cloudflare Challenge 85% confidence
Attribution Cloudflare mechanism: Challenge source: Current Http Probe
Evidence layers Availability: Reachable but protected Content: Unknown DNS: Resolved Registration: Unknown
Latest HTTP observation Reachable but protected Cloudflare Challenge Cloudflare Challenge 85% 2026-10-27 11:05:15 UTC
RDAP registration
Observed timeline last reachable: 2026-10-25 23:00:45 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 · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

17 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 17 detections
alphaMountain.ai
BitDefender
CRDF
CyRadar
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Lionic
MalwareURL
Seclookup
SOCRadar
Sophos
VIPRE
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of cn.ember-whatsapp.com · checked Oct 24, 2026

56
Needs Work
Performance
FCP
9.7 s
First Contentful Paint
LCP
10.07 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0 ms
Total Blocking Time
SI
9.7 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: http://cn.ember-whatsapp.com/
Final URL: https://cn.ember-whatsapp.com/
Preparing Secure Connection...
Response
HTTP 200
HTML body
791 B
Compressed
596 B
Links
0 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html; charset=UTF-8
Cache-Control: no-store, no-cache, must-revalidate
Content-Encoding: gzip
Server: cloudflare
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 13
alt-svc
h3=":443"; ma=86400
Cache-Control
no-store, no-cache, must-revalidate
CF-RAY
a4f9cf74abaa005e-EWR
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html; charset=UTF-8
Date
Sat, 24 Oct 2026 14:53:19 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=wN8FxlTdA%2BxuPbkR8fF7e%2FZNUJbYts219ZGaUOlhAxBWvlAqijuhD57%2Bv6wr0zfXDA0rY6VFmMDorT3tiiNrsKKvH8rcsGD45sGgd2QHxsEWezlW4D2P8ZY1SXWAIzNtQVwdaQQW2
Server
cloudflare
Server-Timing
cfEdge;dur=18,cfOrigin;dur=0,cfWorker;dur=0
Transfer-Encoding
chunked
X-CF-Shield
wash-yahoo

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

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

Stored observation history5

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

    protected

    cloudflare_challenge · Cloudflare · challenge

  2. Availability monitor · Recorded state

    protected

    cloudflare_challenge · Cloudflare · challenge

  3. VirusTotal · Detection count

    19→17

    Engines added
    None recorded
    Engines removed
    LevelBlue · URLQuery
    Recorded vendor total
    17
  4. Availability monitor · Recorded state

    protected

    cloudflare_challenge · Cloudflare · challenge

  5. Domain monitor · First collection record

    Reachable

All retained availability observations15

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_http_probeprotected
    Observation source
    current_http_probe
    Cause
    cloudflare_challenge
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    cdn_security
    Recorded actor
    Cloudflare
    Mechanism
    challenge
    Monitor confidence
    85
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:05:15.000000
    Evidence SHA-256
    742683da325a90106a7bfee74515d0babb1384962296d9b6fcf8c9bfd7e38fe6
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:05:15
    Evidence reason
    cloudflare_challenge
  2. http_observationprotected
    Observation source
    http_observation
    Cause
    cloudflare_challenge
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    cdn_security
    Recorded actor
    Cloudflare
    Mechanism
    challenge
    Monitor confidence
    85
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:05:15.000000
    Evidence SHA-256
    742683da325a90106a7bfee74515d0babb1384962296d9b6fcf8c9bfd7e38fe6
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:05:15
    Evidence reason
    cloudflare_challenge
  3. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 21:55:09.041159
    Evidence SHA-256
    9364d16752bb56ab1a07deaf5402c56950e2c8b359744c1506357d864927fa66
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-26 21:55:09.041159
    Evidence reason
  4. current_http_probeprotected
    Observation source
    current_http_probe
    Cause
    cloudflare_challenge
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    cdn_security
    Recorded actor
    Cloudflare
    Mechanism
    challenge
    Monitor confidence
    85
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 12:00:40.000000
    Evidence SHA-256
    4ac3e74f417552c8b71a5eb12297a528d8d0d95725317e79c08d959c549576c8
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 12:00:40
    Evidence reason
    cloudflare_challenge
  5. http_observationprotected
    Observation source
    http_observation
    Cause
    cloudflare_challenge
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    cdn_security
    Recorded actor
    Cloudflare
    Mechanism
    challenge
    Monitor confidence
    85
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 12:00:40.000000
    Evidence SHA-256
    4ac3e74f417552c8b71a5eb12297a528d8d0d95725317e79c08d959c549576c8
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 12:00:40
    Evidence reason
    cloudflare_challenge
  6. current_http_probeprotected
    Observation source
    current_http_probe
    Cause
    cloudflare_challenge
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    cdn_security
    Recorded actor
    Cloudflare
    Mechanism
    challenge
    Monitor confidence
    85
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 00:00:45.000000
    Evidence SHA-256
    e3c69e42dea31dba72c7fff0cdb834debfbb101088c1b886ac13bffcdf9bbf8b
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 00:00:45
    Evidence reason
    cloudflare_challenge
  7. http_observationprotected
    Observation source
    http_observation
    Cause
    cloudflare_challenge
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    cdn_security
    Recorded actor
    Cloudflare
    Mechanism
    challenge
    Monitor confidence
    85
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 00:00:45.000000
    Evidence SHA-256
    e3c69e42dea31dba72c7fff0cdb834debfbb101088c1b886ac13bffcdf9bbf8b
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 00:00:45
    Evidence reason
    cloudflare_challenge
  8. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 21:55:07.813656
    Evidence SHA-256
    c03dbd2dcd7c6f08fd7189e78b7cd4e699f4a81ddbfb248f4d57c8431243efdd
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-25 21:55:07.813656
    Evidence reason
  9. current_http_probeprotected
    Observation source
    current_http_probe
    Cause
    cloudflare_challenge
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    cdn_security
    Recorded actor
    Cloudflare
    Mechanism
    challenge
    Monitor confidence
    85
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 12:00:46.000000
    Evidence SHA-256
    146a40eafd443e861b8ad0a9578bbc0cbf89bbaafac6df125315f3bf40e773be
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 12:00:46
    Evidence reason
    cloudflare_challenge
  10. http_observationprotected
    Observation source
    http_observation
    Cause
    cloudflare_challenge
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    cdn_security
    Recorded actor
    Cloudflare
    Mechanism
    challenge
    Monitor confidence
    85
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 12:00:46.000000
    Evidence SHA-256
    146a40eafd443e861b8ad0a9578bbc0cbf89bbaafac6df125315f3bf40e773be
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 12:00:46
    Evidence reason
    cloudflare_challenge
  11. current_http_probeprotected
    Observation source
    current_http_probe
    Cause
    cloudflare_challenge
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    cdn_security
    Recorded actor
    Cloudflare
    Mechanism
    challenge
    Monitor confidence
    85
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 01:07:10.000000
    Evidence SHA-256
    a986be21dae2b4b6bbdceead5711105e0c2edb484abf3d0249fed2939571ab5e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 01:07:10
    Evidence reason
    cloudflare_challenge
  12. http_observationprotected
    Observation source
    http_observation
    Cause
    cloudflare_challenge
    Availability state
    reachable_protected
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    cdn_security
    Recorded actor
    Cloudflare
    Mechanism
    challenge
    Monitor confidence
    85
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 01:07:10.000000
    Evidence SHA-256
    a986be21dae2b4b6bbdceead5711105e0c2edb484abf3d0249fed2939571ab5e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 01:07:10
    Evidence reason
    cloudflare_challenge
  13. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 22:55:07.425478
    Evidence SHA-256
    db407a17211d6cfcb77d163e1a7001bdf0972c8f223c354514bcb9984da64451
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-24 22:55:07.425478
    Evidence reason
  14. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 16:52:49.000000
    Evidence SHA-256
    8dd31a3303cafcaf8fc6717db23793a354687dba73e494e382e5c9c453042ed8
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-24 16:52:49
    Evidence reason
  15. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 16:52:49.000000
    Evidence SHA-256
    8dd31a3303cafcaf8fc6717db23793a354687dba73e494e382e5c9c453042ed8
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-24 16:52:49
    Evidence reason

Threat Response Pipeline

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

Recorded events: 11. 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: 1 of 1
  • Threat Ingested
    cn.ember-whatsapp.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · Cloudflare Radar Report · VirusTotal · Blocklist Detection · Brand Impersonation · Forensic Evidence Collected · Technical Analysis Recorded · VirusTotal detections −2 Recorded: 8 of 8
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • VirusTotal
    Detections recorded on VirusTotal: 17/92
  • Blocklist Detection
    Found in blocklists: Phishunt
  • Brand Impersonation
    Automated brand label: WhatsApp
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, URLQuery, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
  • VirusTotal detections −2
    Detections removed: 2 (19 → 17)
Notification RecordsSent Report Recorded Recorded: 1 of 1
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: Guizhou Zhongyu Zhike Network Technology Co., Ltd.. Abuse contacts: 1.
    • abuse3814@brandfocus.cn
Publication & AvailabilityDestroyList Published · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

4 entries
  1. VirusTotal

    17/92 engine detections

    View source
  2. Abuse report sent

    PD-20261024-3EB53B · Receipt 82447

    abuse3814@brandfocus.cn
  3. Added to PhishDestroy

    cn.ember-whatsapp.com

    View source
  4. URLScan

    Page captured

    View source
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

Check for cloaking

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

cn.ember-whatsapp.com

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 17 det. ChainPatrol URLQuery Report stored SSL Labs Stored certificate dates valid CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261024-3EB53B Recipient: abuse3814@brandfocus.cn
PDF notice generated
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

Were You Affected by This Site?

5 evidence signal groups linked 1 stored notification records Last known active
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. Silence is the scammer’s greatest advantage. Break it.
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

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
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.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

Report to Your Local Authorities

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

Even if funds were frozen, they cannot be recovered without an official police report or court order. Submitting a complaint is the only path to potential recovery.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

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 cn.ember-whatsapp.com)
  • 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

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.

Request a correction or appeal How PhishDestroy works
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/cn.ember-whatsapp.com"
  title="PhishDestroy threat report for cn.ember-whatsapp.com"
  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>