DESTINATION CHECKS
Check a saved destination from your workspace, see its latest response and decide what to fix. Keep the address you have already shared.
Destination checks run separately from public redirects. Queue a check in Links → Link health; Zogy checks the saved HTTPS destination and records a private result. Your short link does not wait for the destination check.
A missing page, a server error and a page requiring login are different situations. Results include the response code and check time. Sites that block HEAD requests or time out are marked inconclusive, rather than declared broken.
Workspace owners or admins enable anonymous checks. Editors can check links they are allowed to edit. Results never silently redirect visitors elsewhere; use the existing editor and destination history to make a reviewed change.
Latest results stay in your workspace. Checks send no user cookies or login credentials and inspect no response body. This release supports on-demand checks, with 20 new checks per hour and up to ten queued; it does not claim unattended monitoring or email alerts.
No. The check targets the saved destination using HEAD. It does not follow your public short URL or add to its redirect count.
No. The hosted checker only contacts public HTTPS destinations. It cannot use a company VPN or your browser login.
No. A successful HEAD response is a useful signal, not a browser test, safety verdict or uptime guarantee.