Domain Validation using Agreed-Upon Change to Website

The Baseline Requirements of the CA/Browser Forum provide several methods to validate control of a requested domain for SSL/TLS certificates. 
 
If you request a domain to be used in SSL/TLS certificates issued by QuoVadis you are presented with several choices to validate control of the domain:
  • Agreed-Upon Change to Website: Post a file provided by QuoVadis on the specified host to demonstrate Domain control. Requires access to the web space root directory
  • DNS Change: Create a DNS entry to demonstrate Domain control. Requires access to the DNS zone for the domain
  • QuoVadis Assisted Validation:   QuoVadis will assist you through alternate manual processes of validating control
BR section 3.2.2.4.6 describes a process using a Random Value published in an Agreed-Upon Change to Website using the requested domain to demonstrate control. You will be provided a Random Value by QuoVadis in the following form:
 
QuoVadis=example0-0000-0000-0000-example0000
To verify control of the Domain, please add the RandomValue in a file in the .well-known/pki-validation/fileauth.txt directory of your webspace.
 
http://example.com/.well-known/pki-validation/fileauth.txt  
or
http://www.example.com/.well-known/pki-validation/fileauth.txt  
Note: The Random Value must be in a txt file named “fileauth.txt”.  The address must not include the Random Value itself.
 
The Random Value is valid for 30 days, and validation must reoccur according to the applicable requirements of the certificate type (detailed in Section 4.2.1 of the Baseline Requirements or Section 11.14.3 of the EV Guidelines).

Add Feedback