Security

How we approach link security

URL validation, rate limits, ownership checks, and abuse controls in the current architecture.

9 min read · Sep 9, 2026

Validate without fetching

Submitted destinations are restricted to HTTP and HTTPS and checked for malformed hosts, credentials, and configured block lists. Normal shortening does not fetch the destination, avoiding a server-side request forgery path.

Enforce ownership

Laravel policies scope link reads and mutations to the owner. API tokens have explicit abilities and expire.

Control abuse

Anonymous creation, authenticated creation, analytics, authentication, password reset, and abuse reporting use separate configurable rate limits.

Ready to put this into practice?

Create a managed link and inspect real analytics from your workspace.

Create an account →