c.to - URL scan, 12 Aug 2026
MalwareAnalyzer by Cyble scanned c.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 12 Aug 2026; the page may have changed since.
Scan result
- Verdict: unknown (score 0) · Confidence 3%
- Scanned URL:
https://c.to/ - Domain: c.to
- Scan tier: fast · observed 2026-08-12 18:53:50 UTC
Malware communicating with this URL (2)
These samples were observed contacting or being served from c.to. Each links to its full analysis.
- 54808d28c720599d8588557fc11bba5c90bdc65e8004483bf5f2c560a50d7f07 - referenced ·
54808d28c720599d8588557fc11bba5c· first seen 2026-08-12 - d2788288608b68197e014997020e800dce935c2e66911fde80c8a256a243523b - referenced ·
d2788288608b68197e014997020e800d· first seen 2026-08-11
Why this verdict
- Target did not respond (DNS/connection failure or timeout); verdict from URL structure only
Observed indicators
- c.to
- https://c.to/
Other scans of c.to (2)
This host has been scanned before. Each scan is a separate observation, so a verdict here does not carry over to the others.
- 24 Aug 2026 - unknown
- 20 Aug 2026 - unknown
Questions about c.to
- Is c.to safe?
- The scan of c.to on 12 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 c.to?
- 2 analysed samples communicate with this URL.
- How was c.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 c.to
Scanned on MalwareAnalyzer by Cyble · Open interactive scan