Cloudflare Radar
Scan report
Open reportPhishDestroy first recorded zh-bybit.my on 2026-11-22. Listed by external blocklists: MetaMask, SEAL.
Page title: “Bybit下载 - 官方App安卓iOS正版下载 | 新用户注册赠$30000 2026”
Listed by external blocklists: MetaMask, SEAL. Use caution — do not enter credentials or personal information.
Risk score, higher = worse · How this score works
Pick what happened and tick the steps as you go. The ticks are kept only in this browser.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
Recorded source summary
PhishDestroy first observed zh-bybit.my on Nov 22, 2026. The hostname explicitly references Bybit; stored content metadata identifies the same apparent target. The captured page title is “Bybit下载 - 官方App安卓iOS正版下载 | 新用户注册赠$30000 2026”. Current evidence score: 66/100 (high).
Positive findings are stored from 3 sources: MetaMask, SEAL, and URLScan. MetaMask and SEAL listed the hostname in the separate external-blocklist snapshot on Nov 22, 2026 at 15:20 UTC. URLScan returned a malicious verdict with score 100; scan metadata linked the capture to bybit and assigned phishing as its category on Nov 22, 2026 at 15:30 UTC. Additional recorded evidence: VirusTotal recorded 0 detections among 92 engines on Nov 19, 2026 at 12:02 UTC.
The collector marked the hostname reachable on Nov 22, 2026 at 15:31 UTC, but did not retain the HTTP response code. Registration records for the domain list Gname.com Pte. Ltd. as the registrar and Nov 18, 2026 as the creation date. Registration preceded first observation by 4 days. At collection time, the hostname resolved to 154.201.215.40 on AS132839 (POWER LINE HK CO., LIMITED). The recorded endpoint location is Hong Kong, HK. The stored server header is nginx/1.24.0 (Ubuntu). The evidence archive retains 3 visual captures from PhishDestroy, URLScan, and Cloudflare Radar. TLS metadata lists Let's Encrypt / YE1 as the certificate issuer with validity through Feb 16, 2027.
The content indicators and 3 positive source findings support the current Bybit impersonation and phishing classification. The target field identifies Bybit.
Scan report
Open reportPage capture
SHA-256 fa90e174…946e581
Separate stored monitor snapshot; does not replace the primary report record or establish current availability.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Stored page, network and scanner observations, grouped by source and observation time.
| Mail configuration | Spf lookups: 0 |
|---|---|
| Protective DNS results | Resolvers: 12; Blocked count: 0 |
| Crawler rules | Allow: /; Agents: *, Bingbot, msnbot, Googlebot, Baiduspider; Present: ✓; Disallow: /api/, /*.json$; Sitemaps: https://zh-bybit.my/sitemap.xml |
| Sitemap | URLS: https://zh-bybit.my/, https://zh-bybit.my/download.html, https://zh-bybit.my/features.html, https://zh-bybit.my/security.html, https://zh-bybit.my/faq.html; Present: ✓; URL count: 5 |
| Trackers | Requests: 2 |
| TLS connection | Alpn: http/1.1; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓ |
| Ports | Open: 80, 443 |
| Carbon | Bytes: 10029; Co2 grams: 0.0004; Cleaner than: 72 |
| DNS server | NS: (IP: 162.159.27.88; Host: b.share-dns.net), (IP: 172.64.53.25; Host: a.share-dns.com); Zone: zh-bybit.my |
| Quality | Cls: 0; Seo: 100; Si s: 2.38; Fcp s: 0.78; Lcp s: 0.78; Tbt ms: 0; Performance: 100; Accessibility: 91; Best practices: 100 |
| Location | IP: 154.201.215.40; ASN: 132839; Org: POWER LINE HK CO., LIMITED; City: Hong Kong; Country: HK |
| SSL | San: www.zh-bybit.my, zh-bybit.my; Bits: 256; Chain: zh-bybit.my, YE1, Root YE, ISRG Root X2, ISRG Root X1; Issuer: Let's Encrypt / YE1; Serial: 05CF4C274C8460B2DCE3C3A9E9A2CF9DC43A; SHA256: 789e03923eb13b109632a0b165c1097ec37e73264691ce4e0e1d8db60b0ee0ca; Subject: zh-bybit.my; Valid to: 2027-02-16T11:10:08Z; Valid from: 2026-11-18T11:10:09Z |
| DNS records | A: 154.201.215.40; NS: a.share-dns.com, b.share-dns.net; Soa: Nsname: a.share-dns.com; Hostmaster: master.share-dns.com; Serial: 1795003390; Refresh: 3600; Retry: 1200; Expire: 86400; Minttl: 600 |
| Dnssec | Ds: ✗; Rrsig: ✗; Dnskey: ✗ |
| Hsts | Message: Site does not serve any HSTS headers. |
| HTTP security policies | Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗ |
| Get IP | IP: 154.201.215.40; Family: 4 |
| Redirects | Chain: https://zh-bybit.my |
| Subdomains | Count: 1; Subdomains: www.zh-bybit.my |
| Tech stack | Technologies: Ubuntu, Nginx 1.24.0 |
| Page links | External: https://www.bybit.com/download/, https://www.bybit.com/register/; Internal: https://zh-bybit.my/download.html, https://zh-bybit.my/index.html, https://zh-bybit.my/features.html, https://zh-bybit.my/faq.html, https://zh-bybit.my/security.html; External count: 2; Internal count: 5 |
| Registration record | Registrar: Gname.com Pte. Ltd.; Registrar iana ID: 1923; Registrar URL: https://www.gname.com/; Created: 2026-11-18T11:52:26Z; Updated: 2026-11-18T12:02:19Z; Expires: 2027-11-18T11:52:26Z; Status: clientTransferProhibited https://icann.org/epp, addPeriod https://icann.org/epp; Nameservers: a9.share-dns.com, b9.share-dns.net; Dnssec: unsigned |
| HTTP headers | Headers: Server: nginx/1.24.0 (Ubuntu); Content type: text/html; charset=utf-8 |
PhishDestroy rates zh-bybit.my as high risk (evidence score 66/100) from the recorded evidence; it was first recorded on 2026-11-22. Listed by external blocklists: MetaMask, SEAL. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.
Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions on zh-bybit.my. A confirmed blockchain transaction cannot be reversed.
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.
Last checked
a.share-dns.coma9.share-dns.comb.share-dns.netb9.share-dns.netnsname: a.share-dns.comhostmaster: master.share-dns.comserial: 1795003390refresh: 3600retry: 1200expire: 86400minttl: 600Location describes the IP network.
789e03923eb13b109632a0b165c1097ec37e73264691ce4e0e1d8db60b0ee0cawww.zh-bybit.myzh-bybit.mySaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
www.zh-bybit.myDomain recordGoogle PageSpeed Insights — mobile performance audit of zh-bybit.my ·
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://zh-bybit.my/https://zh-bybit.my/Server: nginx/1.24.0 (Ubuntu)Content-Type: text/html; charset=utf-8Content-Encoding: gzipkeep-alivegziptext/html; charset=utf-8Sun, 22 Nov 2026 15:35:01 GMTW/"6afdbee3-272d"Wed, 18 Nov 2026 15:06:11 GMTnginx/1.24.0 (Ubuntu)chunkedValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Network requests: 3 SHA-256 hashes: 3 URLScan scan:
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-22 15:35 UTC.
Open this scan on URLScan 01a203e1-4063-733c-8906-936ca02b1d3d ↗
Loads saved data; the suspicious site is not opened.
| # | Network request | HTTP method · status | Type | Uncompressed size | Response body SHA-256 |
|---|
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Reachable
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.
No retained observations are recorded.
Recorded events: 9. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Lifecycle
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
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| ID | Stored data |
|---|
112 stored lookalike domains
Names that imitate the brand, found by dnstwist. A similar name alone does not prove the same owner.
A similar name alone does not prove fraud. Send the list to services that check each address themselves. Report a domain as phishing only if you saw a fake page on it.
Where to send it:
Nothing matches. Clear the search or choose another filter.
Showing 12 of 112
Showing 100 of 112
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
zh-bybit.my 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.
The draft stays only with you.
First secure your money: call your bank or revoke wallet approvals. Immediate steps →
Emergency help from security researchers when a crypto wallet is being drained right now.
Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.
Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.
Forward scam emails and text messages to the National Cyber Security Centre, which takes down the malicious sites it finds.
Emailreport@phishing.gov.uk Text messages7726Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.
Forward phishing emails to the Anti-Phishing Working Group.
Emailreportphishing@apwg.orgNational Cyber Crime Reporting Portal. For financial fraud, also call the 1930 helpline straight away.
Helpline1930Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
zh-bybit.my)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive
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.