SSL Certificate File Validation Instructions
SSL file validation is a method used to verify SSL certificates, suitable for users who do not have domain management permissions but do have server management permissions. The following are the detailed steps for SSL file validation.
Obtain File Validation Content
Log In to Racent
- Log in to the Racent Platform and enter the console.
Go to the SSL Certificate Page
-
Click the "SSL Certificate" option.

Validate File Content
There are two places where you can view the validation file content:
-
Find the SSL certificate order for which you have submitted the information. Below it, you will see the "Content" and "File Name" required for file validation.

-
Find the SSL certificate order for which you have previously submitted the information, and click the 'Details' option after it.

After entering, scroll down to find the domain validation section and select file check. The "Content" and "File Name" required for file validation will be displayed.

Place the Validation File in the Domain Server Root Directory
Prerequisite: You have obtained the validation file content. We will use the content in the image above as an example:
// 文件验证内容
40b5df677f116ec811e2ee588f269917b3eed4f8316c9606267f0dc90851f548
comodoca.com
Place the content you obtained into A1F59FE3606C93982C0D98D7679B191A.txt in the .txt format at the root path of the domain's server.
The path is generally:
http://example.com/.well-known/pki-validation/A1F59FE3606C93982C0D98D7679B191A.txt
For file validation, every domain included in the certificate must undergo file validation separately. For example, a single-domain certificate contains example.com and www.example.com, and file validation must be performed separately by placing .txt
- The site root directory depends on the actual environment.
- Nginx default root directory:
/usr/local/nginx/html/ - Tomcat default root directory:
apache-tomcat/webapps/
- Nginx default root directory:
- IIS default root directory:
inetpub\wwwroot\
- The first-level directory is a hidden directory with a dot, and
Windowscontains the following command:mkdir .wellknownNoteCFCA supports validation on any port. For file validation of other brands
httpmust use the80port;httpsmust use the443port.
:::
Configuration Check
After uploading the validation file, you need to check whether the configuration is correct by opening the following links in a browser:
HTTPS configuration check link:
https://example.com/.well-known/pki-validation/A1F59FE3606C93982C0D98D7679B191A.txt
HTTP configuration check link:
http://example.com/.well-known/pki-validation/A1F59FE3606C93982C0D98D7679B191A.txt
example.com and A1F59FE3606C93982C0D98D7679B191A.txt need to be changed to your file validation content
:::
- If it is a single-domain certificate, you need to add
www.beforeexample.comand check whetherwww.example.comis configured successfully. - The same applies to multi-domain certificates.
On the SSL certificate details page, click the Verify button and wait patiently until verification is complete. After verification is complete, you can obtain the SSL certificate.
By following the steps above, you can successfully complete SSL file validation and ensure your website is secure and reliable.
OV and EV certificates also require organization validation