Changing your account email now requires confirmation through your current address and verification of the new address. Start from your profile and follow the confirmation emails to complete the change.

Link and domain lists now show small charts of recent click activity on larger screens. You can spot changes in traffic alongside the total click counts without opening each item.

You can now sort your domains by Certificate expiration (ascending) or Certificate expiration (descending). Bring the certificates expiring soonest to the top of the list when reviewing renewals.

You can now connect a Bitbucket account, select one of its repositories, and deploy it to your servers. The integration also supports repository webhooks for deployments triggered by pushes.

You can now mark a custom domain as the default for creating Tny links. The link-creation form selects it automatically, and a star in the custom-domains list identifies your default.

Custom domains can now send visitors to their default redirect destination when a requested short link does not exist. Enable Redirect to the default redirect when no link is found in the custom domain's settings to use this fallback.

You can now edit an existing custom domain's default redirect destination. Domain redirects also have an edit form for changing the destination and choosing whether to include the incoming path and query parameters.

Certificate-expiration reminders now run four, three, two, and one day before expiration, and on the expiration day. For certificates that remain expired, follow-up reminders run after one, two, three, four, seven, ten, and fourteen days.

You can now add a custom domain and use it when creating short links, including links with your own custom slug. Configure the domain's DNS using the setup instructions in Tny and choose it in the link-creation form.

The GraphQL API now includes unshortenUrl to follow redirects and return a link's final destination and redirect chain. Set stripTrackingParams to remove recognized advertising and campaign parameters from the resulting URL.

Deployment scripts now load the SSH user's .bash_profile before running. Commands can use the environment variables and PATH configured there, which helps when deployment tools are installed in user-specific locations.

Older deployment records and their logs are now retained when the environment cleans up old release directories. You can review past deployment results even after their release files are no longer kept on the server.

A script's execution strategy now lets you choose specific servers. Select the servers that should run the script when deploying the environment, alongside the existing options to run on all servers or a single server.

You can now connect a GitLab account and deploy its repositories. Enable deployment on push for an environment to have repository webhooks trigger deployments when its configured branch changes.

The new Reverse IP lookup tool retrieves the PTR record for an IP address. Enter an IPv4 or IPv6 address to find its published reverse DNS hostname.

Each environment now has a deployment-trigger URL in its settings. Call it to deploy the configured branch, or select a branch, tag, or commit through the request parameters. You can regenerate the URL when you need to replace it.

You can now send a URL to https://tny.app/api/unshorten with a POST request to follow its redirects and retrieve the final destination. Request JSON to receive the redirect chain and success result, or use the text response for the destination URL. The endpoint does not require authentication and is rate limited.

You can now arrange connected deployment scripts by dragging them within an environment's deployment steps. Choose whether a script runs on every deployment server or on a single server, which is useful for tasks that should run only once.

Deploy Chief is now available in public beta for deploying PHP applications from GitHub to your servers. Connect a repository, configure environments and SSH servers, then deploy a branch, tag, or commit manually or enable deployments on push.

Scans you request manually now receive priority over routine queued scans. This applies to domain rescans and requests to refresh SSL Labs or Security Headers results.