CertCentral Services API: Domain locking API endpoints
DigiCert is happy to announce our domain locking feature is now available in the CertCentral Services API.
Note: Before you can use the domain locking endpoints, you must first enable domain locking for your CertCentral account. See Domain locking – Enable domain locking for your account.
New API endpoints
Updated API endpoints
We updated the response for the Domain info and List domains endpoints to include the following parameters with domain lock details:
domain_locking_status (string)account_token (string)To learn more, see:
CertCentral: Domain locking is now available
DigiCert is happy to announce our domain locking feature is now available.
Does your company have more than one CertCentral account? Do you need to control which of your accounts can order certificates for specific company domains?
Domain locking allows you to control which of your CertCentral accounts can order certificates for your domains.
How does domain locking work?
DNS Certification Authority Authorization (CAA) resource records allow you to control which certificate authorities can issue certificates for your domains.
With domain locking, you can use this same CAA resource record to control which of your company's CertCentral accounts can order certificates for your domains.
How do I lock a domain?
To lock a domain:
To learn more, see:
End of life for account upgrades from Symantec, GeoTrust, Thawte or RapidSSL to CertCentral™
From April 5, 2022, MDT, you can no longer upgrade your Symantec, GeoTrust, Thawte, or RapidSSL account to CertCentral™.
If you haven't already moved to DigiCert CertCentral, upgrade now to maintain website security and have continued access to your certificates.
Note: During 2020, DigiCert discontinued all Symantec, GeoTrust, Thawte, RapidSSL admin consoles, enrollment services, and API services.
How do I upgrade my account?
To upgrade your account, contact DigiCert Support immediately. For more information about the account upgrade process, see Upgrade from Symantec, GeoTrust, Thawte, or RapidSSL.
What happens if I don't upgrade my account to CertCentral?
After April 5, 2022, you must get a new CertCentral account and manually add all account information, such as domains and organizations. In addition, you won't be able to migrate any of your active certificates to your new account.
For help setting up your new CertCentral account after April 5, 2022, contact DigiCert Support.
Requisitos das normas da indústria para incluir a extensão CanSignHttpExchanges em um certificado ECC SSL/TLS:
*Nota: Estes requisitos entraram em efeito em 1 de maio de 2019. A extensão Signed HTTP Exchanges está sob desenvolvimento ativo. Pode haver alterações adicionais aos requisitos conforme o desenvolvimento da indústria continua.
O requisito de validade máxima do certificado de 90 dias não afeta certificados emitidos antes de 1 de maio de 2019. Note que certificado reemitido será truncado para 90 dias a partir do momento da re-emissão. Contudo, é possível continuar re-emitindo o certificado para o período completo adquirido de validade.
Extensão CanSignHttpExchanges
Recentemente, adicionamos um novo perfil do certificado, HTTP Signed Exchanges para ajudar a lidar com o problema de exibição da URL de AMP em que a sua marca não é exibida na barra de endereço. Consulte, Exibir melhores AMP URLs com Signed Exchanges.
Este novo perfil permite incluir a extensão CanSignHttpExchanges em certificados OV e EV SSL/TLS. Quando habilitada para a sua conta, a opção Incluir a extensão CanSignHttpExchanges no certificado aparece nos seus formulários de pedidos de certificados OV e EV SSL/TLS em Opções adicionais de certificados. Consulte Obter seu certificado Signed HTTP Exchanges.
Para habilitar este perfil do certificado para a sua conta, fale com o seu gerente de contas ou contate a nossa equipe de atendimento.
