s.to - URL scan, 22 Aug 2026
MalwareAnalyzer by Cyble scanned s.to and returned a unknown verdict (score 0). 1 domain and 0 IPs were contacted. 124 malware samples communicate with this URL. This is a point-in-time observation from 22 Aug 2026; the page may have changed since.
Scan result
- Verdict: unknown (score 0) · Confidence 3%
- Scanned URL:
https://s.to/ - Domain: s.to
- Scan tier: fast · observed 2026-08-22 04:03:57 UTC
Malware communicating with this URL (124)
These samples were observed contacting or being served from s.to. Each links to its full analysis.
- d627a1b1c264ce2ca13a4311553e7b26a8d26cf324f08c1746f4b6fe9f6c72fb - referenced ·
d627a1b1c264ce2ca13a4311553e7b26· first seen 2026-08-22 - 78c218392ec1fe5c07c513ecf08c367ebf8ce580f6f89e8c34d7616814a01830 - referenced ·
78c218392ec1fe5c07c513ecf08c367e· first seen 2026-08-22 - ae256bf85c72e951899cb3111db974c2aa61331b36515bff842f2d0e3dce5cfe - referenced ·
ae256bf85c72e951899cb3111db974c2· first seen 2026-08-21 - ded03563148c48ce1c10eaef4001a1d35725c56e794f8ff1dec6c50a8559fb2f - referenced ·
ded03563148c48ce1c10eaef4001a1d3· first seen 2026-08-21 - 6fd4d37d8bfdc142b39892133b1c6449528964d979fc1628ca299c65aa7381e8 - referenced ·
6fd4d37d8bfdc142b39892133b1c6449· first seen 2026-08-21 - 1b5c3dbe1674b2391ab25778d5cfdac6520453d8644c460a3f0f1e2e3da95433 - referenced ·
1b5c3dbe1674b2391ab25778d5cfdac6· first seen 2026-08-21 - 245fa03718f0dfda08a053a3511a13a8abbbc5858e04fc88f7ddb324e5a36100 - referenced ·
245fa03718f0dfda08a053a3511a13a8· first seen 2026-08-21 - e624277ee8ad5bc5271e7cc72e3c2a8b79e00a32486d7d627d8e1a4dcc437f71 - referenced ·
e624277ee8ad5bc5271e7cc72e3c2a8b· first seen 2026-08-21 - f095590b142883b0e0d11109f3e32b55934beadb8d8b807e80ea617f44324ea7 - referenced ·
f095590b142883b0e0d11109f3e32b55· first seen 2026-08-21 - 97b35913a2ef64bb57b7d8e1773410b07ff58e6a5248d9e06e46a26518be3d23 - referenced ·
97b35913a2ef64bb57b7d8e1773410b0· first seen 2026-08-21 - e3a5ebce1b5342d02c1f51a6b25650137479b94ec8097e1709dbcfab2f89d6b6 - referenced ·
e3a5ebce1b5342d02c1f51a6b2565013· first seen 2026-08-21 - cc3b913442d9f6009c246c158fe5ee1341d759e72f0eab0757e2a9991957a532 - referenced ·
cc3b913442d9f6009c246c158fe5ee13· first seen 2026-08-21 - 4072ebecc3adbf74e00f2e9fb349ea295cd329e195e2c493eeaf1f0898a29cc4 - referenced ·
4072ebecc3adbf74e00f2e9fb349ea29· first seen 2026-08-21 - 0e61593afd2fdef513678be152ba41e1de8ba42b913d22df50ef6f60320546e8 - referenced ·
0e61593afd2fdef513678be152ba41e1· first seen 2026-08-21 - adaa57934025cbdfe0c1c59ff2b5f827abefbb22460e1e1a7121ddf7574f689c - referenced ·
adaa57934025cbdfe0c1c59ff2b5f827· first seen 2026-08-21
Why this verdict
- Target did not respond (DNS/connection failure or timeout); verdict from URL structure only
Observed indicators
- s.to
- https://s.to/
Other scans of s.to (10)
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
- 24 Aug 2026 - unknown
- 23 Aug 2026 - unknown
- 23 Aug 2026 - unknown
- 23 Aug 2026 - unknown
- 22 Aug 2026 - unknown
- 22 Aug 2026 - unknown
- 21 Aug 2026 - unknown
- 21 Aug 2026 - unknown
- 21 Aug 2026 - unknown
Questions about s.to
- Is s.to safe?
- The scan of s.to on 22 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 s.to?
- 124 analysed samples communicate with this URL.
- How was s.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 s.to
Scanned on MalwareAnalyzer by Cyble · Open interactive scan