Skip to security report
Dangerous

Phishing copy of Telegram

hbwkaos.com favicon
Domain security and threat intelligence

hbwkaos.com

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

hbwkaos.com: VirusTotal 0/92 detections. First recorded 2026-10-26. Registrar: GMO Internet Group, Inc. d/b/a Onamae.com.

Page title: “Telegram Web”

More about the sources
Recorded security signals

Use caution — do not enter credentials or personal information.

Stored PhishDestroy threat listing
Registrar
GMO Internet Group
Resolved IP
South Korea43.133.87.107Shenzhen Tencent Computer Systems Company Limited
Registered
2026-10-23
First seen by PhishDestroy
2026-10-26
Page captures
open gallery
Reports sent
view timeline
2026-10-26 1 Report Sent

Risk score, higher = worse · How this score works

What to do right now

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

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

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

ABUSE NOTICE · 7D+ 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 abuse@tencent.com. The latest stored availability evidence still shows the domain reachable; 27 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
27 days
Reports sent
1
Latest case ID
PD-20261026-D364AD
Current status
Observed active at latest stored check

Analysis

High
Scam type (automated label)
Impersonation
Hosting
South Korea43.133.87.107Shenzhen Tencent Computer Systems Company Limited
Registrar
GMO Internet Group
Registered
2026-10-23
Page captures
10

PhishDestroy analysis, earlier unreviewed version

Overview

The captured screenshot from 2026-10-26 shows a Telegram sign-in page in Chinese offering QR code login and phone number login. PhishDestroy listed hbwkaos.com under the classification Impersonation, an impersonation phishing page, based on its automated assessment and an intake assessment on 2026-10-26. It was first seen by PhishDestroy on 2026-10-26, three days after its 2026-10-23 registration.

How the scam works

The page instructed visitors to open Telegram on their phone, go to settings, devices and desktop linking, then point the camera at the screen, with a fallback link to log in by phone number. Anyone following those steps against an attacker-controlled page hands over the login session or phone number, enabling credential theft and account takeover as a category risk of QR and phone-based impersonation. The captured page metadata also carried Telegram branding to reinforce the disguise.

Evidence

The captured screenshot shows a Chinese-language Telegram login screen with a QR sign-in heading, three numbered setup steps, and a phone-number login link, observed on 2026-10-26. URLScan judged the page malicious with an ML score of 99 and an overall phishing score of 100 on 2026-10-26, Cloudflare Radar returned a malicious phishing verdict that day, and the fetched request returned HTTP 200 with no cross-site redirect. VirusTotal did not flag it, Spamhaus held no listing, external blocklists recorded no entries, and OTX held zero pulses, all checked on 2026-10-26; those negatives are not proof of safety. Site inspection recorded a Telegram Web style script stack with AppStorage, I18n, AccountController and cryptoMessagePort globals, no third-party trackers, and 10 distinct script SHA256 hashes, one beginning a2382157448b, for campaign pivoting.

Infrastructure

The domain was registered through GMO Internet Group, Inc. d/b/a Onamae.com on 2026-10-23 and recorded behind an nginx server, with the serving address captured on 2026-10-26. Notable weaknesses: Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy and COOP/COEP/CORP all absent; HSTS present without subdomain coverage; no SPF, DKIM or DMARC; DNSSEC unsigned; CAA present; TLS 1.3, TLS_AES_256_GCM_SHA384, forward secrecy, ALPN h2.

What to do

If you submitted a phone number or scanned the QR code, change your password on the genuine Telegram service, enable two-factor authentication, and review signed-in devices, signing out anything unfamiliar. Treat any follow-up messages asking for codes or payments with suspicion. For defenders, block hbwkaos.com at proxy and DNS layers and track further captures tied to the same campaign.

Source evidence 4 sources

URLScan

Malicious

SHA-256 27cf056e…e427354

Open report
URLScanOriginal source recordObserved: 19 fields
Separate monitor record

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

UUID
01a177f3-ac5b-719c-bb48-819fdc59c195
Enriched at
2026-10-27T09:21:51Z
Source timestamps
Urlscan enriched at: 2026-10-27 10:21:51

PhishDestroy DOM

10 / 100 · heuristic score · 2 brand references · 1 classification

Content heuristic only; not the final score

Open report
Technical metadata

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

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

AI title
hbwkaos.com — Telegram QR code phishing login
AI description
PhishDestroy assesses hbwkaos.com as an impersonation phishing page presenting a Telegram QR login to capture credentials.
AI summary
Overview The captured screenshot from 2026-10-26 shows a Telegram sign-in page in Chinese offering QR code login and phone number login. PhishDestroy listed hbwkaos.com under the classification Impersonation, an impersonation phishing page, based on its automated assessment and an intake assessment on 2026-10-26. It was first seen by PhishDestroy on 2026-10-26, three days after its 2026-10-23 registration. How the scam works The page instructed visitors to open Telegram on their phone, go to settings, devices and desktop linking, then point the camera at the screen, with a fallback link to log in by phone number. Anyone following those steps against an attacker-controlled page hands over the login session or phone number, enabling credential theft and account takeover as a category risk of QR and phone-based impersonation. The captured page metadata also carried Telegram branding to reinforce the disguise. Evidence The captured screenshot shows a Chinese-language Telegram login screen with a QR sign-in heading, three numbered setup steps, and a phone-number login link, observed on 2026-10-26. URLScan judged the page malicious with an ML score of 99 and an overall phishing score of 100 on 2026-10-26, Cloudflare Radar returned a malicious phishing verdict that day, and the fetched request returned HTTP 200 with no cross-site redirect. VirusTotal did not flag it, Spamhaus held no listing, external blocklists recorded no entries, and OTX held zero pulses, all checked on 2026-10-26; those negatives are not proof of safety. Site inspection recorded a Telegram Web style script stack with AppStorage, I18n, AccountController and cryptoMessagePort globals, no third-party trackers, and 10 distinct script SHA256 hashes, one beginning a2382157448b, for campaign pivoting. Infrastructure The domain was registered through GMO Internet Group, Inc. d/b/a Onamae.com on 2026-10-23 and recorded behind an nginx server, with the serving address captured on 2026-10-26. Notable weaknesses: Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy and COOP/COEP/CORP all absent; HSTS present without subdomain coverage; no SPF, DKIM or DMARC; DNSSEC unsigned; CAA present; TLS 1.3, TLS_AES_256_GCM_SHA384, forward secrecy, ALPN h2. What to do If you submitted a phone number or scanned the QR code, change your password on the genuine Telegram service, enable two-factor authentication, and review signed-in devices, signing out anything unfamiliar. Treat any follow-up messages asking for codes or payments with suspicion. For defenders, block hbwkaos.com at proxy and DNS layers and track further captures tied to the same campaign. Useful links urlscan.io scan and screenshot: https://urlscan.io/result/01a17800-bf54-74ab-8792-94cd52355dbd/ Cloudflare Radar report: https://radar.cloudflare.com/scan/17ee397e-d9d7-48dd-ac71-51d674a7dc25 URLQuery report: https://urlquery.net/report/e4f3c0cf-32e1-41f4-acc8-18b06412e085 Stored capture screenshot: https://i.ibb.co/cKyD1zdS/f65846ad1a67.png Cloudflare Radar screenshot (2026-10-26T11:34:42Z): https://screenshots.phishdestroy.io/cf/17ee397e-d9d7-48dd-ac71-51d674a7dc25.png URLQuery screenshot: https://screenshots.phishdestroy.io/uq/e4f3c0cf-32e1-41f4-acc8-18b06412e085.png URLScan screenshot (2026-10-26T11:23:51Z): https://screenshots.phishdestroy.io/us/01a177f3-ac5b-719c-bb48-819fdc59c195.png URLScan capture report: https://urlscan.io/result/01a177f3-ac5b-719c-bb48-819fdc59c195/ URLScan screenshot (2026-10-26T11:34:56Z): https://screenshots.phishdestroy.io/us/01a177fd-d572-770c-81eb-73df1c6f16e2.png URLScan capture report: https://urlscan.io/result/01a177fd-d572-770c-81eb-73df1c6f16e2/ URLScan screenshot (2026-10-26T11:38:52Z): https://screenshots.phishdestroy.io/us/01a17801-786a-73fd-94ed-34eb08f893d6.png URLScan capture report: https://urlscan.io/result/01a17801-786a-73fd-94ed-34eb08f893d6/ VirusTotal report: https://www.virustotal.com/gui/domain/hbwkaos.com Google Safe Browsing status: https://transparencyreport.google.com/safe-browsing/search?url=hbwkaos.com Archived copy: https://web.archive.org/web/20261026113354/https://hbwkaos.com/ Report phishing to Google: https://safebrowsing.google.com/safebrowsing/report_phish/ Site owner? Request a review: https://phishdestroy.io/appeals/
AI generated by
mimo-flash
AI generated at
2026-10-26T20:19:17Z
Revision
67f4065f00a67e870db59cf308aedc13dfa6e104fc5f5890182f1b7f2da782fe
Mode
stored
Interpretation
Earlier stored analysis, not reviewed; text generation time is separate from source observation dates.

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

Collected source details

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

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

Mail configuration

SPF lookups
0

CAA records

Domain
hbwkaos.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
6910

Page title and metadata

Open Graph URL
https://web.telegram.org/k/
Page title
Telegram Web
Open Graph type
website
Open Graph image
assets/img/android-chrome-192x192.png?v=jw3mK7G9Ry
Open Graph title
Telegram Web
Theme color
#ffffff
Description
Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed.
Canonical URL
https://web.telegram.org/
Open Graph description
Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed.

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
269
TLS
307
Waiting
596
Connection
298
Download
0
Response time, ms
1470

TLS connection

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

Ports

Open ports
  • 22
  • 80
  • 443

Carbon estimate

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

DNS servers

Nameservers
  • IP address
    172.64.53.25
    Host
    a.share-dns.com
  • IP address
    162.159.27.88
    Host
    b.share-dns.net
DNS zone
hbwkaos.com

Location

IP address
43.133.87.107
ASN
132203
Organization
Shenzhen Tencent Computer Systems Company Limited
City
Seoul
Country
KR

TLS certificate

Issuer
Let's Encrypt / YR1
Subject
hbwkaos.com

DNS records

A
  • 43.133.87.107
NS
  • b.share-dns.net
  • a.share-dns.com
SOA
Primary nameserver
a.share-dns.com
Hostmaster
master.share-dns.com
Serial
1792745282
Refresh, seconds
3600
Retry, seconds
1200
Expiry, seconds
86400
Minimum TTL, seconds
600

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

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

HTTP security policies

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

IP lookup

IP address
43.133.87.107
IP version
4

Redirects

Redirect chain
  • https://hbwkaos.com

Registration record

Registrar
GMO Internet Group, Inc. d/b/a Onamae.com
Registered
Updated
Expires
Status
  • clientTransferProhibited https://icann.org/epp
Nameservers
  • a9.share-dns.com
  • b9.share-dns.net

HTTP headers

Response headers
Server
nginx
Content-Type
text/html
Strict-Transport-Security
max-age=31536000
Original source fields · JSON
Mail configuration
Spf lookups: 0
Caa records
Domain: hbwkaos.com
Protective DNS results
Resolvers: 12; Blocked by: CloudFlare Family; Blocked count: 1
Web archive observations
Last: 2026-10-26T11:33:54Z; First: 2026-10-26T11:33:54Z; Changes: 0; Days archived: 1; Avg page bytes: 6910
Page title and metadata
Ogurl: https://web.telegram.org/k/; Title: Telegram Web; Ogtype: website; Ogimage: assets/img/android-chrome-192x192.png?v=jw3mK7G9Ry; Ogtitle: Telegram Web; Themecolor: #ffffff; Description: Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed.; Canonicalurl: https://web.telegram.org/; Ogdescription: Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed.
Forms and mixed content
Third party scripts: 0
Status
Up: ✓; Code: 200; Timings: DNS: 269; TLS: 307; Wait: 596; Connect: 298; Download: 0; Response ms: 1470
TLS connection
Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1.1, TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓
Ports
Open: 22, 80, 443
Carbon
Bytes: 15547; Co2 grams: 0.0006; Cleaner than: 62
DNS server
NS: (IP: 172.64.53.25; Host: a.share-dns.com), (IP: 162.159.27.88; Host: b.share-dns.net); Zone: hbwkaos.com
Location
IP: 43.133.87.107; ASN: 132203; Org: Shenzhen Tencent Computer Systems Company Limited; City: Seoul; Country: KR
SSL
Issuer: Let's Encrypt / YR1; Subject: hbwkaos.com
DNS records
A: 43.133.87.107; NS: b.share-dns.net, a.share-dns.com; Soa: Nsname: a.share-dns.com; Hostmaster: master.share-dns.com; Serial: 1792745282; Refresh: 3600; Retry: 1200; Expire: 86400; Minttl: 600
Dnssec
Ds: ✗; Rrsig: ✗; Dnskey: ✗
Hsts
Header: max-age=31536000; Message: HSTS header does not include all subdomains.
HTTP security policies
Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: ✗; Stricttransportpolicy: max-age=31536000; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗
Get IP
IP: 43.133.87.107; Family: 4
Redirects
Chain: https://hbwkaos.com
Registration record
Registrar: GMO Internet Group, Inc. d/b/a Onamae.com; Created: 2026-10-23T08:45:43Z; Updated: 2026-10-23T08:45:53Z; Expires: 2027-10-23T08:45:43Z; Status: clientTransferProhibited https://icann.org/epp; Nameservers: a9.share-dns.com, b9.share-dns.net
HTTP headers
Headers: Server: nginx; Content type: text/html; Strict transport security: max-age=31536000
Network Security Intelligence
CF Cloudflare Radar Verdict Malicious
DGA Domains Phishing Security Risks Phishing Security threats New Domains

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Page captures (10)

All capture links and hashes (10)
hbwkaos.com: phishdestroy risk analysis, risk score 65/100 (high); not yet listed by external security vendors.
Social preview card hbwkaos.com: phishdestroy risk analysis, risk score 65/100 (high); not yet listed by external security vendors. v ae0751e87ab6

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Telegram report ↗
IP Reputation South Korea43.133.87.107 0/100abuse score · abuse reports about this server's IP address, not about the domain; higher = worse This IP address has not been reported to the abuse database yet, but the domain itself is recognized as phishing. 0 reports checked 2026-10-26
Registrar GMO Internet Group
Hosting abuse contact abuse@tencent.com Shenzhen Tencent Computer Systems Company Limited · AS132203
RegistrationCreated 2026-10-23 (30d · New) — Expires 2027-10-23
Technical detailsProvenance & timestamps
First Detected2026-10-26
DOM Analysisanalyzed 2026-10-26score 10/1002 brand signals
Submitted URLhttps://hbwkaos.com/
Favicon Hash
Case ID
Observed page title
Telegram Web
Automated brand references
Argent Telegram
TLS Certificate
Issued by Let's Encrypt / YR1 · stored validity ends in 59 days

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
South Korea43.133.87.107
Network ASN
AS132203
AS name
TENCENT-NET-AP-CN - Tencent Building, Kejizhongyi Avenue, CN
Organization
Shenzhen Tencent Computer Systems Company Limited
Observed location
South KoreaSeoul, KR
Server header
nginx

Nameservers 4

  • a.share-dns.com
  • a9.share-dns.com
  • b.share-dns.net
  • b9.share-dns.net

SOA

  • nsname: a.share-dns.com
  • hostmaster: master.share-dns.com
  • serial: 1792745282
  • refresh: 3600
  • retry: 1200
  • expire: 86400
  • minttl: 600

Registrar abuse contact VirusTotal WHOIS

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YR1
Valid from
2026-10-23 08:15:14
Valid until
2027-01-21 08:15:13
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint0db1f8ee4398d846b0dd75a01ea771b08d0175d6ee1c1718ce2050e36eab3232
Certificate names · 2 SANs
  • hbwkaos.com
  • itelsgiae.com

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

Technologies · 2 identified
Open complete records

Archived Evidence

Wayback Machine Snapshot
View Archive

Saved snapshots 1

PageSpeed (mobile): 45

Google PageSpeed Insights — mobile performance audit of hbwkaos.com ·

45
Poor
Performance
FCP
3.29 s
First Contentful Paint
LCP
4.8 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
1067 ms
Total Blocking Time
SI
10.67 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

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

Archived HTTP response HTTP 200
Requested URL: https://hbwkaos.com/
Telegram Web
Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed.
Response
HTTP 200
HTML body
15.2 KB
Compressed
5.6 KB
Links
0 internal · 0 external
Detected technologies
nginx
Selected response headers
Server: nginx
Content-Type: text/html
Content-Encoding: gzip
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Favicon fingerprint: 926cc27874313cb1f3a6fc23d89d98d5cde0e63a3bfd360beb5d02e9c62ea38e
Open Graph title: Telegram Web
Open Graph description: Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed.
Saved response-header values · 10
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Mon, 26 Oct 2026 11:33:55 GMT
Etag
W/"6ad405d5-3cbb"
Last-Modified
Sat, 17 Oct 2026 23:33:41 GMT
Server
nginx
Strict-Transport-Security
max-age=31536000
Transfer-Encoding
chunked
Vary
Accept-Encoding

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

Registration & observation details2

Availability observations

Last reachable observation
Last content observation

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

All stored data116
Open complete records

Captured network requests

Network requests: 265 SHA-256 hashes: 255 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:57 UTC.

Open this scan on URLScan 01a17800-bf54-74ab-8792-94cd52355dbd ↗

Stored observation history7

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

  1. Availability monitor · Recorded state

    Serving page content

    page content returned

  2. Availability monitor · Recorded state

    Serving page content

    page content returned

  3. Availability monitor · Recorded state

    Serving page content

    page content returned

  4. Availability monitor · Recorded state

    Serving page content

    page content returned

  5. Availability monitor · Recorded state

    Serving page content

    page content returned

Earlier observations 2
  1. Availability monitor · Recorded state

    Serving page content

    page content returned

  2. Availability monitor · Recorded state

    Serving page content

    page content returned

All retained availability observations113
Open complete records

Threat Response Pipeline

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

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
  • Threat Ingested
    hbwkaos.com detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · Cloudflare Radar: Malicious · Automated brand label: Telegram · Forensic Evidence Collected · Technical Analysis Recorded recorded
Notification RecordsSent Report Recorded recorded
  • Sent Report Recorded
    Stored record of an abuse report about this domain; registrar at the time: GMO Internet Group, Inc. d/b/a Onamae.com. Abuse contacts: 1.
    • abuse@tencent.com
Publication & AvailabilityDestroyList Published recorded

Recorded activity

5 entries

Lifecycle

  1. Domain registered
  2. Added to PhishDestroy+3 d 2 h
  3. First abuse report sent+8 min

Reported 3 d 2 h after registration

  1. Abuse report sent

    PD-20261026-D364AD · Receipt 83408

    abuse@tencent.com
    +1 min
  2. URLScan

    Page captured

    +5 min
  3. Cloudflare Radar

    Phishing

    same minute
  4. Wayback Machine

    Page archived

    same minute
  5. Added to PhishDestroy

    hbwkaos.com

How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

All stored records by source

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

Download all records as JSON

Check for cloaking

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

hbwkaos.com

Evidence & External Reports

Submitted Evidence Snapshot
Sent: Ledger records: 1 Case ID: PD-20261026-D364AD Recipient: abuse@tencent.com
PDF notice generated
Deep Analysis

Were You Affected by This Site?

You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Where to report

The draft stays only with you.

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

More: international and crypto channels

Official reporting routes

More official reporting routes
SEAL 911 Worldwide

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

FTC ReportFraud United States

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

IdentityTheft.gov United States

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

CISA United States

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

CSIRTs Network European Union

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

FIRST Worldwide

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

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

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

After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
  • Downloaded a file — do not open it and scan the device with security software
  • Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
  • Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
  • Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
  • Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including hbwkaos.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

Stay Informed, Stay Safe

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

Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials. Learn more about recovery fraud →
About this reportSources, observation dates and corrections

This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html
<iframe
  src="https://phishdestroy.io/embed/domain/hbwkaos.com"
  title="PhishDestroy threat report for hbwkaos.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>