Skip to security report
Analytics Dashboard
Domain security and threat intelligence
white-bit.global favicon

white-bit.global

In short

white-bit.global is a blocklisted domain detected by PhishDestroy on 2026-03-09. Risk: high (63/100). Status: Content unavailable. Hosting: Cloudflare, Inc. VirusTotal: 1/94 engines flag it. Do not enter credentials or connect a wallet.

Resolved IP
172.67.70.38
PhishDestroy assessment High
Availability Content unavailable Content was unavailable in the latest observation Observed · HTTP probe
Risk signals
VirusTotal detections: 1/94 Scam type: Generic Phishing
Mar 9, 2026 CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 1. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
1 / 94
engine detections
Google Safe Browsing
No threat flag
Page captures
2
open gallery
Source evidenceVirusTotal 1 / 94 7 sources

VirusTotal

1 / 94 engine detections

Open report

PhishStats

checked — no match recorded

OTX

no community references

Open report

DNS blocks

14 checked — no blocks

Google Safe Browsing

No threat flag

Open report

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

Analysis

High
VirusTotal
1 / 94
Page captures
2
Page captures Source results

PhishDestroy threat report

The domain white-bit.global is a generic phishing site designed to deceive users into disclosing sensitive information. It does not impersonate a specific brand or employ a known crypto drainer kit. As of the latest verification, white-bit.global has been taken offline, though it previously posed an elevated risk of credential theft or other fraudulent activity.

Technical analysis of white-bit.global reveals limited but notable indicators. The domain was flagged by 1 of 95 VirusTotal security vendors, including SOCRadar, and appears on 3 security blocklists: PhishDestroy, MetaMask, and SEAL. It was created on March 09, 2026, and resolved to the IP address 172.67.70.38, hosted by Cloudflare, Inc. (AS13335) in the US. No SSL certificate was detected, and the observed page title was 'Just a moment...'. Technologies identified include Cloudflare Browser Insights, Cloudflare, and HTTP/3. The registrar and SSL issuer details are not available.

Users who may have interacted with white-bit.global should take immediate steps to secure their accounts. If login credentials were entered, change passwords for all affected accounts and enable two-factor authentication (2FA) where possible. Monitor accounts for unauthorized activity and report any suspected fraud to financial institutions or relevant platforms. To report the phishing domain, submit it to Google Safe Browsing, PhishTank, or local cybersecurity authorities for further investigation.

Questions about white-bit.global

Is white-bit.global legit?

No. PhishDestroy classifies white-bit.global as a blocklisted domain (risk: high, 63/100); it was first detected on 2026-03-09. VirusTotal: 1/94 engines flag it. Treat the site as unsafe.

Is white-bit.global safe to connect a wallet?

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

What should I do if I used white-bit.global?

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

Explore

Forensic Intelligence

External Scripts 1
https://performance.radar.cloudflare.com/beacon.js
Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 2 captures

Primary capture 1 / 2
SourcePrimary capture
Recorded2026-03-09 17:26 UTC
StateStored capture
Position1 / 2
Open capture Wayback Download

Domain details

Domain
URLScan verdict Analysis completed score 0 report ↗
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Time to First Unavailability 6h
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 DetectedMar 9, 2026
DOM Analysisanalyzed Apr 10, 2026score 63/100
Submitted URLhttps://white-bit.global/
Favicon Hash
TLS Certificate
Issued by Let's Encrypt · stored validity ends in 86 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
172.67.70.38
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • amy.ns.cloudflare.com
  • rustam.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt
Valid until
2026-06-04 00:00:00
Validity
Stored certificate expired
Collection time
2026-03-15 05:41:46 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.

viewdns.info · 172.67.70.38rapiddns.io

Latest Classified Outcome 2026-10-21 14:53:36 UTC

Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Unknown Probe Inconclusive 20% 2026-10-21 01:10:34 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-04-22 04:24:19 UTC current episode first observed: 2026-09-30 16:14:55 UTC observed RIP window: 2026-04-22 04:24:19 UTC → 2026-09-30 16:14:55 UTC · 3,875.84h midpoint estimate ≈ 2026-07-11 22:19:37 UTC · precision very low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

1 / 94 security vendors flagged this domain
View on VT
Last analyzed
SOCRadar
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of white-bit.global · checked Mar 9, 2026

87
Needs Work
Performance
FCP
0.77s
First Contentful Paint
LCP
2.56s
Largest Contentful Paint
CLS
0.004
Cumulative Layout Shift
TBT
395ms
Total Blocking Time
SI
1.31s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Registration & observation details8

Availability observations

Last reachable observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
3875.84
Estimate basis
Bounded by observations
Estimate precision
very_low

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

Check for cloaking

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

No cloaking flag in this check

unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='white-bit.global', port=80): Max retries exceeded with url: / (Caused by NewConnectionErro

white-bit.global
Stored observation history11

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

    Unknown→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

Earlier observations 6
  1. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

Recorded activity

3 entries
  1. VirusTotal

    1/94 engine detections

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. Added to PhishDestroy

    white-bit.global

    View source

Community reports

Reported by 1 community member, first seen Mar 9, 2026

Stored reports
1
Unique reported URLs
1
Accepted1

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 1 det. ChainPatrol URLQuery Report stored SSL Labs CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
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?

4 evidence signal groups linked 0 stored notification records Content unavailable

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 →

Report to Your Local Authorities

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

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

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

What should I do immediately?

Urgent

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

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

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

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

Live Threat Feed Appeal This Listing
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.

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/white-bit.global"
  title="PhishDestroy threat report for white-bit.global"
  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>