General

I have a few domains that do not have public websites. Would be nice to check the domain once a day for the expiration of registration.

Ability to create group of checks or tag them to ease search and filtering.

It would be useful if the check IPv4/6 offering was included in the API, that way I could integrate an external IPv6 check into my local Uptime Kuma instance.

A user should be able to generate (and tag) multiple api keys. i.e. staging + production environments

Hi, I have implemented a simple php script on one of my servers to take a query via GET method and returns the requested DNS record. The site is restricted to updown.io servers and uses a URL in the following format : https://webserver.com/lookup.php?T=A&D=google.co.uk&R=IP This uses the following fields : T - Type of record to return eg. MX/A/TXT D - Domain to check eg. google.co.uk R - Record field to return. eg. ip for ip address The server code simple checks if the record type is a valid one we accept, checks the domain name is in a valid format and then performs a PHP dns_get_record(), it then checks if the R field is in the result and returns it if it is. If there are multiple matching records, then it simple returns them all separated by a ',' this allows using the 'contains' field within the check portal to check for the required data. This allows me to check that a DNS record hasn't been changed by a third party (eg. I host a customers web page, but all there DNS etc is handled by someone else). Would be happy to supply the scripts if anyone is interested, would be great to add to updown as a service (with rate limiting etc!) marl_scot

It would be awesome to have a server in Africa so that updown.io would cover every continent on this planet.

I think a custom logo has been suggested before in a comment ( https://updown.canny.io/general/p/custom-css-for-public-status-pagess ), just wanted to raise it a suggestion now

How about having a dark theme? I find it a bit aggressive to the eyes after few minutes. Having a toggle button and choose between original or website in a dark theme would be amazing!

Add a new check point in Russia. Moscow and Novosibirsk.

Currently updown.io breaks out the time of normal requests into: * name lookup; * connection; * tls handshake; and * response time but shows redirects as a single block of time. It would be useful to see redirects broken out the same way. Users often type naked domains, like example.com , into browsers. That might lead to this sequence of redirects: http://example.com/ -> https://example.com https://example.com/ -> https://www.example.com (HSTS preload requires the first redirect; you can't go straight from http://example.com/ to https://www.example.com .) Depending on how you're handling both http and naked domains the time for the redirects can be much greater than the time of a page load. It would be useful to know where that time is actually being spent. For example, maybe your naked domain doesn't have good geographic distribution, or maybe it has slow TLS handshakes.