Frequently Asked Questions

Certainly! You have to check it again because each certification authority has strict rules for confirming the information you give them.

Certainly! Please resend the documents because we treat it as a new purchase.

The time it takes to get a new SSL certificate varies based on several factors. These include the type of SSL certificate, the validation process, and how quickly you respond with the requested information from us or the certificate authority.

All major web and mobile browsers are compatible with the SSL certificates provided by us.

If there are some browsers which are incompatible with it, then those browsers are either very old, and nobody uses them anymore, or they are custom made browsers, and again, very few or no people use them.

The trial certificate is just like our regular SSL Certificates. It works in all browsers and has strong encryption. You can use it to test your systems before using the official certificate. Since it's free, we have a limit on how many trial certificates we can give out.

Certainly! Sure, if you plan to renew your certificate within 90 days before it expires, we can transfer the remaining days to the new certificate you wish to buy.

No, you need to create a new CSR (Certificate Signing Request) and send it to us. Then we can give you a certificate.

Certificate Authorities understand that thorough validation is crucial for the ongoing success of online businesses. Before granting a certificate, we check that the person applying either owns the domain name or has the legal right to use it. Additionally, we confirm that the applicant is a genuine and legally responsible entity. To accomplish this, we need to review relevant documents that confirm these details.

You don't have to provide any documents to buy a Domain Validated (DV) certificate. Just make sure you confirm that you own the domain by responding to the email you get from the Certificate Authority (CA).

Organization Validation verification involves checking your business registration. If the Certificate Authority (CA) can confirm it online, no extra documents are needed. But if online data is unavailable or inaccurate, the CA might ask for additional official government registration documents, depending on the situation.

Please find the list of documents to be provided given below :-

a) SSL Documentation Form,

b)Acknowledgement of Agreement letter

c)Professional Opinion Letter (if required)

If you don't receive the DRC email, the Certifying Authority (CA) can send it again. Alternatively, you can use a Professional Opinion Letter (POL)."

In order to reschedule this, please contact us and provide your availability. Please note, not all telephone numbers are suitable. The number must be verified by the Certificate Authority (CA), so please confirm the number that the CA will be calling.

Once we check and confirm everything, we'll send the certificate to the email address you gave us for technical communication. If the email doesn't show up, please get in touch with us, and make sure to check your Spam and Junk Mail folders first.

Certainly, you can use this for EV, OV, and DV Certificates.

It depends on the type of certificate and the validation process of the Certificate Authority. Domain Validated (DV) Certificate can take a few minutes to a business day, Organization Validated (OV) Certificate can be issued within 2-3 days to be issued and Extended Validation (EV) Certificate usually take around 5-10 business days to be issued.

We can include the phone number you give us in the Professional Opinion Letter (POL) and confirm it so the CA can reach out to you.

No, they support the key size set by the web server or browser. If the web server or browser can only use 40 or 128 bits, then that's the session that gets created.

The problem is probably because a middle certificate hasn't been loaded. To check if your certificate is installed correctly, go to our Online Support Center and follow the SSL Certificate Installation instructions.

This error normally occurs due to following reasons:

1. The website's files aren't in the secure "https" directory on the web server. You can check this by trying to access the file using an unsecured "http" call. If the pages don't load correctly, add the files to the "https" directory in the SSL configuration.
2. Port 443 is blocked by the server's or the user's firewall. To fix this, open up port 443 for both inbound and outbound traffic on the firewall.
3. The https server is not working. Check your web server's task manager to see if the server running the https service is up.
4. There might be an issue with the SSL certificate. Make sure your SSL certificate has a corresponding private key file. Refer to the installation documents for your web server on our support site to confirm that you've installed the SSL certificate correctly with the corresponding private key file.

If your website isn't loading securely (https), it might be because you're trying to load content over an insecure connection (http) when you're in SSL mode. Check your website's code and make sure there are no references to files or graphics like 'src=http://www.yourcompany.com/directory/file.gif.' 

If you have such references, make them relative (like 'src=/directory/file.gif') or use https (like 'src=https://www.yourcompany.com/directory/file.gif')."

This problem happens when you try to use a certificate on a website with a different full address than the one it was meant for. For instance, if the certificate is for www.yourcompany.com, using it on secure.yourcompany.com will cause an error because they don't match.

You might also encounter a Security Alert if you forgot to install the intermediate certificate and restart your server.
 

If your Load Balancer is connected to the internet and handles SSL offloading, you only need one SSL Certificate. The purpose of a load balancer is to make all your servers look like one to the client.

If you plan to use a domain name (like http://myservice.com) instead of an IP address (like http://192.168.0.1) for your website, the IP address for SSL doesn't have to stay the same all the time; it just needs to be exclusively used for your site. The challenge with using SSL on a changing IP address is that you'll need to adjust your DNS settings to keep up with the changes in your IP address.

Having a unique IP address for every website can cause issues because there are limited IP addresses available. To tackle this, Server Name Indication (SNI) comes into play. Browsers that support SNI share the website name they're trying to connect with when establishing a secure connection. This helps the server know which certificate to send. With SNI, multiple certificates for different domain names can be linked to a single IP address. So, visitors won't experience any noticeable differences when accessing your website.

Sometimes, the name on a website certificate and the address in your browser might not exactly match. This can happen if "www." is missing in the browser, if the certificate is assigned incorrectly, or if the purchased certificate doesn't cover the specific subdomain or domains you're trying to access.

The old standard for SSL certificates was 1024 bits, but it's not considered safe enough since 2010. Major certification authorities and their partners now only accept root keys that are 2048 bits or longer.

The size of your SSL certificate's root key, whether it's 4096 bits or 2048 bits, doesn't make a big difference because both are very secure. Most certificate authorities accept both 2048 and 4096 bit root keys. The latest web browsers can handle certificates with up to 4096 bits.

In recent years, there have been fake SSL certificates created because of mistakes by certificate authorities (CAs) or compromised server infrastructure. These fake certificates make websites look secure and verified, tricking web browsers and users into thinking they're visiting a safe site.

SSL certificates are crucial for the HTTPS protocol. They are signed by a trusted CA and issued only after verifying that the requester is the real owner of the domain.

Google's Certificate Transparency project addresses flaws in the SSL certificate system that supports HTTPS connections. It doesn't prevent bad certificates but allows anyone to check all certificates issued by a CA through centralized logging. This transparency helps identify unusual activity and allows companies to monitor certificates created with their domains. More log servers can be added by other CAs, increasing transparency as the popularity of Certificate Transparency grows.

The usual platforms include Microsoft, JAVA, Adobe, Android, and more. Developers use these platforms to create and sign their apps using specific tools. Each platform has its own unique features.

You might have difficulty downloading the code signing certificate, and this could be because of a few reasons. Firstly, if you're not using the same web browser that you used to create the certificate signing request (CSR) or if you're not using the browser correctly, you'll get an error message. Secondly, if you're not on the same computer where you placed the order, using a different computer will cause the corresponding private key to be missing, and you won't be able to download the code signing certificate.

• First, check if you have a backup. Try reinstalling the "private key" from your backups. If you're unsure how to do this, reach out to your system administrator or call us for technical support.
• If all else fails, the last option is to reissue your SSL Certificate. To do this, create a new CSR (Certificate Signing Request) and send it to us. We'll then reissue your certificate for you.

The problem is likely because the middle certificate is not installed. To fix it, please install the middle certificate.

When you're getting an SSL Certificate, put the website name you want it for in the Common Name field. Don't add 'http://' before the name, and don't include any slashes or subfolders after the name.

If they have the Private Key and you're using the original CSR, your encrypted sessions could be at risk. But if you use a new CSR, even if someone has the Private Key, they won't be able to decrypt your sessions once you apply the new certificate.