-
-
Notifications
You must be signed in to change notification settings - Fork 592
Description
Describe the feature request
DOMAIN_EXPIRATION
should automatically pick up the root domain in a HTTP(S) url and check the expiry for that. Currently, it does not and fails with a negative date:
[DOMAIN_EXPIRATION] (-9223372036854) > 720h (2592000000)
because the ExpiryDate resolves to an invalid date: 0001-01-01 00:00:00 +0000 UTC
.
Why do you personally want this feature to be implemented?
I want a single status check that checks for 3 conditions: domain expiry, cert expiry, and website status. However, the website is often published on a subdomain only such as www
.
- name: gully-tours
interval: 6h
client:
timeout: 30s
conditions:
- "[STATUS] == 200"
- "[DOMAIN_EXPIRATION] > 720h"
- "[CERTIFICATE_EXPIRATION] > 240h"
url: https://www.gully.tours/
In such cases, the DOMAIN_EXPIRATION
check should be smart enough to use gully.tours
as the domain name instead of www.gully.tours
.
How long have you been using this project?
No response
Additional information
I checked ExpirationDate
in the twin/whois
library for both, and perhaps this could be resolved at the whois
layer using the public suffix list?
gully.tours
- 2026-03-26 12:11:13 +0000 UTCwww.gully.tours
- 0001-01-01 00:00:00 +0000 UTC