Trust, abuse, and prohibited content

clk.ms rejects links that point back to the service, malformed destinations, excessive-length URLs, and known spam or malicious destinations when detection is available. Public creation can be limited when one IP creates too many links, and abusive IP addresses can be blocked temporarily or permanently. Users may not create links to illegal content, spam, phishing, malware, or other harmful destinations. Confirmed abuse can lead to permanent account and IP blocking.

Trust and abuse controls protect visitors, link owners, and the service. clk.ms rejects malformed destinations, links that point back to the service, excessive-length URLs, known spam or malicious destinations when detection is available, and unsafe patterns that violate rules. Public creation can be rate-limited, abusive IP addresses can be blocked, and confirmed harmful use can lead to permanent blocking.

Users are not allowed to create links to illegal content, spam, phishing, malware, or other harmful destinations. This protects recipients who click short links and protects legitimate owners from losing trust in their campaigns. Warning pages, preview pages, and destination checks are additional tools for transparency and safety.

Example: if an account repeatedly creates links to phishing pages, the links can be removed and the creator can be blocked permanently. If a legitimate user accidentally enters an unsafe or blocked destination, the creation form explains why the short link cannot be created.

Best practice: only shorten destinations you trust, review third-party pages before sharing, and use preview or warning pages when transparency is important. For teams, define acceptable-use rules before granting link creation permissions.

How to apply this section

Each topic explains a feature, the user decision behind it, and how to use it without making the link harder to manage. Read the checklist before changing a link that is already shared.

Before you publish or update

Start from the visitor experience: who opens the link, from where, on which device, and what should happen next.
Check that the destination is correct, opens quickly, and shows the expected page for the intended audience.
Choose only the controls that match the goal, such as expiration, password, referrer, QR design, UTM, routing, or analytics sharing.
Save a short note for important changes so future review, rollback, or teamwork stays clear.
Open the short link in a private browser session and, when relevant, test mobile, desktop, QR scan, and protected access paths.
Review analytics after sharing to confirm real visitors, source quality, device mix, and campaign performance.

Practical example

Example: create a test link for an internal page, add a clear slug, set a short expiration, enable preview if the destination is sensitive, scan the QR code from a phone, then check whether the visit appears in the link statistics.

Next step

After this topic is clear, combine it with one adjacent feature. For example, pair UTM with campaigns, QR with print layouts, targeting with fallback, or webhooks with conversion tracking.