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

wecbhsk.com

In short

PhishDestroy stores a record for wecbhsk.com. Source observations are dated separately; missing checks do not establish safety.

“wecbhsk.com”

Review the evidence
Registrar
Realtime
Resolved IP
United States23.20.116.56Amazon.com
Registered
Oct 7, 2026
First observed
Oct 27, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 3/92 Young domain: 24 days old
VirusTotal
3 / 92
engine detections ·
URLScan
Malicious
engine verdict · score 98
Cloudflare Radar
Phishing
Page captures
7
open gallery
Domain age
24 days
registered 2026-10-07 according to WHOIS
Reports sent
1
view timeline
Oct 27, 2026 1 Report Sent
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 rtr-security-threats@realtimeregister.com. The latest stored availability evidence still shows the domain reachable; 4 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
4 days
Reports sent
1
Latest case ID
PD-20261027-3BEE07
Current status
HTTP 200 at latest stored check

Questions about wecbhsk.com

Is wecbhsk.com legit?

PhishDestroy stores a record for wecbhsk.com. Source observations are dated separately; missing checks do not establish safety.

Is wecbhsk.com safe to connect a wallet?

This report does not record which wallet requests wecbhsk.com makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.

What should I do if I used wecbhsk.com?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you 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

Source evidenceVirusTotal 3 / 92 8 sources

VirusTotal

3 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 16 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
53
Malicious
3
Suspicious
0
Undetected
36

Vendor labels

CRDF
malicious
SOCRadar
phishing
alphaMountain.ai
phishing

Reputation score

0

Tags

  • dga

Categories

alphaMountain.ai
Phishing (alphaMountain.ai)

Registrar

Realtime Register B.V.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    21600
    Type
    NS
    Value
    gracie.ns.cloudflare.com
  • TTL, seconds
    300
    Type
    A
    Value
    23.20.116.56
  • TTL, seconds
    21600
    Type
    NS
    Value
    charles.ns.cloudflare.com
  • TTL, seconds
    1800
    Type
    SOA
    Responsible mailbox
    dns.cloudflare.com
    Value
    charles.ns.cloudflare.com

DNS records observed

JARM fingerprint

21d19d00021d21d00042d43d0000005ad20eceaf7f71ae0887d2ff117bf97f

Certificate

Subject alternative names
  • webttt555.shop
  • www.webttt555.shop
Issuer
Sectigo Limited / Sectigo Public Server Authentication CA DV R36
Serial
c5cac7fe678f8b0fbc95b366ceb7e048
SHA-256
fd6b777295029e6aced108e8ee06b1c747bfd8984ac34e2043d53f062713d775
Subject
webttt555.shop
Valid until
Valid from

Registration record

Registrar
Realtime Register B.V.
Registrar IANA ID
839
Registrar URL
http://www.realtimeregister.com
Registered
Updated
Expires
Status
  • clientTransferProhibited
Nameservers
  • ashton.ns.cloudflare.com
  • june.ns.cloudflare.com
DNSSEC
unsigned

Registry data (RDAP)

Status
  • active
Registry events
Expiration
Last changed
Registration
Registrar expiration
Last RDAP database update
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 53,
    "malicious": 3,
    "suspicious": 0,
    "undetected": 36
}
Vendor labels
{
    "CRDF": "malicious",
    "SOCRadar": "phishing",
    "alphaMountain.ai": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
Registrar
Realtime Register B.V.
Created
2026-10-07T08:24:36Z
Expires
2027-10-07T08:24:36Z
Updated
2026-10-07T08:26:27Z
First seen
2026-10-07T10:02:25Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "gracie.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "23.20.116.56"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "charles.ns.cloudflare.com"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "charles.ns.cloudflare.com"
    }
]
Dns at
2026-10-27T13:31:43Z
Jarm
21d19d00021d21d00042d43d0000005ad20eceaf7f71ae0887d2ff117bf97f
Certificate
{
    "san": [
        "webttt555.shop",
        "www.webttt555.shop"
    ],
    "issuer": "Sectigo Limited / Sectigo Public Server Authentication CA DV R36",
    "serial": "c5cac7fe678f8b0fbc95b366ceb7e048",
    "sha256": "fd6b777295029e6aced108e8ee06b1c747bfd8984ac34e2043d53f062713d775",
    "subject": "webttt555.shop",
    "valid_to": "2027-03-14T23:59:59Z",
    "valid_from": "2026-08-28T00:00:00Z"
}
Registration record
{
    "registrar": "Realtime Register B.V.",
    "registrar_iana_id": "839",
    "registrar_url": "http://www.realtimeregister.com",
    "created": "2026-10-07T08:24:36Z",
    "updated": "2026-10-07T08:26:27Z",
    "expires": "2027-10-07T08:24:36Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "ashton.ns.cloudflare.com",
        "june.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "active"
    ],
    "events": {
        "expiration": "2027-10-07T08:24:36Z",
        "last changed": "2026-10-26T10:39:58Z",
        "registration": "2026-10-07T08:24:36Z",
        "registrar expiration": "2027-10-07T08:24:36Z",
        "last update of RDAP database": "2026-10-26T11:55:18Z"
    }
}
Separate source record · 3 malicious + 0 suspicious / 92 · 2026-10-27 13:05:09 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-27T13:05:09Z
fetched_at
2026-10-27T16:40:55Z
stats
{"timeout":0,"harmless":53,"malicious":3,"suspicious":0,"undetected":36}

Cloudflare Radar

Phishing

Open report
Cloudflare RadarOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Report ID

7fc58f9a-ff30-42ec-9956-f94945b63169

Final URL

https://wecbhsk.com/

Navigation history

  • URL
    https://wecbhsk.com/
    Status
    0

DOM structure hash

94bfc7c24186e5b245b5675859fb84b248547086370961e5637590177432b219

URL risk categories

  • Phishing

Domain risk categories

  • DGA Domains
  • Security threats
  • New Domains
  • Security Risks
  • Phishing
  • Newly Seen Domains
  • CIPA Filter
  • CIPA

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    wecbhsk.com
    Type
    A
    Value
    23.20.116.56

DNSSEC valid

No

Verdict

Tags
  • phishing
Malicious
Yes
Categories
  • phishing

Registration record

Registrar
Realtime Register B.V.
Registered
Updated
Expires
Nameservers
  • charles.ns.cloudflare.com
  • gracie.ns.cloudflare.com
Original source fields · JSON
Uuid
7fc58f9a-ff30-42ec-9956-f94945b63169
Final url
https://wecbhsk.com/
History
[
    {
        "url": "https://wecbhsk.com/",
        "status": 0
    }
]
DOM structure hash
94bfc7c24186e5b245b5675859fb84b248547086370961e5637590177432b219
Url risks
[
    "Phishing"
]
Domain risks
[
    "DGA Domains",
    "Security threats",
    "New Domains",
    "Security Risks",
    "Phishing",
    "Newly Seen Domains",
    "CIPA Filter",
    "CIPA"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "wecbhsk.com",
        "type": "A",
        "value": "23.20.116.56"
    }
]
Dnssec valid
false
Verdict
{
    "tags": [
        "phishing"
    ],
    "malicious": true,
    "categories": [
        "phishing"
    ]
}
Registration record
{
    "registrar": "Realtime Register B.V.",
    "created": "2026-10-07T08:24:36Z",
    "updated": "2026-10-26T10:39:57Z",
    "expires": "2027-10-07T08:24:36Z",
    "nameservers": [
        "charles.ns.cloudflare.com",
        "gracie.ns.cloudflare.com"
    ]
}

URLScan

Malicious · engine verdict · score 98

SHA-256 850a2a27771804c9e7ffd73f100bdd6364e2aad6aad750a0aa18a23b21913789

Open report
URLScanOriginal source recordObserved: 21 fields

Observed: · Retrieved:

Report ID

01a17e3e-9550-722e-82c5-3def27ae33b5

Final URL

https://wecbhsk.com/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://wecbhsk.com/
    From
    http://wecbhsk.com/
    Status
    307

IP address

23.20.116.56

Reverse DNS (PTR)

ec2-23-20-116-56.compute-1.amazonaws.com

Contacted IP addresses

  • 23.20.116.56

Autonomous systems (ASN)

  • 14618

Server countries

  • US

Document hash

04d05978fdb111358073ab0524e5c1fafc0826615c206987618416b8bd8a4747

Script hashes

  • 8e89fcb524218901b5fe4b302ec9e9f8591580426d964936f74e0c35f22e755f
  • dfe11c34cb98c6e3ff6674130049a0922b72ef3b6604982edc4b45d205635557

JavaScript globals

  • __VUE_INSTANCE_SETTERS__
  • __VUE_SSR_SETTERS__
  • __vueuse_ssr_handlers__
  • __VUE__
  • __vite_is_modern_browser

Browser storage keys

  • topActive

Domain age, days

17

Registered domain age, days

17

Certificate age, days

60

Certificate validity, days

198

Page requests

10

Provider verdicts

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

HTTP headers

Content-type
image/png
Original source fields · JSON
Uuid
01a17e3e-9550-722e-82c5-3def27ae33b5
Final url
https://wecbhsk.com/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://wecbhsk.com/",
        "from": "http://wecbhsk.com/",
        "status": 307
    }
]
Ip
23.20.116.56
Ptr
ec2-23-20-116-56.compute-1.amazonaws.com
Contacted IP addresses
[
    "23.20.116.56"
]
Asns
[
    "14618"
]
Countries
[
    "US"
]
Document hash
04d05978fdb111358073ab0524e5c1fafc0826615c206987618416b8bd8a4747
Script hashes
[
    "8e89fcb524218901b5fe4b302ec9e9f8591580426d964936f74e0c35f22e755f",
    "dfe11c34cb98c6e3ff6674130049a0922b72ef3b6604982edc4b45d205635557"
]
Globals
[
    "__VUE_INSTANCE_SETTERS__",
    "__VUE_SSR_SETTERS__",
    "__vueuse_ssr_handlers__",
    "__VUE__",
    "__vite_is_modern_browser"
]
Storage keys
[
    "topActive"
]
Domain age days
17
Apex age days
17
Tls age days
60
Tls valid days
198
Requests
10
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 98,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "content-type": "image/png"
}
Separate monitor record · 2026-10-28 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a17e3e-9550-722e-82c5-3def27ae33b5
score
0
malicious
false
result_at
2026-10-28T04:30:42Z
enriched_at
2026-10-28T09:17:22Z
source_timestamps
{"urlscan_result_at":"2026-10-28 05:30:42","urlscan_enriched_at":"2026-10-28 10:17:22"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

0 / 100 · heuristic score · 0 brand references · 0 classifications

Open report
Separate monitor score · 0 / 100 · 2026-10-27T17:00:02Z

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
0
analyzed_at
2026-10-27T17:00:02Z
source_timestamp
2026-10-27 18:00:02
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: 15 fields

Mail configuration

SPF lookups
0

CAA records

Domain
wecbhsk.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
3867

Trackers

Requests
5

TLS connection

ALPN
http/1.1
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
No
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443

Threat lists

Phishtank
Yes

DNS servers

Nameservers
  • IP address
    172.64.34.144
    Host
    gracie.ns.cloudflare.com
  • IP address
    108.162.193.83
    Host
    charles.ns.cloudflare.com
DNS zone
wecbhsk.com

Location

IP address
23.20.116.56
ASN
14618
Organization
Amazon.com
City
Ashburn
Country
US

TLS certificate

Issuer
Sectigo Limited / Sectigo Public Server Authentication CA DV R36
Subject
webttt555.shop

DNS records

A
  • 23.20.116.56
NS
  • gracie.ns.cloudflare.com
  • charles.ns.cloudflare.com
SOA
Primary nameserver
charles.ns.cloudflare.com
Hostmaster
dns.cloudflare.com
Serial
2418584837
Refresh, seconds
10000
Retry, seconds
2400
Expiry, seconds
604800
Minimum TTL, seconds
1800

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

IP lookup

IP address
23.20.116.56
IP version
4

Registration record

Registrar
Realtime Register B.V.
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • charles.ns.cloudflare.com
  • gracie.ns.cloudflare.com
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "wecbhsk.com"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Web archive observations
{
    "last": "2026-10-27T16:38:38Z",
    "first": "2026-10-27T16:38:38Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 3867
}
Trackers
{
    "requests": 5
}
TLS connection
{
    "alpn": "http/1.1",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": false,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Threats
{
    "phishtank": true
}
Dns server
{
    "ns": [
        {
            "ip": "172.64.34.144",
            "host": "gracie.ns.cloudflare.com"
        },
        {
            "ip": "108.162.193.83",
            "host": "charles.ns.cloudflare.com"
        }
    ],
    "zone": "wecbhsk.com"
}
Location
{
    "ip": "23.20.116.56",
    "asn": "14618",
    "org": "Amazon.com",
    "city": "Ashburn",
    "country": "US"
}
Ssl
{
    "issuer": "Sectigo Limited / Sectigo Public Server Authentication CA DV R36",
    "subject": "webttt555.shop"
}
DNS records
{
    "A": [
        "23.20.116.56"
    ],
    "NS": [
        "gracie.ns.cloudflare.com",
        "charles.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"charles.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2418584837, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Get ip
{
    "ip": "23.20.116.56",
    "family": 4
}
Registration record
{
    "registrar": "Realtime Register B.V.",
    "created": "2026-10-07T08:24:36Z",
    "updated": "2026-10-26T10:39:57Z",
    "expires": "2027-10-07T08:24:36Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "charles.ns.cloudflare.com",
        "gracie.ns.cloudflare.com"
    ]
}
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
Security threats Phishing Security Risks Phishing New Domains DGA Domains
View full Cloudflare Radar report
Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 7 captures

Primary capture 1 / 7
SourcePrimary capture
Recorded
StateStored capture
Position1 / 7
Open capture Wayback Download
All capture links and hashes (7)
wecbhsk.com: caution — 3/92 VirusTotal engines. PhishDestroy risk score 69/100 (high).
Social preview card wecbhsk.com: caution — 3/92 VirusTotal engines. PhishDestroy risk score 69/100 (high). v a37bbb8c2635

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 98 report ↗
IP Reputation United States23.20.116.56 abuse score 0/100 0 reports checked Oct 27, 2026
Registrar Realtime
Abuse contactrtr-security-threats@realtimeregister.com
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for wecbhsk.com →
Hosting abuse contact rtr-security-threats@realtimeregister.com Amazon.com · AS14618
RegistrationCreated Oct 7, 2026 (24d · Very New!) — Expires Oct 7, 2027
WHOIS statusclientTransferProhibited
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 27, 2026
DOM Analysisanalyzed Oct 27, 2026score 0/100
Submitted URLhttp://wecbhsk.com/
Favicon Hash
Case ID
Observed page title
wecbhsk.com
TLS Certificate
Issued by Sectigo Limited / Sectigo Public Server Authentication CA DV R36 · stored validity ends in 134 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
United States23.20.116.56
Network ASN
AS14618
AS name
AMAZON-AES - Amazon.com, Inc., US
Organization
Amazon.com
Observed location
United StatesAshburn, US
Server header
nginx

Nameservers 2

  • charles.ns.cloudflare.com
  • gracie.ns.cloudflare.com

SOA

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

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
Sectigo Limited / Sectigo Public Server Authentication CA DV R36
Valid from
2026-08-28 00:00:00
Valid until
2027-03-14 23:59:59
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintfd6b777295029e6aced108e8ee06b1c747bfd8984ac34e2043d53f062713d775
Certificate names · 2 SANs
  • webttt555.shop
  • www.webttt555.shop

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

viewdns.info · 23.20.116.56rapiddns.io

Latest Classified Outcome 2026-10-31 11:36:02 UTC

The site was serving its pages at the latest check.

Technical details
Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-31 11:36:02 UTC
RDAP registration
Observed timeline last reachable: 2026-10-31 11:36:02 UTC last content: 2026-10-31 11:36:02 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.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

3 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 3 detections
alphaMountain.ai
BitDefender
CRDF
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
Netcraft
Seclookup
SOCRadar
Sophos
URLQuery
VIPRE
Webroot
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://wecbhsk.com/
WEBULL
Response
HTTP 200
HTML body
1,016 B
Compressed
578 B
Links
0 internal · 0 external
Detected technologies
nginx
Selected response headers
Server: nginx
Content-Type: text/html; charset=utf-8
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Favicon fingerprint: 1526c8f30be2d785f92cd68950a6d06ef230dd5ebc779311c069446a4be17e85
Saved response-header values · 8
Accept-Ranges
bytes
Connection
keep-alive
Content-Length
1016
Content-Type
text/html; charset=utf-8
Date
Tue, 27 Oct 2026 16:38:29 GMT
Etag
"6adec40f-3f8"
Last-Modified
Mon, 26 Oct 2026 03:07:59 GMT
Server
nginx

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

Archived
Registration & observation details3

Availability observations

Last reachable observation
Last content 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.

Captured network requests

Network requests: 10 SHA-256 hashes: 10 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:54 UTC.

Open this scan on URLScan 01a17e3e-9550-722e-82c5-3def27ae33b5 ↗

Check for cloaking

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

Page titles differ

Our scanner could not complete this check.

Browser
wecbhsk.com
Crawler
WEBUCCC
wecbhsk.com
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

    live_content

    content_served

  2. Availability monitor · Recorded state

    live_content

    content_served

  3. Availability monitor · Recorded state

    live_content

    content_served

  4. Availability monitor · Recorded state

    live_content

    content_served

  5. Domain monitor · First collection record

    Reachable

All retained availability observations24

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. 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-31 23:20:09.600237
    Evidence SHA-256
    fdac094cb4b92350d9f20b2c0fc69fdcaa33e7da7eb2d1063ea3f2bc257f29ef
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 23:20:09.600237
    Evidence reason
  2. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:36:02.000000
    Evidence SHA-256
    2d32866f9cb68e858e716398216de084644b0b0c56dd141a9fe2d6f514c325cc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:36:02
    Evidence reason
    alive_content
  3. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:36:02.000000
    Evidence SHA-256
    2d32866f9cb68e858e716398216de084644b0b0c56dd141a9fe2d6f514c325cc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:36:02
    Evidence reason
    alive_content
  4. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:56:09.000000
    Evidence SHA-256
    ab9e9780051424d6434b9b64552400f8da9a9b2a98d008e4cf6be7c0de0e0930
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:56:09
    Evidence reason
    alive_content
  5. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:56:09.000000
    Evidence SHA-256
    ab9e9780051424d6434b9b64552400f8da9a9b2a98d008e4cf6be7c0de0e0930
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:56:09
    Evidence reason
    alive_content
  6. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 00:04:49.000000
    Evidence SHA-256
    85cb9ee047fbe9860e7a5d6d1f992f02ed209f60aa91fdb398033a9aaed2ccc1
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 00:04:49
    Evidence reason
    alive_content
  7. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 00:04:49.000000
    Evidence SHA-256
    85cb9ee047fbe9860e7a5d6d1f992f02ed209f60aa91fdb398033a9aaed2ccc1
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 00:04:49
    Evidence reason
    alive_content
  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-30 22:35:15.875079
    Evidence SHA-256
    97b1f1aad91757df55a07aa8eadffa1ea48bf460a07a53a1e786c935a601fca5
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-30 22:35:15.875079
    Evidence reason
  9. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:05:32.000000
    Evidence SHA-256
    28088245285a73818eef271fa5a28c91a31e95de98e18cb93d357b55a3603d90
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:05:32
    Evidence reason
    alive_content
  10. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:05:32.000000
    Evidence SHA-256
    28088245285a73818eef271fa5a28c91a31e95de98e18cb93d357b55a3603d90
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:05:32
    Evidence reason
    alive_content
  11. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:05:54.000000
    Evidence SHA-256
    0adfcffdfe8329445c3554f7793a9ee1a12f386f48b8b1a4fdafd0b25aa72290
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:05:54
    Evidence reason
    alive_content
  12. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:05:54.000000
    Evidence SHA-256
    0adfcffdfe8329445c3554f7793a9ee1a12f386f48b8b1a4fdafd0b25aa72290
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:05:54
    Evidence reason
    alive_content
  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-29 17:14:29.775349
    Evidence SHA-256
    db74fcc6d756cb36943e7c7745a6a8737aaa6959c4a9679405e4f75391d96929
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-29 17:14:29.775349
    Evidence reason
  14. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:06:17.000000
    Evidence SHA-256
    01a7b8ecae4ee8cd56c262b6a2327e3a098bf8fec5ca16edbe9a55048be43504
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:06:17
    Evidence reason
    alive_content
  15. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:06:17.000000
    Evidence SHA-256
    01a7b8ecae4ee8cd56c262b6a2327e3a098bf8fec5ca16edbe9a55048be43504
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:06:17
    Evidence reason
    alive_content
  16. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 01:05:43.000000
    Evidence SHA-256
    d174fbd18310b9737c2836a43a210e6a6fabc715ce95e12630d9ad3988e73e1a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 01:05:43
    Evidence reason
    alive_content
  17. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 01:05:43.000000
    Evidence SHA-256
    d174fbd18310b9737c2836a43a210e6a6fabc715ce95e12630d9ad3988e73e1a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 01:05:43
    Evidence reason
    alive_content
  18. 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-28 17:03:14.895165
    Evidence SHA-256
    73d1f345e73e3fe3ec20cf30f9fc86221ba9885e7af8cdcc18189657c73b0d4e
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-28 17:03:14.895165
    Evidence reason
  19. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 13:13:23.000000
    Evidence SHA-256
    039d3e93638bcac9f34552571d0b762902472a916252e0d32fe0317f261bc9d4
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 13:13:23
    Evidence reason
    alive_content
  20. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 13:13:23.000000
    Evidence SHA-256
    039d3e93638bcac9f34552571d0b762902472a916252e0d32fe0317f261bc9d4
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 13:13:23
    Evidence reason
    alive_content
  21. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 01:30:46.000000
    Evidence SHA-256
    41d297b4d76802f0e1657421f54e3d4f9131d2fbf800f2ea1121e52a01d4e1dc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 01:30:46
    Evidence reason
    alive_content
  22. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 01:30:46.000000
    Evidence SHA-256
    41d297b4d76802f0e1657421f54e3d4f9131d2fbf800f2ea1121e52a01d4e1dc
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 01:30:46
    Evidence reason
    alive_content
  23. 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-27 17:45:11.000000
    Evidence SHA-256
    974f49ae0f88ef268ed913f7c7d2617205d8c5c8555455bc928292b30b96c395
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-27 17:45:11
    Evidence reason
  24. 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-27 17:45:11.000000
    Evidence SHA-256
    974f49ae0f88ef268ed913f7c7d2617205d8c5c8555455bc928292b30b96c395
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-27 17:45:11
    Evidence reason

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: 1 of 1
  • Threat Ingested
    wecbhsk.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Cloudflare Radar: Malicious · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 7 of 7
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 98
  • 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: 3/92
  • Cloudflare Radar: Malicious
    Cloudflare Radar classified this domain as Security threats, phishing, Security Risks, New Domains, DGA Domains
  • 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.
Notification RecordsSent Report Recorded Recorded: 1 of 1
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: Realtime Register B.V.. Abuse contacts: 1.
    • rtr-security-threats@realtimeregister.com
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

5 entries
  1. Abuse report sent

    PD-20261027-3BEE07 · Receipt 83884

    rtr-security-threats@realtimeregister.com
  2. URLScan

    Page captured

    View source
  3. Cloudflare Radar

    Phishing

    View source
  4. Added to PhishDestroy

    wecbhsk.com

    View source
  5. VirusTotal

    3/92 engine detections

    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

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 3 det. ChainPatrol URLQuery Report stored SSL Labs Certificate hostname mismatch CF Radar Malicious WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261027-3BEE07 Recipient: rtr-security-threats@realtimeregister.com
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.

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.

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

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. 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.

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.

  • 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

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 wecbhsk.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/wecbhsk.com"
  title="PhishDestroy threat report for wecbhsk.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>