Frequently Asked Questions (FAQ)

There are 3 types of SSL Certificates
• Domain Validated (DV) certificates provide the lowest level of authentication, meaning anonymous entities are able to obtain a certificate. These certificates are low-cost certificates that only require the user to demonstrate control over a web domain for which the subscriber wants to obtain a certificate.
• Organization Validated (OV) certificates provide additional checks of the website. CAs verify domain ownership of OV certificates similarly to DV certificates. What distinguishes OV from DV is the steps taken by CAs to authenticate that the business organization (i.e. Inc., Corp, LLC, Ltd, Pty Ltd, etc.) is valid and remains in good standing.
• Extended Validation (EV) certificates guarantee the highest standard of brand protection. With EV, brands signal a commitment to customers that transactions are secure. In addition to all the authentication steps of DV and OV certificates, EV certificates require vetting of the business organization’s operational existence, physical address and a telephone call to verify the employment status of the requestor. Dual-person validation is required as well.

Domain Validation (DV) only requires the user to demonstrate control over the web domain for which they want to obtain a certificate. Only Domain Validation and Order Acknowledgment are required.

Organization Validation (OV) requires multiple verification steps to ensure that the organization is a legally active entity, has control over the domain, and that the contact person is employed with the organization. This process is designed to prove the existence of the company. Order Acknowledgement required.
OV validation consists of the following steps:
Domain Validation
Legal Existence
Physical Existence
Validation of Authority
Phone Verification

Extended Validation (EV) certificates: guarantee the highest standard of brand protection. With EV, brands signal a commitment to customers that transactions are secure. In addition to all the authentication steps of DV and OV certificates, EV certificates require vetting of the business organization’s operational existence, physical address and a telephone call to verify the employment status of the requestor. Order acknowledgment are required.
EV validation consists of the following verification steps:
-Domain Validation
-Legal Existence
-Physical Existence
-Jurisdiction of Incorporation (JOI)
-Operational Existence
-Registration Number Format Checking
-Validation of Authority
-Phone Verification
-Certificate Request Form

DV certificates provide the lowest level of authentication, meaning anonymous entities can get a certificate. The certificate doesn’t contain information about the owner of the certificate, and only the internet domains contained in the certificate are validated

OV certificates provide additional checks to ensure brand protections.The certificate contain the identity of the owner of the certificate, and this information must be validated

EV certificates guarantee the highest standard of brand protections. The certificate must contain more specific information about the owner, and
the validation of this information must be done according to more strict processes

Yes, all TuringSign SSL certificates work well across the main browsers, including Google Chrome, Mozilla Firefox, Microsoft Edge, Apple Safari, and 360 Browser.

Static site seals are non-interactive image files displayed on a website to signal to visitors that the site has security measures in place. Unlike clickable seals, they simply serve as visual indicators of security and cannot be interacted with.
Dynamic seals are interactive; they can be clicked to reveal detailed security information and provide a higher level of assurance to website visitors. In the realm of e-commerce, where trust is crucial, dynamic site seals are designed to instill the greatest confidence. They are often associated with premium security certificates, such as OV and EV certificates.

TuringSign offers a 30-day refund policy for a full refund on TLS/SSL certificates. Orders can be canceled within 30 days of issuance. You can request a refund for your TuringSign purchase through our Sales team at [email protected].

The maximum validity period of SSL certificate is 397 days.

The issuance time for your certificate largely depends on the type you purchased and your response times. The certificates are typically issued immediately after the validation process is completed.
DV Certificates: Typically issued within minutes to be issued.
OV / EV Certificates: Usually take around 1-3 business days to be issued.

Yes,TuringSign Multi-year Subscription Plans allow you to pay a discounted price for up to 5 years of SSL/TLS certificate coverage. With these plans, you select the SSL/TLS certificate, choose the duration of coverage (up to 5 years), and set the certificate validity period.

If your SSL/TLS certificate is about to expire, please contact us to renew your certificate. As your certificate’s expiration date approaches, it’s important to prepare for a timely renewal. This process doesn’t have to be complicated. You will receive notifications well in advance of the expiration date and should start the renewal process 30 days before the certificate expires.

When you renew a certificate, you can use the original CSR, but this CSR will use the same private key, which may pose a security risk. Therefore, we highly recommend generating a new CSR and private key for the renewal process to enhance security.

You can revoke the certificate through the CertifyID TLS Manager portal by logging into your order information page. Alternatively, you can contact us via email or submit a ticket for assistance with certificate revocation.

Sales : [email protected]
Validation : [email protected]
TCS(Partners) : [email protected]
General / Technical Support : [email protected]

Please send your validation documentation to [email protected]. Alternatively, you can create a support ticket with the following criteria:
Inquiry Type: Validation Support
Case Reason: Validation Support

The 3 available methods to complete DCV are:

Email based
– Domain Control can be proven by responding to a CA/B forum approved email.
The email listed on the WHOIS record can be used for Domain Control Validation.
Certificate Authorities (CAs) are permitted to send DCV verification emails to a set of 5 constructed email addresses:
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

DNS TXT / CNAME Record Method
– Demonstrate control over your domain with a DNS CNAME Record.
– Demonstrate control over the domain on your order by creating a DNS TXT record containing a randomly generated value.

HTTP TXT File methods
– Demonstrate control over your domain by hosting a .txt file containing a randomly generated value at a predetermined location on your website.
– Wildcard DNS Names do not support the “Http TXT File” method.
– Http TXT File method is not valid for subdomains. Please ensure you validate the exact FQDN you need in the certificate.

Please use the following link to access our booking system and select the date/time most appropriate to call you.
https://tls.turingsign.com/user/callbookings

It depends on the type of certificate. Typically, TuringSign may use your previous documents for the renewal process of certain certificates. However, if any information about your organization has changed, you will need to submit updated documents. For an EV SSL order, full business validation is required again if the certificate was validated more than 13 months ago. For an OV SSL, you can reuse the previous information for up to 27 months from the original order.

Yes, TuringSign provides validation instructions for different SSL certificate types, including OV SSL and EV SSL.
Please download the validation guides for instructions on completing your validation.
Click here to download the Validation Instructions for OV SSL
Click here to download the Validation Instructions for EV SSL

TuringSign Root Certificate Information:

OISTE WISeKey Global Root GB

• Thumbprint: ‎0f f9 40 76 18 d3 d7 6a 4b 98 f0 a8 35 9e 0c fd 27 ac cc ed
• Valid From: 1st December 2014
• Valid To: 1st December 2039

File name:
oistewisekeyglobalrootgbca.crt
[Click here to download]

Manual for Checking and Installing a Root Certificate in JAVA [Click here to download]