s.to - URL scan, 21 Aug 2026
MalwareAnalyzer by Cyble scanned s.to and returned a unknown verdict (score 0). 1 domain and 0 IPs were contacted. 110 malware samples communicate with this URL. This is a point-in-time observation from 21 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-21 15:12:26 UTC
Malware communicating with this URL (110)
These samples were observed contacting or being served from s.to. Each links to its full analysis.
- adaa57934025cbdfe0c1c59ff2b5f827abefbb22460e1e1a7121ddf7574f689c - referenced ·
adaa57934025cbdfe0c1c59ff2b5f827· first seen 2026-08-21 - eacf1c7323f3a32f147759144cff619f0f5e5f41dce34f29a7cf1403f347ea59 - referenced ·
eacf1c7323f3a32f147759144cff619f· first seen 2026-08-21 - 33effee300c82375901f19f60c792d4aecb347b92d88b3a5beb88e1cb5631bc1 - referenced ·
33effee300c82375901f19f60c792d4a· first seen 2026-08-21 - a9fad52ddd5d4d1ef5e64c415d0be738bc60786e54cec397e4d982802a0802a6 - referenced ·
a9fad52ddd5d4d1ef5e64c415d0be738· first seen 2026-08-21 - c1df0746b05c4ee8aab9bdd83eef5240217e334a2902edcd8796e607a5f1e6a6 - referenced ·
c1df0746b05c4ee8aab9bdd83eef5240· first seen 2026-08-21 - d629640d1f27dc2d32350fa8437e9a2898d844dd368de6465e55065e65a81f00 - referenced ·
d629640d1f27dc2d32350fa8437e9a28· first seen 2026-08-21 - 24caa60b7abf305e8b248bf32120b464da82cc7cc27b8455be9508ca81ef5312 - referenced ·
24caa60b7abf305e8b248bf32120b464· first seen 2026-08-21 - 490d92146f1552a5f7639cd49352bdef56ae468f814b91faf2b8ff95654b12a6 - referenced ·
490d92146f1552a5f7639cd49352bdef· first seen 2026-08-21 - 114b66e9d64654b53db0b20e36dca186cd2e96b9f6781ae3665bab361001fd79 - referenced ·
114b66e9d64654b53db0b20e36dca186· first seen 2026-08-21 - 7eda1070bc8a6e94e13d3f6d21da03185745993054da395baf6c356dd2e118c2 - referenced ·
7eda1070bc8a6e94e13d3f6d21da0318· first seen 2026-08-21 - f448764cda422bfe495b31c7997966ea61cc313d99c3840c01403fd844094e29 - referenced ·
f448764cda422bfe495b31c7997966ea· first seen 2026-08-21 - 56de7d73032c03b41cbd98d3d5df8fe95f0c388cdf746dd7edcdd03acca6b031 - referenced ·
56de7d73032c03b41cbd98d3d5df8fe9· first seen 2026-08-21 - d3e737b8dfd7f3fc102ea14c093ab2d5d9363fc5e310cfa15d139aaa31b58352 - referenced ·
d3e737b8dfd7f3fc102ea14c093ab2d5· first seen 2026-08-21 - 638314131743ec906640de11a9ba79dc1d2d31407f2b005937870e9ce791c0af - referenced ·
638314131743ec906640de11a9ba79dc· first seen 2026-08-21 - e581675076595a5aece7680b1ab73acfff40073a1e4acc8480c19b1416fe2898 - referenced ·
e581675076595a5aece7680b1ab73acf· 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
- 23 Aug 2026 - unknown
- 23 Aug 2026 - unknown
- 23 Aug 2026 - unknown
- 22 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 21 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?
- 110 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