VirusTotal
checked — no detections recorded
ReportInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“BTC 猜涨跌”
Assessment based on the stored source evidence below. Review sources →
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
checked — no detections recorded
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
no community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
stored report
Report A preserved page image documents what the collector received; a capture is not a safety verdict.
Report stored; verdict not recorded
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Stored narrative · generated . Provider checks below retain their own observation dates.
On 2026-10-15, bet.bi was observed as internally listed by PhishDestroy, according to a recorded source observation. This observation provides a useful reference point for evaluating the domain's infrastructure alongside other recorded evidence.
VirusTotal checked bet.bi on 2026-09-14, recording 0 detections out of 92 scanners. PhishDestroy internally listed the domain as of 2026-10-15. The domain was registered with Dynadot on 2024-02-22, and its SSL certificate was issued by Let's Encrypt / YE2, with scanning performed on 2026-10-15.
The VirusTotal record contains external scanning results, documenting how bet.bi was measured by multiple detection engines for potential security issues. PhishDestroy provides a publisher-owned listing, which is a distinct internal catalogue entry for the domain. These sources offer varied technical and security perspectives, allowing for comparison of network performance and catalogue status across different dates.
For bet.bi, preserve the VirusTotal scan results and the PhishDestroy internal listing for future reference and comparison. Review subsequent records from these sources to track any changes in detection outcomes or catalogue entries. Retain technical measurements such as pagespeed scores to support ongoing assessments of the domain's infrastructure.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Local archived 2026-10-15 06:02:25 UTCeoin.ns.cloudflare.comgail.ns.cloudflare.comLocation describes the IP network.
73dd3888ce0667d198569979d4cb8231ffd67c17345b47cf7b14eea1ca995438Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of bet.bi · checked Oct 15, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
https://www.bet.bi/Content-Encoding: gzipContent-Type: text/html; charset=utf-8Server: waf.bibytesgzip342default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self' data:; connect-src 'self'text/html; charset=utf-8Thu, 15 Oct 2026 04:02:23 GMTstrict-origin-when-cross-originwaf.bimax-age=31536000; includeSubDomainsMISSnosniffSAMEORIGIN3dcce2bc3f03a8eaabdb70d41; mode=blockValues retained by the collector; long values may be shortened during collection.
75.2.97.28.5 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
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