Feature Requests Support Automatic Domain Change Detection
Closed
Could updown.io automatically track domain changes and keep monitoring the new domain after a permanent 301 redirect (e.g. abc123 → abc456)?
Christiana Honerpeick
Created on June 13, 2026 · Last update on June 18, 2026
8 Comments
Updown does follow 301 redirects, like any other types of redirect, in order to monitor the full chain and what is as the end.
So my understanding is that you would like the monitored domain to be updated on updown side, so as to stop following the 301 every time and monitor the target site directly ?
If that is what you mean, then it's unlikely I'll implement this. Because even though 301 are permanent and can be "safely" replaced for search engines and the likes, in terms of monitoring people usually want to make sure this 301 is in place and stays correct in the future. So it's very often preferable to keep querying and following the 301 to ensure that, and if you actually want to stop monitoring the 301, you can replace the monitored URL directly on your end.
Thanks for the explanation. I understand why you prefer to keep monitoring the original URL and its 301 redirect.
Would it be possible to add API support (or a notification field) that indicates when the final destination domain has changed?
For example, if abc123.com previously redirected to abc123.com and later starts permanently redirecting to abc456.com, the API could report that the final destination domain has changed.
My goal is not to automatically replace the monitored URL in Updown, but simply to be informed when a domain migration occurs. With that information, I could automatically adjust links, records, and frontend displays on my side.
This would keep the current monitoring behavior unchanged while making it easier for developers to build their own automation around domain changes.
It wouldn't make much sense for a monitoring service to notify on that as it's not abnormal. There's no reason updown should automate this detection for you. But one thing that could be added in the API is the detailed results for the last 5 checks (on the /api/checks/xxxx endpoint), these results would contain the final url (after all redirection were followed). But that would mean you would have to poll those for all checks regularly, which is not any simpler than simply checking the redirection target on your end.
Thanks, that would actually be very useful for my use case.
I understand that I could check redirect targets on my own, but having the final URL included in the API response would make integration much easier for developers who already rely on Updown as their monitoring source.
Even if notifications are out of scope, exposing the final URL in the recent check results would provide all the information needed to build custom automation on top of Updown.
If you ever decide to extend the API, I would definitely make use of that feature. Hopefully it can be considered sooner rather than later.
Providing the detailed results in the API could be beneficial for other use-cases too so yes I'll consider adding it and let you know.
Ok I just added the
resultsparameter to the GET /api/checks/:token endpoint. If you passtruefor that parameter you'll now get the detailed results for the last 5 requests, including theresponse.final_url.Thanks! Since I'll be monitoring over 1,000 websites, could you consider adding 6h, 12h, and 24h check interval options in the future? That would be very helpful for large-scale monitoring.
I can't as this wouldn't work with updown pricing (see https://updown.io/features/more-check-periods-2h-and-4h) but for 1000 sites I can allow your to use the 2h check interval (I just added it to your account).
Sign in to comment