From 5bca88ae93ac5d088334e183d8d0f08e30cd8c83 Mon Sep 17 00:00:00 2001 From: zeinjaber <69680657+zeinjaber@users.noreply.github.com> Date: Fri, 26 Mar 2021 15:38:21 +0200 Subject: [PATCH] Update validation-backoff-schedule.md (#859) * Update validation-backoff-schedule.md * Update validation-backoff-schedule.md Think that info will be more visible if we separate it into a bulleted list Co-authored-by: kodster28 --- .../src/content/ssl-for-saas/validation-backoff-schedule.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/products/ssl/src/content/ssl-for-saas/validation-backoff-schedule.md b/products/ssl/src/content/ssl-for-saas/validation-backoff-schedule.md index f6d8384f3872426..5937f19c2855867 100644 --- a/products/ssl/src/content/ssl-for-saas/validation-backoff-schedule.md +++ b/products/ssl/src/content/ssl-for-saas/validation-backoff-schedule.md @@ -4,7 +4,11 @@ order: 7 # Validation backoff schedule -Attempts to complete domain validation with our CA partners are distributed over 14 days. Afterward, DCV tokens expire as dictated by the CA/B Baseline Requirements, which govern issuance of publicly trusted SSL certificates. +Domain validation happens with our CA partners according to the following schedule: +- Digicert - 14 days +- Let's Encrypt - 7 days + +Afterward, DCV tokens expire as dictated by the CA/B Baseline Requirements, which govern issuance of publicly trusted SSL certificates. Here is the function that is used to determine the next check: