s.to - URL scan, 24 Aug 2026
MalwareAnalyzer by Cyble scanned s.to and returned a unknown verdict (score 0). 1 domain and 0 IPs were contacted. 159 malware samples communicate with this URL. This is a point-in-time observation from 24 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-24 00:23:22 UTC
Malware communicating with this URL (159)
These samples were observed contacting or being served from s.to. Each links to its full analysis.
- c2eac121fb60e5a6c1383950dcab1b47c10c4df8718e16c47425f8afdfbfc7f5 - referenced ·
c2eac121fb60e5a6c1383950dcab1b47· first seen 2026-08-24 - 14864a42516135109b7a755906a4d34c10312dfba2e7390b3a2ee1d1b7116947 - referenced ·
14864a42516135109b7a755906a4d34c· first seen 2026-08-23 - e85dddee5a11e330b1662d3f70e5b4f65e6f77b968844cfb06f039461e5efc5f - referenced ·
e85dddee5a11e330b1662d3f70e5b4f6· first seen 2026-08-23 - 8364278abdddac5a1d5d971f6f45c292c81f28ba9ee381bb59a19f317fc5e8b6 - referenced ·
8364278abdddac5a1d5d971f6f45c292· first seen 2026-08-23 - 1b3e56854b20e0f5837697d2e2e6e1ae50e482bb6ae3c22c0105bdf7cb7bdbf9 - referenced ·
1b3e56854b20e0f5837697d2e2e6e1ae· first seen 2026-08-23 - b736682b39beeed2262e9561a6bf255ef07a4be7e53aa288ca700e136841123e - referenced ·
b736682b39beeed2262e9561a6bf255e· first seen 2026-08-23 - b4ce2d1a9cfae221b8cc1a790575d011b3002ae691096e017a4d96849f4f4a5d - referenced ·
b4ce2d1a9cfae221b8cc1a790575d011· first seen 2026-08-23 - ec823f588cdb9c5302d744b9f39cd0001cfadf5e4d4bebabdd17529457dfd44b - referenced ·
ec823f588cdb9c5302d744b9f39cd000· first seen 2026-08-23 - b962353a79d001f30d983de0e0c75740339075b324e03cf1d861578d61cbd4a0 - referenced ·
b962353a79d001f30d983de0e0c75740· first seen 2026-08-23 - 4baff9309042bf3e049ba0925a5766860d0fdc81fa5b56512af4c0ec343faeff - referenced ·
4baff9309042bf3e049ba0925a576686· first seen 2026-08-23 - 0096e9d3f18be6df1e5db5337b27db0b197276bfa419aba9f0b33aa296befa67 - referenced ·
0096e9d3f18be6df1e5db5337b27db0b· first seen 2026-08-23 - db54c38ba224e03e12d437a95b03e68201941b13c08454cbcaf521e0bfa5186f - referenced ·
db54c38ba224e03e12d437a95b03e682· first seen 2026-08-23 - 90d346a716467a4b20dc968aa8f4969027ba6071276a668e34950430df01ddd9 - referenced ·
90d346a716467a4b20dc968aa8f49690· first seen 2026-08-23 - 8b49b7e33dc0aa44125c6312147c28b5bfd0da38f8aa373eed085c100c67b903 - referenced ·
8b49b7e33dc0aa44125c6312147c28b5· first seen 2026-08-23 - ba44f77e1040c9bb227107ea7f006988dab5e8321dabda777a8b3eb93c820420 - referenced ·
ba44f77e1040c9bb227107ea7f006988· first seen 2026-08-23
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.
- 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
- 21 Aug 2026 - unknown
Questions about s.to
- Is s.to safe?
- The scan of s.to on 24 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?
- 159 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