DSC Problem
Revocation is permanent, a revoked certificate can't be reactivated, here's what to do instead.
Unlike expiry (which happens naturally at the end of your validity period), revocation is a deliberate action, taken before expiry, usually because the token was lost or stolen, the holder's details changed materially, or the certificate was requested to be withdrawn. A revoked certificate cannot be reactivated, ever, regardless of the reason.
Check with your Certifying Authority or issuer to confirm the certificate's actual status, some error messages can look similar without being true revocation.
If you didn't request the revocation yourself, ask your CA for the reason, this matters especially if it points to a security concern like token compromise.
There's no reactivation path, you'll need a new Class 3 DSC issued through the standard verification process.
We issue new Class 3 DSCs quickly, same-day verification in most cases.
No, revocation is permanent and final, a fresh certificate is the only path forward.
Common reasons include a lost or stolen token, a change in the holder's authorized status (like a director leaving a company), or a voluntary request by the holder or organization.
Generally yes, documents signed while the certificate was active and valid remain valid, revocation doesn't retroactively invalidate past signatures.