Analysis of www.bybitgum.com shows an active high‑risk infrastructure that impersonates the Bybit brand. The domain was registered on February 21, 2026 through CSC Corporate Domains, Inc., and resolves to IP 43.132.83.231 located in Japan under ASN AS139341 (ACE). HTTP requests return a 302 redirect and the site presents a page titled “Buy”. Technical fingerprints include Nginx, OpenResty, React, Amazon Web Services, and client‑side integrations for Google Sign‑in, Apple Sign‑in, Yandex.Metrika, and Twitter Ads. The authoritative name servers are ns-1367.awsdns-42.org, ns-1618.awsdns-10.co.uk, ns-7.awsdns-00.com, and ns-7 (truncated). The TLS certificate is issued by TrustAsia Technologies, Inc. under the TrustAsia DV TLS RSA CA 2025. Reputation metrics are poor: Gridinsoft scores the domain 0/100, it appears on one security blocklist and is blocked by PhishDestroy. AlienVault OTX references the domain in sixteen threat‑intel pulses, and VirusTotal reports twelve detections out of ninety‑five scanners. The listed scam type is a crypto‑related scam targeting Bybit users. While the page content has not been independently verified, the convergence of brand impersonation, redirection behavior, low trust scores, and multiple vendor detections indicates a malicious operation. Defenders should block the domain at network perimeter, monitor DNS queries for the listed name servers, and add the IP address to threat‑intel feeds. Continuous re‑evaluation is advised as additional indicators may emerge.
Extracted from stored page analysis
Observed indicators
0 wallet · 1 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
Telegram
https://t.me/BybitEnglishStored page reference
IoC extraction recorded 2026-07-29 02:28:00 UTC
Detection-evasion evidence
Cloaking confirmed: scanners and visitors see different content
ObservedDifferent content was served to scanners and to visitors
The page served one response to a browser-like visitor and another to a crawler or security scanner. Cloaking exists only to keep reviewers away from the real landing page.
Stored cloaking flag
Observed
Cloaking type
redirect_split
Cloaking score
3/6
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-155321.invalid', port=80): Max retries exceeded with url: / (Caused by
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-155321.invalid', port=80): Max retries exceeded with url: / (Caused by
checked Oct 11, 2026
Time to First Unavailability17 days
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedFeb 26, 2026
DOM Analysisanalyzed Jul 9, 2026score 100/1001 brand signal
IoC Extractionscanned Jul 29, 20260 wallet · 1 Telegram IoC
Favicon Hash
ICANN OVERSIGHT
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
Accreditation is a contract, not a safety certification.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Accountability draft
Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
43.132.83.231
Network ASN
AS139341
Organization
ACE
Observed location
Osaka, JP
Server header
Openresty
Nameservers 1
ns-799.awsdns-35.net
Location describes the IP network.
TLS certificate
Issuer
TrustAsia Technologies, Inc. / TrustAsia DV TLS RSA CA 2025
Hostname coverage
Hostname coverage not recorded
Collection time
2026-03-15 08:11:17 UTC
Collection source
PhishDestroy collector
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:31:00 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-23 02:11:57 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 16 identified
Google Sign-in
A
Apple Sign-in
N
Nginx
Web serversReverse proxies
High-performance HTTP server and reverse proxy, known for stability and low resource usage.
R
React
JavaScript frameworks
JavaScript library for building user interfaces with component-based architecture.
O
OpenResty
Web servers
Web platform based on Nginx with LuaJIT for scalable web apps.
A
Amazon Web Services
PaaSIaaS
Cloud computing platform offering compute, storage, and networking services.
Y
Yandex.Metrika
Twitter Ads
Conversion and audience tracking pixel for paid campaigns on X (Twitter) — signals that the site runs paid X ads.
Google PageSpeed Insights — mobile performance audit of duplicate-disabled-155321.invalid· checked Mar 2, 2026
100
Good
Performance
FCP
0.81s
First Contentful Paint
LCP
0.81s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.81s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Domain Status Transition2026-09-25 01:31:10 UTC
Domain state transitioned from alive to dead.
Threat Response Pipeline
Discovery
Analysis
Monitoring
14 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
duplicate-disabled-155321.invalid detected and queued for full analysis
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Sep 25, 2026
Time to First Unavailability
396 hours elapsed from detection to the first unavailable observation.
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+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
5 evidence signal groups linked0 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
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 →
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches4
Same favicon hash or the same page title as this host.
(US)
