Dead link monitoring and health score

clk.ms can monitor destination health and warn the owner when a page becomes unavailable or suspicious. Checks cover not found pages, server errors, timeouts, expired SSL, domains that no longer resolve, and redirect loops. A redirect loop means the destination keeps forwarding the visitor in circles and never reaches a final page. The health score is a simple quality rating based on practical signals such as HTTPS availability, suspicious-domain status, redirect chain length, page response speed, and anti-phishing or safe-browsing results when those sources are available.

Dead link monitoring helps owners catch destination problems before visitors complain. A destination can fail because the page was deleted, the server returns an error, the domain stops resolving, SSL expires, the page times out, or redirects loop forever. The health score summarizes practical quality signals into a simple view so owners can decide whether the link is safe to keep sharing.

Health is not only about whether the page opens. A slow page can hurt conversion. A long redirect chain can confuse analytics and reduce trust. A suspicious or unsafe destination can damage users and the brand. When available, safe browsing and anti-phishing signals help identify risky destinations, while HTTPS and SSL checks help confirm basic transport trust.

Example: a campaign link still redirects, but the final page now takes eight seconds to respond and passes through several redirects. The health score drops, giving the owner a reason to update the destination or fix the landing page before increasing ad spend.

Best practice: review health before major campaigns, after destination changes, and before printing QR materials. Treat warnings as operational signals: fix the target page, change the destination, or pause sharing until the issue is resolved.

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.