Add domain name expiry checker monitor

[enginyilmaaz]

📑 I have found these related issues/pull requests

Not applicable

🔖 Feature description

We currently have 40 separate HTTPS monitors, and within the HTTPS monitors there is a “Domain Name Expiry Notification” feature. However, we also have some domains that were purchased as alternatives and do not have any hosting, service, etc. attached to them. It would be very useful to receive a notification before those domains expire as well. Instead of using the existing “Domain Name Expiry Notification” within the current monitor services, it would be great to have a new monitor service specifically for those standalone domains I mentioned.

✔️ Solution

What needs to be done is to add a new monitoring service that only has the domain name check function.

❓ Alternatives

No response

📝 Additional Context

No response

[matthewCmatt]

Related to #944

[CommanderStorm]

I don't see a reason why this should be a new monitor instead of integrated as the option to the http monitor like currently.

Why would you want to monitor dead infrastructure that you don't even have a website behinind..

[enginyilmaaz]

I don't see a reason why this should be a new monitor instead of integrated as the option to the http monitor like currently.

Why would you want to monitor dead infrastructure that you don't even have a website behinind..

Assume you have a company that operates in several countries and also serves customers worldwide, although the same logic applies even if it only operates in a single country.

Now assume that you own many domains, and that you also need to purchase many country-code extensions and alternative similar domain names. In some cases, this is simply to prevent others from acquiring them and using them for malicious purposes, and to protect the brand name.

For example, companyAbc.com may be the company’s official website, but you may still need to keep local domains such as companyAbc.de and companyAbc.it, as well as alternative names such as companyAbc.net or abcCompany.net under your control.

However, none of these alternative or local domains has any actual function. Naturally, an HTTP monitor would always fail for them, so having a separate monitor type for this scenario would make sense. In addition, this would make the application more comprehensive and more robust.

[CommanderStorm]

I would just recomend to do a permanent redirect under those aliases then, that seems confusing to visit google.de and not get redirected to google.com

[enginyilmaaz]

I would just recomend to do a permanent redirect under those aliases then, that seems confusing to visit google.de and not get redirected to google.com

Thank you for your suggestion; in fact, most of them are already like that. The main goal here is that because there are so many domains, some of them are being overlooked and expiring. We want to receive a warning before they expire so we can renew them in time and eliminate the risk of expiration.

[CommanderStorm]

Then set up all the domains to have a redirect. It is better UX for your users and less work to manage.

Also, not all of those domains are likely domain expiry checkable in the first place if they are country domains -> https://deployment.rdap.org/