Using the Approval URL method, where you can insert a meta tag on the root page of your domain.
Our verification system will be able to detect the meta tag on the page and verify the domain ownership.
We hope this blog will help you avoid those pitfalls and streamline your time to completion, but if you have a problem that you cannot solve using this blog you can still contact our support team or submit a support ticket on our website.
DNS TXT records entails implementing a code into the DNS TXT of the website.
Use this link for checking if a DNS TXT record is present on a domain.
Sometimes, even the most effective webmaster has problems with SSL/TLS Certificates.
Ordering the right certificate, creating a CSR, downloading it, installing it and testing it to make sure there are no problems are all areas where a webmaster can encounter problems.
If the private key is no longer stored on the server (lost) then the certificate will need to be reissued with a new CSR.
Examples of error messages/situations which would indicate there is no private key: For more information regarding SAN compatibility, see the below image.
For example, if the CN is " and you specified sub-domain as "domain.domain2.com" which actually specifies FQDN.
After installing the certificate, you may still receive untrusted errors in certain browsers.
For example, if you want to secure mail.and secure.domain.com, you will need to enter *.as the Common Name in the CSR.
This error appears when you are using a private key which has already been used. You should generate a new private key and CSR on their server and re-submit the new CSR.
When choosing the ‘switch from competitor’ option in our certificate ordering system, you may see the following error message: The server hosting your existing certificate cannot be reached to confirm its validity.