Skip to main content

SSL Certificate Application Submission Information

This article provides a detailed explanation of the full process for submitting SSL certificate application information, covering the CSR generation guide on the Racent platform, configuration methods for domain validation (email/DNS/file), and filling specifications and precautions for wildcard certificates and OV/EV certificates, helping you complete your certificate application efficiently.

There are two ways to generate a CSR:

  1. You can use a tool to generate it. The CSR generated by the tool requires you to keep the key .key file yourself.

  2. When submitting application information through the Racent platform, use "One-click CSR generation".

tip

The certificate key issued from a CSR generated through the Racent platform can be found and downloaded in the details section after the certificate is issued.

Generate a CSR with a Tool First​

  • Open the tool: CSR generation tool link

  • Use the tool to generate a CSR (all information must be filled in, and there must be no leading or trailing spaces)

  • Keep the private key safe yourself (.key file)

    sslrequest

Prerequisites for Submitting a Certificate Application

When submitting a certificate application, the prerequisite is that you have already purchased a certificate.

Purchase steps: On the SSL Certificate page -> click Buy SSL Certificate -> select the desired certificate and place the order.

For specific purchase details, please refer to SSL Certificate Purchase Guide

Certificate Application Steps​

Log in to Racent​

Go to the SSL Certificate Page​

  • Click the "SSL Certificate" option.

    sslrequest

Go to the Submission Page​

  • Find the previously purchased SSL certificate and click the "Submit Information" option after it.

    sslrequest

Fill in the Domain and Select the Validation Method​

  • Enter the domain name to be protected by the certificate, and select the domain validation method (DNS/file/email validation).

    sslrequest

    Tip
    • Wildcard certificates must be submitted in the following format when requesting a certificate: for example, example.com requires adding *. before the domain name, and entering *.example.com in the input field.
    • Wildcard certificates do not support file validation.

Fill in Organization Information/Personal Information​

  • Fill in the remaining information based on the type of certificate, such as organization information, personal information, etc.

    • DV certificate : A valid email address is required; other information can be left as default.

      sslrequest

    • OV/EV certificate: All information must be filled in, and must be valid and accurate.

      sslrequest

      Note
      • The address for Sectigo enterprise-level orders must be the registered address.

Fill in the CSR​

  • After filling in all the information, click the "Generate CSR with One Click" option at the bottom of the page, and then click "Submit" to submit the certificate request.

    sslrequest
    Note
    • If the CSR was generated using the first method or another tool, you can paste the CSR directly into the input field above.
    • A CSR generated elsewhere must exactly match the information filled in above (such as organization name and domain name).
    • If the filled-in information does not match the CSR, the issuance process may be delayed (for example, the certificate remains in the request status) or the certificate may need to be requested again.

Domain Validation Methods​

After submitting the certificate request, you need to validate the domain. There are three methods for domain validation:

  • Email validation
  • DNS validation
  • File validation

Email Validation​

You can only use the following five administrator email addresses and the Whois email address for validation (using example.com as an example).

Note
  • For domain validation, select email validation, choose one of the email addresses above, open the corresponding mailbox, and click the verification link.
  • Various CAs have gradually discontinued the Whois email validation method.

DNS Validation​

After the order is submitted, you can view the DNS resolution records in the list and details:

sslrequest

Set a specific record value to verify domain validity. See the article: 《DNS Resolution Verification Settings for Different Platforms》

To check whether the resolution has been added successfully, see 《How to Check Whether DNS Resolution Records Are Set Up Successfully》

File Validation​

Place the validation file in the server root path of the domain, typically:

  • http://example.com/.well-known/pki-validation

After submitting the materials, the SSL certificate order page will provide the content required for file validation. For detailed file validation instructions, see 《SSL Certificate File Validation Instructions》

Notes​

Note
  • Wildcard certificates do not support file validation
  • IP can only use file validation (CFCA file validation does not restrict port numbers)
  • Digicert DV orders require adding the resolution before submitting
Last updated on