Revoking certain certificates on March 4


We’re currently discussing a plan to reduce the QPS that we send to Worldnic/NetSol by adding more outbound IP addresses. I’m not sure when this will come to fruition, but it’s a route we’re pursuing.


Thank you for your feedback and suggestions. We will keep them in mind if we have to provide this tool/service in the future.

1 Like

This is probably not the best place for it, but MS are terrible at responding to anything and this is extremely short notice - Does anyone know if the team at Azure are aware of this imminent revoking and have a plan in place? I have certs provisioned that haven’t been renewed (and they don’t have the ability to manually renew CDN certificates)… I imagine they are a large consumer of letsencrypt certs and there would be a lot of people in the same boat.

1 Like

We believe the (Network Solutions) issue is mostly resolved, and affected subscribers should be seeing more success getting new certificates:


We’re in the same boat as @kf6nux. We have thousands of customer domains on WorldNic/Netsol and spread across our certs so those certs will keep failing.

1 Like

We saw the worldnic issue get a lot better about an hour ago and @JamesLE posted that it’s either fixed or mostly fixed here: DNS failures (SERVFAIL, timeout) for domains using Network Solutions/ nameservers


In order to complete revocations before the deadline of 2020-03-05 03:00 UTC, we are planning to start revoking affected certificates at 2020-03-04 20:00 UTC (3:00pm US EST). Please continue to renew and replace affected certificates in the meantime. If there are any changes to this start time, updates will be provided in this thread. Thank you all very much for your patience, understanding, and help as we work through this issue.


I have updated the top level FAQ to reflect this information


As of 06:45 UTC 04/03/2020 no email notification.
Saw an article in “The register” and took 30 seconds to renew a certificate.

More good luck than good management!!
Should have checked before renewing, I suppose. Checked after and it seems OK now

A post was split to a new topic: HTTPSConnectionPool(host=‘’, port=443): Read timed out

A post was split to a new topic: Certificate renew with Kubernetes cert-manager

A post was split to a new topic: How to reissue cert for QNAP NAS

Bit of an odd one, the email I received shows the domain and serial number of the affected domains but searching the caa-rechecking-incident-affected-serials.txt.gz the serial number isn’t there. So do I still need to re-issue the certificate?

@RobC-CTL Can you post the specifics?

Are you sure it isn’t just a syntax issue or something – some software displays serial numbers with colons and some doesn’t, and a simple grep won’t match them.

1 Like

Hi @mnordhoff

The email that I received:

Your affected certificate(s), listed by serial number and domain names:


However searching the gz file for either the domain or serial doesn’t return any results. I’ve also checked the domain and it reports as OK. The certificate is due to renew on the 7th March.


$ zgrep -n caa-rechecking-incident-affected-serials.txt.gz
2069026:serial 038347490d86e1777e3b7a2382a31e3f90f9 53724289 bc0cd81bd98d29327120078607e585e3afa83da5d08584cd89edcc498f1de4f6 names: [] missing CAA checking results for at 2019-12-08 14:18:52.977438985 +0000 UTC

Hi @RobC-CTL

that value is in the file:

serial 038347490d86e1777e3b7a2382a31e3f90f9 53724289 bc0cd81bd98d29327120078607e585e3afa83da5d08584cd89edcc498f1de4f6 names: [] missing CAA checking results for at 2019-12-08 14:18:52.977438985 +0000 UTC

But the certificate is old, so you have already renewed it. So

doesn’t show a result.


#HugOps@LE :heart:
Thanks for the additional time to get replacement certs.
Thanks @JamesLE et al (including Network Solutions) for getting resolution to that problem which was blocking/slowing getting replacement certs for hostnames with worldnic NS.
We were able to get all ~1000 of our affected certs reissued prior to revocation. :grinning:


Our CDN (Akamai) is still overloaded :cold_face:
The renewal didn’t progress for 14 hours !

I opened a ticket with their support team, but I’m really worried it may not renew before revocation.


Your options seem to be to trust your vendor to get it resolved or have a contingency plan where you get your own cert (from LE or any other CA) and know how to deploy it (to Akamai or another CDN).

1 Like