Open link lists are a risk: bots harvest them, they get reported or blocked, and they quickly become unmanageable. This guide shows how to pass on download links encrypted, access-protected and neatly organised – using a link container instead of an open list. Zaulto bundles your links in a protected container, with no installation and no tracking.
Posting several download links directly into a forum, chat or web page makes them instantly visible to everyone – including automated bots. These scan the web specifically for open links, harvest them and get them reported or blocked. Long lists are also messy and break the moment a single source goes offline.
The answer is a link container: instead of posting every link in the open, you bundle them all, encrypted, under a single short address. They only become visible once a visitor passes the access check.
The simplest effective protection is a password per container. Visitors must enter it before the links become visible. The password is not stored in plain text but only as a hash, and the links are only delivered once it is entered correctly. So you can share the short container address openly – and pass the password to recipients separately, through a different channel.
To stop automated scripts from simply harvesting your links, every container can be secured with a captcha. Zaulto offers three variants: a simple arithmetic challenge, an invisible proof-of-work (compute-based, no clicks) and a custom question with a stored answer. The arithmetic challenge and the custom question include the same invisible proof-of-work – it makes mass automation costly without locking scripts out entirely; the pure proof-of-work variant needs no click puzzles.
With geo and IP rules you control where a container may be accessed from. You can restrict access to specific countries or block individual IP ranges. Requests that don't match get no access to the links at all – an effective extra hurdle against unwanted access.
In stealth mode visitors who fail a protection rule – such as geo, IP block, limit or expiry – see “not found” (404) instead of “blocked” (403): to them the container looks as if it doesn't exist. It is on by default for new containers. With optional URL masking the real hoster addresses are not in the page source; Zaulto only redirects to the hoster on click. AutoProtect adds an intermediate page with a short wait and an invisible proof-of-work to the masking, per container, so links can't be read out by a simple script.
For each container you can set an expiry date and access limit and limit the number of unlocks. At the expiry date the container is deleted; once the download limit is reached it hands out no more links – or it deletes itself via self-destruct after the set number of unlocks. That way shared links don't circulate forever, but exactly as long as you want.
For large, multi-part collections you can switch on Click'n'Load per container – a single click adds all links to JDownloader at once. You can also offer a .dlc file; it is Zaulto's own format with the links in readable form (not an encrypted DLC file for JDownloader) and is unavailable with URL masking. Both are only available after the visitor has passed the access check.
Secure sharing means leaving nothing in the open. With a protected container you only pass on a short address – encrypted, access-protected and revocable at any time. No installation, data-minimal and without tracking, on your smartphone too.