Yes. There are no captchas or bot walls in front of the website, the API, the MCP server or zou.sh redirects, so Blinkhop works the same over Tor, a VPN or any shared network.
What works over Tor and VPNs
- Shortening links on blinkhop.com, with custom endings and QR codes
- The REST API and the MCP server, without a key
- Redirects and
+preview pages on zou.sh - The free tools: QR code generator, UTM builder and link expander
Shared IP addresses and rate limits
Rate limits are counted per IP address: 20 new links per minute and 300 per day, or 120 calls per minute and 5,000 per day on the MCP server. Many people can share the same Tor exit or VPN address, so you might reach a limit that other people used up.
If you see a rate_limited error, wait a minute and try again. Through the API, the Retry-After header tells you exactly how long to wait.
What we store about you
- Redirects set no cookies, and visitor IP addresses are never stored.
- Creating a link stores the destination URL, the code, the creation time and how it was created (web, API or MCP). No IP address.
- Clicks are counted in aggregate, by day, country, referrer domain and device type.
- Rate limiting keeps IP addresses in memory for at most 24 hours, never on disk.
What data does Blinkhop collect? has the full list. For more on how Blinkhop handles privacy, see Blinkhop for privacy-conscious users.
Still stuck? If a Blinkhop page, the API or a zou.sh link ever shows you a captcha or a block page, tell us.
