2 results found
Indeed that's an idea but unfortunately there's no notion of "connection" for UDP so it's not possible to know if a port is filtered or if a service is simply not responding because it waits for a specific message for example. There is just one obvious case when the port is "officially" closed and so a response is sent to tell you that. Which kind of service would you like to monitor? would it require to send a specific packet? would it need to check for a response? Is just knowing that no response is received (not knowing if it's filtered or open) enough for your use-case?
An error occurred while saving the commentOlivier Mary commented
Somes games servers have all port only udp
One important thing to note here is that having an invalid certificate does NOT prevent the expiration notifications. This is independent so you can keep an "invalid" certificate forever (updown will not notify you again about this) and still benefit from expiration warnings. This way we already kind of "tolerate" this use-case of running a non-publicly trusted certificate.
About the suggested changes, I would like to avoid the custom cert/CA UI because that's a lot of added complexity for a very small use-case among my clients. It'll generate more support also as people will wonder what this do, try to upload other certificates, it'll be annoying for self-signed certificates, etc... The UI to manually "acknowledge" that one cert should be considered valid though sounds more doable for me, I'll keep this suggestion to track the demand and will probably add this someday.