Linksave
linksave.in · Debrid · 1 record · JSON
Linksave (linksave.in / linkcrypt.ws) Debrid
deadanonymousno cardM
| Free tier | Historical: a free link protector whose API took a username and password and returned a folder URL. 'URL: http://linksave.in/protect?api=[username]:[Password]' with fields for links, mirrors, captcha on/off and container types rsdf/ccf/dlc. Nothing of the service answers today. unit none; metered on none; The 2011 API description is third-party. No current page on the domain exists to confirm or price anything. |
|---|---|
| Price | none stated |
| Per-object cap | not applicable: it held links, not bytes. |
| Retention | unknown and now moot: the service is unreachable, so nothing is retained. |
| Egress | none: dead. free_allowance: none |
| Identity | anonymous Historical API used a username:password pair embedded in the URL; whether registration was open is not verifiable now. |
| Limits |
The 302 target is the same wildcard pattern that linkcrypt.ws now uses, which suggests one operator or one parking setup for both domains. |
| Binding | none Nothing binds because nothing answers: at any volume the first failure is DNS. |
| Interface | rest Historical HTTP API only: POST to /protect?api=user:pass with *save, *links and optional container/captcha fields. Today the domain issues a 302 to a wildcard host that does not resolve in DNS. |
| Tooling | JDownloader used to ship a linksave decrypter plugin. Nothing to drive now. |
| Composes with | none: a dead container service removes an indirection layer, it does not add one. |
| Reliability | Dead as of today: 302 to ww17.linksave.in, then getaddrinfo failure (errno 11004). The broker also returned 504 on the plain read. Last known live capture is the Wayback snapshot of 2025-05-24, HTTP 200. |
| Notes | linkcrypt.ws is the same case and is recorded here rather than as a second file: both 302 to the identical ww17.<domain> wildcard and both fail DNS. The brief names both; one dead service with two domains is one fact. |
| Evidence rung | measured The death is measured twice (probe redirect + DNS failure, broker 504). The description of what it was rests on a 2011 forum post and the archive capture, and is marked reported. |
| Checked | 2026-10-24 (live); stale on 2026-11-23 |
Evidence (4)
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | probe:https://linksave.in/ | HTTP 302 to https://ww17.linksave.in/, then 'getaddrinfo failed' errno 11004; 0 bytes; no hash |
| 2026-10-23 | probe:https://linkcrypt.ws/ | the sibling domain fails identically: 302 to https://ww17.linkcrypt.ws/, then DNS failure |
| 2026-10-23 | web.archive.org/web/20250524063944/http://linksave.in/ | Wayback capture 2025-05-24 06:39:44 of the root: HTTP 200, text/html, 1122 bytes recorded |
| 2026-10-23 | www.autoitscript.com/forum/topic/129784-help-using-winhttp-t | reported, 2011: the protect API signature and the rsdf/ccf/dlc container options |
More fields (2)
{
"sibling_domain": "linkcrypt.ws (302 to ww17.linkcrypt.ws, DNS failure)",
"last_live_capture": "2025-05-24T06:39:44Z (Wayback, HTTP 200)"
}