b.to - URL scan, 14 Aug 2026
MalwareAnalyzer by Cyble scanned b.to and returned a unknown verdict (score 0). 1 domain and 0 IPs were contacted. 2 malware samples communicate with this URL. This is a point-in-time observation from 14 Aug 2026; the page may have changed since.
Scan result
- Verdict: unknown (score 0) · Confidence 3%
- Scanned URL:
https://b.to/ - Domain: b.to
- Scan tier: fast · observed 2026-08-14 10:45:15 UTC
Malware communicating with this URL (2)
These samples were observed contacting or being served from b.to. Each links to its full analysis.
- 998ab20451d9d4322ccabe305b175adf90e81e72b0e0ac6699c6a338c50bb6ea - referenced ·
998ab20451d9d4322ccabe305b175adf· first seen 2026-08-14 - 0b9bc12d.pdf - referenced ·
34dcdb9e3e499a22a5cf5d8cb5e54c2e· first seen 2026-08-12
Why this verdict
- Target did not respond (DNS/connection failure or timeout); verdict from URL structure only
Observed indicators
- b.to
- https://b.to/
Other scans of b.to (1)
This host has been scanned before. Each scan is a separate observation, so a verdict here does not carry over to the others.
- 20 Aug 2026 - unknown
Questions about b.to
- Is b.to safe?
- The scan of b.to on 14 Aug 2026 reached no verdict either way (score 0). Too little was captured to judge it, which is an unknown rather than a pass.
- What malware is associated with b.to?
- 2 analysed samples communicate with this URL.
- How was b.to checked?
- A static pass resolved DNS, captured TLS and headers and followed the redirect chain, and where the fast tier allows, a headless browser rendered the page and recorded every request. Egress is SSRF-locked. Signatures that matched only page text are weighted far below one that matched a served file, because a page documenting malware matches the same rules.
Scanned at the fast tier - see how URL scanning works.
Scan another URL · Latest analyzed threats · All scans of b.to
Scanned on MalwareAnalyzer by Cyble · Open interactive scan