篩選依據: FileAuth x 清除
compliance

Industry changes to file-based DCV (HTTP Practical Demonstration, file auth, file, HTTP token, and HTTP auth)

To comply with new industry standards for the file-based domain control validation (DCV) method, you can only use the file-based DCV to demonstrate control over fully qualified domain names (FQDNs), exactly as named.

To learn more about the industry change, see Domain validation policy changes in 2021.

How does this affect me?

As of November 16, 2021, you must use one of the other supported DCV methods, such as Email, DNS TXT, and CNAME, to:

  • Validate wildcard domains (*.example.com)
  • To include subdomains in the domain validation when validating the higher-level domain. For example, if you want to cover www.example.com, when you validate the higher-level domain, example.com.
  • Prevalidate entire domains and subdomains.

To learn more about the supported DCV method for DV, OV, and EV certificate requests:

compliance

CertCentral: Pending certificate requests and domain prevalidation using file-based DCV

Pending certificate request

If you have a pending certificate request with incomplete file-based DCV checks, you may need to switch DCV methods* or use the file-based DCV method to demonstrate control over every fully qualified domain name, exactly as named, on the request.

*Note: For certificate requests with incomplete file-based DCV checks for wildcard domains, you must use a different DCV method.

To learn more about the supported DCV methods for DV, OV, and EV certificate requests:

Domain prevalidation

If you plan to use the file-based DCV method to prevalidate an entire domain or entire subdomain, you must use a different DCV method.

To learn more about the supported DCV methods for domain prevalidation, see Supported domain control validation (DCV) methods for domain prevalidation.

compliance

CertCentral Services API

If you use the CertCentral Services API to order certificates or submit domains for prevalidation using file-based DCV (http-token), this change may affect your API integrations. To learn more, visit File-based domain control validation (http-token).

enhancement

CertCentral:自動 DCV 檢查 – DCV 輪詢

我們很榮幸宣佈我們已改進了網域控制驗證 (DCV) 程序,並新增了 DNS TXT、DNS CNAME 和 HTTP 現實論證 (檔案驗證) DCV 方法的自動檢查。

這表示,您將 fileauth.txt 檔案放到您的網域上,或新增隨機值到您的 DNS TXT 或 DNS CNAME 記錄後,您不需要擔心登入 CertCentral 以自行執行檢查。我們將自動執行 DCV 檢查。雖然您仍可以在需要時執行手動檢查。

DCV 輪詢步調

在提交您的公用 SSL/TLS 憑證訂單、提交網域進行預先驗證或變更網域的 DCV 方法後,DCV 輪詢會立刻開始並執行一星期。

  • 間隔 1 - 前 15 分鐘的每一分鐘
  • 間隔 2 - 每五分鐘,為期一小時
  • 間隔 3 - 每十五分鐘,為期四小時
  • 間隔 4 - 每一小時,為期一天
  • 間隔 5 - 每四小時,為期一周*

*在間隔 5 後,我們停止檢查。如果您在第一星期結束前尚未將 fileauth.txt 檔案放到您的網域上,或新增隨機值到您的 DNS TXT 或 DNS CNAME 記錄中,您需要自行執行檢查。

如需更多有關支援的 DCV 方法的資訊: