If you used the tool with the URL of your site, it might pick up the incorrect certificate (b/c it might have already been renewed). You could enter your hostname into https://crt.sh/ and check the certificate which was issued just before January 26th. That cert then probably is revoked and on the list of the tool. You can check that using the serial (without the colons :, just the number/letters).
Has anyone been able to successfully fix this using Lego? I am getting 'The certificate expires in 59 days, the number of days defined to perform the renewal is 30: no renewal.'. It would really suck if the website can't be seen for 29 more days. Doesn't seem like a good thing for Lego to not have a force renew option.
@tychoash
Is there any way to temporarily change the default renewal interval (30 days before expiry) to a number that would trigger the renewal today?
We completed revocations and provided additional time for revoked certs to be renewed and replaced with relaxed rate limits. We have returned our rate limits to the documented values.