Obtaining certificate chain for unlock.no, one moment while we download the unlock.no certificate and related intermediate certificates...
Refreshing certificate chain and revocation status for unlock.no, one moment while we re-check the unlock.no certificate and related intermediate certificates...
You need to clear your local browser cache or use a private browsing session to immediately see the refreshed results when this refresh has completed...
Revocation check via OCSP and CRL for unlock.no failed
Sorry, the request for unlock.no could not be completed...
We could not load the certificate for unlock.no, it might not exist or we could not reach the server, complete the TLS handshake, etc.
Revoked certificates can't and should not be trusted, these certificate will cause errors like "NET::ERR_CERT_REVOKED" in browsers and expose a security risk.