Filecrypt
- Free allowance
- Opening a container costs nothing and needs no account: a container URL answers 200 to an anonymous GET.
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- anonymousno card, no phone
- Binding limit
- write-gatedsome containers put a 'Security Check' captcha in front of the link list; others serve the table directly
- Evidence
- documented7 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-11-23checked 2026-10-23 (live); stale on 2026-11-23
| Free tier | Opening a container costs nothing and needs no account: a container URL answers 200 to an anonymous GET. Creating one is offered on a public Create page ('You can also create a test container containing any link you want here https://filecrypt.cc/Create.html'). The site root redirects an anonymous visitor to /Login.html, which is the management side of the service, not the container side. unit unlimited; metered on none; No price list, no quota page and no account requirement were found on the container path. |
|---|---|
| Price | USD 0 |
| Limits |
The captcha is per container, not per account, so it cannot be paid away. Cloudflare fronts the whole site and the root response carries a challenge-platform signature. |
| Binding | write-gated The captcha on a protected container is what stops an unattended wrapper first; account quotas do not exist on this path, and a container holds links rather than bytes so no volume quota applies. |
| Identity | anonymous No account was needed to fetch a container page or to reach the Create page. The /Login.html redirect applies to account management. |
| Egress | No egress of its own: the container page lists links to other hosts and the browser or downloader fetches from those hosts. free allowance: none: no service-side bytes |
| Per-object cap | not applicable: a container holds links, not bytes. The size shown on a container page is the sum of the linked host files. |
| Retention | unverified: no page states how long a container survives. Containers dated 2024-2025 still appear in search results with live host links, so retention is at least months for popular containers, but no policy is published. |
| Interface | unknown HTML container pages. The machine interfaces are Click'n'Load (a page script POSTs the link list to a local JDownloader listener on 127.0.0.1:9666) and the DLC container file offered on the page. No documented JSON API for resolving a container was found, so a wrapper parses the page. |
| Tooling | JDownloader's filecrypt plugin is the mature client; the board records that its direct-link parsing broke in 2024 while CNL and DLC kept working. A HTTP wrapper is feasible because the container page is server-rendered HTML. |
| Composes with | A container is the index, not the storage: resolving it yields one link per host, and those links are what a debrid service, a leech site or a JD instance consumes. It composes with every other row. |
| Reliability | Containers rot when the underlying host files are removed: pages show an online count (e.g. '4/13 Online') so dead links are visible. Cloudflare challenges and per-container captchas break unattended resolution. |
| Notes | The container page is the only part that answers 'resolve a link with no install and no account' cleanly: it turns one protected URL into the host list. It does not produce a direct file link, and it does not bypass the host's own limits. Relevant because DDL posts increasingly wrap their mirrors in a container rather than printing five host URLs, so any pipeline that scrapes DDL indexes needs a container resolver as a second stage. Not the storage topic's: the container holds no bytes. |
| Evidence note | documented Two container probes and the root probe are measured; the captcha and creating-without-account statements come from pages and a third-party issue comment. Solving a captcha and diffing the resolved list would raise this to measured. |
| Parsed numbers |
|
Evidence 7
| date | source | what it proved |
|---|---|---|
| 2026-10-23 | probe: https://filecrypt.cc/ | the root redirects anonymously to /Login.html: HTTP 200 at 01:59:05Z, 5388 bytes, sha256 66e512e7a1fde0b97cdb6f02b67174d29f0e5f1629958fbf50721a5e8fdc22d6, challenge signature cloudflare-challenge. The same 5388-byte page hashed differently on an earlier request, so the digest is per-response and the byte count is the stable fact. |
| 2026-10-23 | probe: https://filecrypt.cc/Container/4537F7C9C6.html | a container resolves anonymously: HTTP 200, 300000 bytes read (truncated prefix), sha256 3fa5c06cea42eff610275db57549150c626e8c7030c037198918108ec5508f1f, no challenge detected |
| 2026-10-23 | www.filecrypt.cc/Container/5A442B9C26 | a protected container serves a 'Security Check' captcha before its link table |
| 2026-10-23 | github.com/rogerfar/rdt-client/issues/68 | reported, third-party: 'You can also create a test container containing any link you want here https://filecrypt.cc/Create.html' and a real container URL; the DLC button exports the list |
| 2026-10-23 | board.jdownloader.org/showthread.php?t=96509 | reported: the JD plugin's direct-link parsing broke in 2024 because filecrypt changed the site; CNL and DLC were unaffected |
| 2026-10-23 | filecrypt.cc/Container/4C4DAE699C.html | HTTP 200 with a language selector (English, German, Italian, French, Russian, Spanish, Polish, Dutch, Turkish, Japanese, Chinese, Czech) and no link list in the extracted text |
| 2026-10-23 | filecrypt.cc/ | the reader was redirected to https://filecrypt.cc/Login.html and returned 'login wall' rather than the home page |
More fields 6
| container probe record | scratch (removed) |
|---|---|
| root probe record | scratch (removed) |
| machine interfaces | Click'n'Load to 127.0.0.1:9666, DLC export, HTML parse |
| container path | /Container/<id>.html |
| client side render | yes |
| known clients | JDownloader plugin, Filecrypt Link Unlocker userscript (seen in search results, not executed) |
Unknown values 1
- interface: the access interface was not established