CertCentral

若要讓規劃您的憑證相關工作變得更容易，我們預先排程我們的 2022 維護視窗。請參閱 DigiCert 2022 排程的維護 — 此頁面有最新的所有維護排程資訊。

我們在全世界都有客戶，因此理解沒有對每個人的最佳時間。但在檢閱與客戶使用有關的資料後，我們選擇了會影響我們最少客戶量的時段。

關於我們的維護時程表

如果您需要更多有關這些維護時段的資訊，請聯絡您的帳戶管理員或 DigiCert 支援團隊。

To simplify the domain control validation (DCV) workflow for OV and EV TLS certificates, we've improved our random value generation process for OV and EV certificate orders.

Now, when using DCV methods that require a random value to complete the domain validation for your OV or EV TLS orders, you receive a single random value that you can use to complete the DCV check for every domain on the order.

This change brings the DCV workflow for OV and EV orders into closer alignment with DV orders, which have always returned a single random value for all domains on the order.

Affected DCV methods:

To improve API workflows for clients using DCV methods that require a random value for OV and EV TLS certificate orders, we made the following enhancements to the CertCentral Services API.

{
  "id": 12345,
  "dcv_random_value": "ab12cdef345gh6i78jklmnop901qrs23",1
  "domains": [
    {
      "id": 1469,
      "name": "example.com",
      "dns_name": "example.com",
      "dcv_token": {
        "token": "ab12cdef345gh6i78jklmnop901qrs23",
        "status": "pending",
        "expiration_date": "2023-08-16T01:16:29+00:00"
      }
    },
    {
      "id": 1469,
      "name": "example.com",
      "dns_name": "sub.example.com",
      "dcv_token"2: {
        "token": "ab12cdef345gh6i78jklmnop901qrs23",
        "status": "pending",
        "expiration_date": "2023-08-16T01:16:29+00:00"
      }
    },
    {
      "id": 1470,
      "name": "example.org",
      "dns_name": "example.org",
      "dcv_token": {
        "token"3: "ab12cdef345gh6i78jklmnop901qrs23",
        "status": "pending",
        "expiration_date": "2023-08-16T01:16:29+00:00"
      }
    }
  ],
  "certificate_id": 123456
}

{
  ...
  "higher_level_domains": [
    {
      "name": "sub.example.com",
      "id": 4316203,
      "dcv_expiration_datetime": "2023-12-04T04:08:50+00:00"
    },
    {
      "name": "example.com",
      "id": 4316205,
      "dcv_expiration_datetime": "2023-12-04T04:08:49+00:00"
    }
  ],
  ...
}

https://www.digicert.com/services/v2/domain/{{domain_id}}?include_dcv=true

To give API clients access to more information about the verified contacts that exist for an organization, we added a new array to the Organization info API response: verified_contacts.

The new verified_contacts array provides a list of objects with details about each verified contact that exists for the organization. The verified_contacts array:

{
... 
 "verified_contacts": [
    {
      "id": 942858,
      "name": "Jane Doe",
      "first_name": "Jane",
      "last_name": "Doe",
      "job_title": "Site Reliability Engineer",
      "telephone": "1234567890",
      "email": "jane.doe@example.com",
      "verified_roles": [
        {
          "validation_type": "EV",
          "status": "pending"
        },
        {
          "validation_type": "CS",
          "status": "pending"
        }
      ]
    }
  ],
...
}

We fixed a bug where submitting a verified contact with multiple validation types (for example, CS and EV) caused duplicate verified contacts to be created for the organization, one for each validation type. This bug affected verified contacts submitted through the CertCentral console or through the CertCentral Services API.

Now, when you submit verified contacts with multiple validation types, we assign each validation type to the same verified contact, instead of creating a duplicate.

On December 6, 2022, at 10:00 MST (17:00 UTC), DigiCert will no longer issue EV Code Signing certificates with a permanent identifier value in the Subject Alternative Name field.

What do I need to do?

Does your EV code signing process expect to find the permanent identifier when parsing your issued EV Code Signing certificates?

Does this change affect my existing EV Code Signing certificates?

This change does not affect existing EV Code Signing certificates with a permanent identifier value in the Subject Alternative Name field. However, if you reissue an EV Code Signing certificate after the change on December 6, 2022, your reissued certificate will not contain a permanent identifier.

Background

The permanent identifier is a unique code for EV code signing certificates that includes information about the certificate subject’s jurisdiction of incorporation and registration information. In 2016, the CA/Browser Forum removed the permanent identifier requirement from EV Code Signing certificates.

Starting December 6, 2022, DigiCert will require organizations on Code Signing (CS) and EV Code Signing (EV CS) certificate orders to have a verified contact.

This change was originally scheduled for October 19, 2022. However, we postponed the change to December 6, 2022. For more information, see the October 19, 2022 change log entry.

Learn more:

DigiCert will perform scheduled maintenance on December 3, 2022, 22:00 – 24:00 MST (December 4, 2022, 05:00 – 07:00 UTC).

Although we have redundancies to protect your services, some DigiCert services may be unavailable during this time.

DigiCert will perform scheduled maintenance on November 5, 2022, 22:00 –24:00 MDT (November 6, 2022, 04:00 – 06:00 UTC). Although we have redundancies to protect your services, some DigiCert services may be unavailable during this time.

We updated the Prove control over your domain popup window for pending DV orders, making it easier to see what you need to do to complete the domain validation for all domains included on your certificate.

Now, when you select a domain control validation (DCV) method, you can see basic instructions for completing the domain validation along with a link to more detailed instructions on our product documentation website.

See for yourself

Improved Prove control over your domain popup window

DigiCert is happy to announce that CertCentral allows you to upgrade your product when renewing your order.

Are you tired of placing a new order and reentering all your information when upgrading to a new product?

Now you don’t have to. We’ve improved our order renewal process so you can upgrade your product when renewing your certificate order.

Don’t see that option to upgrade your product when renewing your order, or already have the products you need and don’t want to see the option to upgrade?

Don’t worry; you can enable and disable this feature as needed. When ready to upgrade, you can enable it to save the hassle of placing a new order. When done, you can disable it until the next time you want to upgrade a product. See Upgrade product on renewal settings.

DigiCert is happy to announce that we updated the Code Signing and EV Code Signing request forms making it easier to view and add organization-related information when ordering a certificate.

This update allows you to select an organization and review the contacts associated with that organization or enter a new organization and assign contacts to the new organization.

Changes to note

Before, you could only see and select an existing organization and could not see the contacts assigned to the organization.

See for yourself

In your CertCentral account, in the left main menu, go to Request a Certificate > Code Signing or Request a Certificate > EV Code Signing to see the updates to the request forms.

When reissuing your code signing certificate, we now include the Subject Email Address on your reissued certificate. Adding a subject email is optional and only available in enterprise accounts.

Note that we will not include the subject email address in the reissued certificate if the domain validation on that email domain has expired.

Background

When you order a code signing certificate, you can include an email address on your code signing certificate—subject email. Including an email address on the certificate provides an additional layer of trust for end users when checking your code signing signature.

See 訂購 Code Signing 憑證.

We are happy to announce that you can now make the Additional emails field a required field on CertCentral, Guest URL, and Guest Access request forms.

Tired of missing important expiring certificate notifications because the certificate owner is on vacation or no longer works for your organization?

The change helps prevent you from missing important notifications, including order renewal and expiring certificate notifications when the certificate owner is unavailable.

See for yourself:

To change this setting for CertCentral request forms:

To change this setting for Guest Access:

To change this setting for Guest URLs:

On October 20, 2022, the RSS feed for the docs.digicert.com change log is going down due to a platform migration.

It will return. Check back here for updates or contact us at docs@digicert.com to be notified when the new RSS feed is available.

Starting October 19, 2022, DigiCert will require organizations on Code Signing (CS) and EV Code Signing (EV CS) certificate orders to have a verified contact.

DigiCert has always required a verified contact from the organization to approve code signing certificate orders before we issue the certificate. Today, DigiCert can add a verified contact to an organization during the validation process. After October 19, verified contacts must be submitted with the organization.

To make the transition easier, when you submit a request to the Order code signing certificate API endpoint, DigiCert will default to adding the authenticated user (the user who owns the API key in the request) as a verified contact for the organization.

DigiCert will apply this default when:

To avoid a lapse in service, make sure users in your CertCentral account with active API keys have a job title and phone number.

Learn more

We are happy to announce that we updated the DigiCert site seal image and replaced the checkmark with a padlock.

The updated site seal continues to provide your customers with the assurance that your website is secured by DigiCert—the leading provider of digital trust.

In CertCentral, we reorganized and updated the look of the Code Signing and EV Code Signing certificate request forms. These forms are now more consistent with the look and flow of our TLS/SSL certificate request forms.

On the code signing request form, when adding a Subject email address to appear on the certificate, you can now see the validated domains assigned to the organization with which the code signing certificate is associated.

DigiCert will perform scheduled maintenance on October 8, 2022, 22:00 –24:00 MDT (October 9, 2022, 04:00 – 06:00 UTC). Although we have redundancies to protect your services, some DigiCert services may be unavailable during this time.

DigiCert will end support for Cipher-Block-Chaining (CBC) ciphers in TLS connections to our services on October 8, 2022, at 22:00 MDT (October 9, 2022, at 04:00 UTC).

This change affects browser-dependent services and applications relying on CBC ciphers that interact with these DigiCert services:

This change does not affect your DigiCert-brand certificates. Your certificates will continue to work as they always have.

To give you more control over your domain prevalidation workflows, we added a new optional request parameter to the Add domain API endpoint: keep_www. Use this parameter to keep the www. subdomain label when you add a domain using a domain control validation (DCV) method of email, dns-txt-token, or dns-cname-token.

By default, if you are not using file-based DCV, the Add domain endpoint always removes the www. subdomain label from the name value. For example, if you send www.example.com, DigiCert adds example.com to your account and submits it for validation.

To keep the www and limit the scope of the approval to the www subdomain, set the value of the keep_www request parameter to true:

{
  "name": "www.example.com",
  "organization": {
    "id": 12345
  },
  "validations": [
    {
      "type": "ov"
    }
  ],
  "dcv_method": "email",
  "keep_www": true
}

CertCentral supports including a revocation reason when revoking a certificate. Now, you can choose one of the revocation reasons listed below when revoking all certificates on an order or when revoking an individual certificate by ID or serial number.

Supported revocation reasons:

*Note: Selecting Key compromise does not block using the associated public key in future certificate requests. To add the public key to the blocklist and revoke all certificates with the same key, visit problemreport.digicert.com and prove possession of the key.

Revoke immediately

We also added the Revoke this certificate immediately option that allows Administrators to skip the Request and Approval process and revoke the certificate immediately. When this option is deselected, the revocation request appears on the Requests page, where an Administrator must review and approve it before it is revoked.

Background

The Mozilla root policy requires Certificate Authorities (CAs) to include a process for specifying a revocation reason when revoking TLS/SSL certificates. The reason appears in the Certificate Revocation List (CRL). The CRL is a list of revoked digital certificates. Only the issuing CA can revoke the certificate and add it to the CRL.

DigiCert will perform scheduled maintenance on September 10, 2022, 22:00 –24:00 MDT (September 11, 2022, 04:00 – 06:00 UTC). Although we have redundancies to protect your services, some DigiCert services may be unavailable during this time.

In the CertCentral Services API, we added the option to choose a revocation reason when you submit a request to revoke a TLS/SSL certificate.

You can choose a revocation reason when revoking all certificates on an order or when revoking an individual certificate by ID or serial number.

To choose a revocation reason, include the optional revocation_reason parameter in the body of your request.

Example JSON request body:

{
  "revocation_reason": "superseded"
}

For information about each revocation reason, visit the API documentation:

In the CertCentral Services API, we added a new contact_type label for verified contacts: verified_contact.

Use the verified_contact label to identify verified contacts for an organization when you submit a request for an EV TLS, Verified Mark, Code Signing, or EV Code Signing certificate. The updated label applies to all verified contacts, regardless of which product type the order is for.

For example, this JSON payload shows how to use the verified_contact label to add a verified contact to an organization in a new certificate order request:

{
  "certificate": {
    ...
  }
  "organization": {
    "id": 12345,
    "contacts": [
      {
        "contact_type": "verified_contact",
        "user_id": 12345
      }
  },
  ...
}

Note: Before this change, verified contacts were always identified with the label ev_approver. The CertCentral Services API will continue accepting ev_approver as a valid label for verified contacts on EV TLS, VMC, Code Signing, and EV Code Signing certificate orders. The verified_contact label works the same as the ev_approver label, but the name is updated to apply to all products that require a verified contact.

We updated the Order code signing certificate API documentation to describe three ways to add an organization to your Code Signing (CS) or EV Code Signing (EV CS) order requests:

Learn more: Order code signing certificate – CS and EV CS organization validation

DigiCert is happy to announce that CertCentral allows you to modify the common name and subject alternative names (SANs) on pending orders: new, renewals, and reissues.

Tired of canceling an order and placing it again because a domain has a typo? Now, you can modify the common name/SANs directly from a pending order.

Items to note when modifying SANs

See for yourself

See Edit common name and SANs on a pending TLS/SSL order: new, renewals, and reissues.

To make it easier for API clients to get the exact date and time domain validation reuse periods expire, we added new response parameters to the Domain info and List domains API endpoints:

Learn more:

Some DigiCert services will be down for about 15 minutes during scheduled maintenance on August 6, 2022, 22:00 – 24:00 MDT (August 7, 2022, 04:00 – 06:00 UTC).

To give API clients the option to hide unused certificates from API response data, we released new API endpoints to archive and restore certificates. By default, archived certificates do not appear in response data when you submit a request to the List reissues or List duplicates API endpoints.

New API endpoints

Updated API endpoints

We updated the List reissues and List duplicates endpoints to support a new optional URL query parameter: show_archived. If the value of show_archived is true, the response data includes archived certificates. If false (default), the response omits archived certificates.

Some DigiCert services will be down for a total of 20 minutes during scheduled maintenance on July 9, 2022, 22:00 – 24:00 MDT (July 10, 2022, 04:00 – 06:00 UTC).

DigiCert is happy to announce that we improved the layout and design of the Order details page.

We took your feedback and updated the Orders page to make managing your certificates and orders easier throughout their lifecycle.

When we reorganized the information on the Order details page, we didn’t remove anything. So, everything you did before the updates, you can still do now. However, there are a few things you asked for that you can do now that you couldn’t do before.

DigiCert is happy to announce that we improved the CAA resource record checking feature and error messaging for failed checks in CertCentral.

Now, on the order’s details page, if a CAA resource record check fails, we display the check’s status and include improved error messaging to make it easier to troubleshoot problems.

DigiCert is happy to announce that CertCentral bulk domain validation now supports two more domain control validation (DCV) methods: DNS TXT and DNS CNAME.

Remember, domain validation is only valid for 397 days. To maintain seamless certificate issuance, DigiCert recommends completing DCV before the domain's validation expires.

Don't spend extra time submitting one domain at a time for revalidation. Use our bulk domain revalidation feature to submit 2 to 25 domains at a time for revalidation.

DigiCert 很榮幸宣佈以下的 CertCentral Report Library API 增強：

DigiCert 將在 2022 年 6 月 4 日北美山區夏令時間 22:00 到 -24:00 (2022 年 6 月 5 日世界協調時間 04:00 到 06:00) 執行排程的維護。雖然我們有保護您的服務的適當備援，但有些 DigiCert 服務在這段時間內仍可能無法使用。

更新：為了提供更多時間給 API 消費者評估他們的整合上的訂單資訊 API 回應的影響，我們將此更新延期到 2022 年 5 月 31 日。我們原本計畫在 2022 年 4 月 25 日釋出以下所述的變更。

2022 年 5 月 31 日，DigiCert 將對 Order info API 做出以下的改進。這些變更移除了未使用的值與，並將訂單詳細資料物件的資料結果更新為與不同產品類別的不同狀態中的訂單更一致。

如需更多有關公用 TLS、代碼簽署、文件簽署和第 1 類 S/MIME 憑證的資訊與回應範例，請參閱訂單資訊端點的參考文件。

如果您有疑問或需要這些變更的協助，請聯絡您的客服代表或 DigiCert 支援團隊。

2022 年 5 月 24 日 9:00 am 和 11:00 am MDT (3:00 pm 和 5:00 pm UTC) 之間，DigiCert 將取代以下所列的 GeoTrust 和 RapidSSL 中繼 CA (ICA) 憑證。我們不再發行來自這些中繼授權單位的最長有效期 (397 天) DV 憑證。

請參閱 DigiCert ICA 更新知識庫文章。

DigiCert 很榮幸發佈我們的新金鑰產生服務 - KeyGen。使用 KeyGen 從您的瀏覽器產生和安裝您的用戶端和代碼簽署憑證。KeyGen 可以使用在 macOS 和 Windows 上，而且所有主要瀏覽器都支援。

使用 KeyGen 不需要產生 CSR 即可訂購您的用戶端和代碼簽署憑證。不使用 CSR 下訂單。在我們處理訂單和您的憑證就緒後， DigiCert 傳送附有關於使用 KeyGen 的指示的 "Generate your Certificate" (產生您的憑證) 電郵以取得您的憑證。

我們修復了在沒有使用者與訂單關聯時，訂單資訊 API (GET https://www.digicert.com/services/v2/order/certificate/{{order_id}}) 傳回 user 欄位的錯誤資料類型的問題。現在，對於沒有使用者資料的訂單，訂單資訊端點傳回空白的 user 物件 ("user": {} )，而非傳回空白的陣列 ("user": [])。

更新：在 5 月 7 日 MDT 時間 (5 月 8 日 UTC 時間) 維護期間沒有計畫的停機時間。

DigiCert 將在 2022 年 5 月 7 日 22:00 到 24:00 MDT (2022 年 5 月 8 日 4:00 到 06:00 UTC) 之間執行排程的維護。雖然我們有保護您的服務的適當備援，但有些 DigiCert 服務在這段時間內仍可能無法使用。

服務將在我們完成維護時盡快還原。

我們很榮幸宣佈現在 CertCentral 和 CertCentral Services API 中的經過驗證的標章憑證 (VMC) 可使用多年期套餐。

DigiCert® 多年期套餐允許您支付一次優惠費用即可得到最長六年的經過驗證的標章憑證涵蓋時間。在多年期套餐中，您可以選取想要的涵蓋時間長度 (最長 6 年)。訂單到期前，每次重新發行憑證時都無需其他費用，直到有效期間結束為止。

DigiCert 很榮幸發佈現在在 CertCentral Services API 中可使用我們的網域鎖定功能。

新 API 端點

更新的 API 端點

我們更新了網域資訊和列出網域端點的回應，納入以下有網域鎖定資料的參數：

若要瞭解更多資訊，請參閱 :

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 lets you 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:

從 2022 年 4 月 5 日 MDT 起，您再也無法將您的 Symantec、GeoTrust、Thawte 或 RapidSSL 帳戶升級至 CertCentral™。

如果您尚未轉移到 DigiCert CertCentral，請立刻升級，保持您的網站安全並持續使用您的憑證。

DigiCert 將在 2022 年 4 月 2 日 22:00 到 24:00 MDT (2022 年 4 月 3 日 04:00 到 06:00 UTC) 之間執行排程的維護。在此期間，有些服務可能停機最多兩小時。

DigiCert 很榮幸宣佈我們的大量網域驗證功能現在已可以使用。不要花費額外的時間一次提交一個網域進行重新驗證。使用我們的大量網域重新驗證功能，一次提交 2 到 25 個網域進行重新驗證。

請記住，網域驗證的有效期間只有 397 天。若要保持無縫發行憑證，DigiCert 建立在網域的驗證到期前預先完成網域控制驗證 (DCV)。

自己查看

請參閱 網域預先驗證：大量網域重新驗證。

自 2022 年 3 月 24 日起，當您瀏覽 SSL 工具時，您將看到讓您知道 SSL 工具再也無法使用的彈出訊息。我們鼓勵您使用 DigiCert® SSL 安裝診斷工具。

DigiCert Basic OV 和 EV 憑證訂單包含 DigiCert 網站圖章。現在，您可以在相同的網站上，安裝您的 Basic SSL 憑證保護的 DigiCert 網站圖章。網站圖章向您的客戶提供您的網站安全受到 DigiCert (TLS/SSL 安全性之中最著名的名稱之一) 保護的保證。

當您按下網站圖章時，您會看到更多與網域、組織、TLS/SSL 憑證和驗證有關的詳細資料。

瞭解如何設定與安裝您的 DigiCert 網站圖章

在 CertCentral 和 CertCentral Services API 中，現在您可以使用 DNS CNAME 網域控制驗證 (DCV) 方法驗證您的 DV 憑證訂單上的網域。

若要使用您的 DV 憑證訂單上的 DNS CNAME DCV 方法：

若要瞭解更多有關使用 DNS CNAME DCV 方法的資訊：

為了更容易找到與您的 CertCentral 帳戶中的網域控制驗證 (DCV) 狀態有關的資訊，我們在列出網域 API 回應的網域物件中加入這些回應參數：

如需更多資訊，請參閱列出網域端點的參考文件。

DigiCert 將在 2022 年 3 月 5 日 22:00 到 24:00 MST (2022 年 3 月 6 日 05:00 到 07:00 UTC) 之間執行排程的維護。在此期間，有些服務可能停機最多兩小時。

在 CertCentral 和 the CertCentral Services API 中，我們已更新 EV TLS 憑證請求程序為僅傳送 EV TLS 請求核准電郵給在您的憑證要求上納入的經過驗證的聯絡人。

新增經過驗證的聯絡人到 EV TLS 憑證要求中：

若要瞭解更多有關 EV TLS 憑證要求的資訊：

在 2022 年 2 月 12 日 22:00 – 24:00 MST (2022 年 2 月 13 日 05:00 - 07:00 UTC) 的排程維護是我們的排程維護的一部份，DigiCert 正在擴大我們用於我們的服務的 IP 位址範圍。這些其他 IP 位址是我們努力增加服務運作時間，以及減少排程維護時間所做的努力的一部份。

我們更新了網域資訊 API 回應，納入與網域關聯的 DCV 權杖的 expiration_date 參數。現在，當您呼叫 Domain info API 並將 include_dcv 查詢參數的值設定為 true 時，回應中的 dcv_token 物件加入了網域的 DCV 權杖的 expiration_date。

{
  ...
  "dcv_token": {
    "token": "91647jw2bx280lr5shkfsxd0pv50ahvg",
    "status": "pending",
    "expiration_date": "2022-02-24T16:25:52+00:00"
  },
  ...
}

CertCentral 系統管理員現在可指定電郵網域使用者建立 CertCentral 帳戶所針對的內容。這有助於防止將電郵傳送到未核准、一般的電郵網域 (@gmail.com, @yahoo.com) 或第三方擁有的網域。如果使用者嘗試將使用者電郵地址設定或變更為未核准的網域，他們會收到錯誤。

在設定 > 喜好設定中尋找此設定。展開進階設定，然後尋找核准的電郵網域區段。

我們很榮幸宣佈 DigiCert 現在可識別的驗證您的 VMC 憑證所使用標誌的智慧財產局增加了三個。這些新的辦事處位於韓國、巴西和印度。

新核准的商標局：

其他核准的商標局：

什麼是「經過驗證的標章憑證」？

經過驗證的標章憑證 (VMC)是新型的憑證，允許公司將通過認證的品牌標誌放在客戶收件匣的「寄件者」欄位旁邊。

瞭解更多有關 VMC 憑證的資訊。

我們修復 Code Signing (CS) 憑證發行程序中的 Bug，其中我們僅傳送憑證產生電郵給 CS 驗證的聯絡人。此 Bug 只會發生在要求者未要求者未納入有代碼簽署憑證要求的 CSR 時。

現在，對於提交的沒有 CSR 的訂單，我們將代碼簽署憑證產生電郵傳送到：

我們致力於統一我們的 DV、OV 和 EV TLS 憑證設定檔，因此對我們的 EV TLS 憑證設定檔做了小變更。2022 年 1 月 25 日，我們在我們的 OV 和 EV TLS 憑證設定檔中，將 Basic Constraints 延伸程式設定為非重大。

在網域頁面的驗證狀態下拉清單中，我們更新了已完成/已驗證篩選器，因此更容易找到已完成和啟用網域控制驗證 (DCV) 的網域。

現在，當您搜尋有已完成/已驗證 DCV 的網域時，我們僅傳回您的搜尋結果中已完成和啟用 DCV 的網域。若要尋找 DCV 已到期的網域，請使用驗證狀態下拉清單中的已到期篩選器。

尋找已完成和啟用 DCV 的網域

對於 List domains API，我們更新了 filters[validation]=completed 篩選條件，因此更容易找到為了發行 OV 或 EV 憑證而驗證的網域。

之前，此篩選條件傳回完成 DCV 檢查的所有網域，即使網域驗證已到期。現在，篩選條件僅傳回 OV 或 EV 網域驗證狀態為啟用的網域。

我們更新了網域和網域詳細資料頁面，因此更容易追蹤和保持您的網域的最新驗證。這些更新符合去年業界對網域驗證重新使用期*的變更。將您的網域驗證保持為最新減少了憑證發行時間：新的、重新發行、重複發行和續訂。

DigiCert 將在 2022 年 1 月 8 日 22:00 到 24:00 MST (2022 年 1 月 9 日 05:00 到 07:00 UTC) 之間執行排程的維護。雖然我們有保護您的服務的適當備援，但有些 DigiCert 服務在這段時間內仍可能無法使用。