f.in - URL scan, 14 Aug 2026
MalwareAnalyzer by Cyble scanned f.in and returned a unknown verdict (score 0). 1 domain and 0 IPs were contacted. 2 malware samples communicate with this URL (Zusy). 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://f.in/ - Domain: f.in
- Scan tier: fast · observed 2026-08-14 18:10:48 UTC
Malware communicating with this URL (2)
These samples were observed contacting or being served from f.in. Each links to its full analysis.
- Zusy - referenced ·
0812e06ac07706fc004d9610fb0f5062· first seen 2026-08-14 - 79577c55cd1277da996f6ff4d0684431441a81aee6b78cc78c6e6d0416878f1a - referenced ·
79577c55cd1277da996f6ff4d0684431· first seen 2026-08-13
Why this verdict
- Target did not respond (DNS/connection failure or timeout); verdict from URL structure only
Observed indicators
- f.in
- https://f.in/
Other scans of f.in (1)
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
Questions about f.in
- Is f.in safe?
- The scan of f.in 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 f.in?
- 2 analysed samples communicate with this URL, including Zusy.
- How was f.in 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 f.in
Scanned on MalwareAnalyzer by Cyble · Open interactive scan