Frequently Asked Questions

Answers to Common Questions

Can't find the answer you need? Please contact us and we will be happy to help!

FAQs about RunSSL & SSL Certificates

Here are some common questions answered about us and SSL certificates:

SSL is an acronym for Secure Sockets Layer, a security technology that encrypts connections between your web server and your visitors' web browser allowing for private information to be transmitted without the problems of eavesdropping, data tampering, or message forgery.
RunSSL offer a no quibble 30 day money back guarantee on all purchases, from the date of order.
Of course the 90 day FREE Trial via product page, this product is not limited to 1 time therefore can be renewed as required.
Domain validated SSL can be issued within minutes, given DCV is completed post haste. EV SSLs typically take upto 5 working days from order, though this dependant on the applicant submitting the required documents in a timely manner.
At present RunSSL accepted ALL payment via PayPal.
Firsty you will need a unique IP address. The way that the SSL protocol was set up, you will need a separate IP address for each certificate that you want to use. If you have multiple subdomains on one IP address, you can secure them with a Wildcard SSL Certificate. If you have multiple different domain names on one IP address, you can secure them with a certificate which support Subject Alternative Names such as the Comodo UCC or EV MDC SSL. A CSR. A certificate signing request or CSR is a piece of text that must be generated on your web server before ordering the SSL certificate. The certificate authority will use the information contained in the CSR it must have at least (domain name, public key, etc...) to create your certificate and obtain your Domain Validated Certificate. Correct contact information in WHOIS record. When you purchase a certificate for a particular domain name, the certificate authority needs to ensure that you own the domain name that you are getting the certificate for and that you are authorised to order the certificate. This is primarily done by making sure that the WHOIS record (the ownership and contact information associated with each domain name) matches the company name and address that is submitted with the certificate order. Some Certification Authorities will call the phone number listed in the WHOIS record and many will send an email to the address listed there so make sure you have the correct information listed. The ComodoSSL product support 3 Domain Control Validation methods:- Email, CNAME and HTTP (see Alternative Methods of Domain Control Validation (DCV)).

All Comodo certificates must pass through DCV (Domain Control Validation) before they are issued. DCV is a mechanism used to prove ownership or control of a registered domain name.

There are 3 mechanisms for DCV: eMail-based DCV (Traditional) You will be sent an email to an administrative contact for your domain. The email will contain a unique validation code and link. Clicking the link and entering the code will prove domain control. Valid email addresses are: Any email address which our system can scrape from a port 43 whois check;

The following generic admin type email addresses @ the domain for which the certificate is being applied: admin@ administrator@ postmaster@ hostmaster@ webmaster@ DNS CNAME-based.

The CSR you submit to Comodo will be hashed. The hash values are provided to you and must be entered as a DNS CNAME record for your domain. The hashes are to be entered as follows: CNAME

Note: Please take notice the trailing period/fullstop at the tail end of each of the TLDs as this is required to make the entry fully-qualified.
Note 2: in the example above (and below in the HTTP(S) method instructions) means the Fully Qualified Domain Name (FQDN) contained in the certificate.

If you are ordering a MDC or UCC certificate, separate CNAME records must be created for EACH FQDN in your order. Examples: CNAME CNAME HTTP(S)-based DCV.

The CSR you submit to Comodo will be hashed. The hash values are provided to you and you must create a simple plain-text file and place this in the root of your webserver and served over HTTP-only! The file and it's content should be as follows: Content (as a plain text file):

Note: The DCV will fail if any redirection is in place.
Note 2: in the example above (and in the CNAME method instructions; above) means the Fully Qualifed Domain Name (FQDN) contained in the certificate.

If you are ordering a MDC or UCC, each FQDN in the certificate MUST have the TXT file in place in its root folder. Examples:

1. DOMAIN VALIDATED CERTIFICATES (DV) • A - Email Challenge-Response DCV • B - HTTP Based DCV • C - DNS CNAME Based DCV Following completion of one of the elements above the certificate will be signed and released.

Additional details can be found using the following URL: Methods of Domain Control Verification Note that ALL SSL Certificates MUST undergo the above DCV process in addition to any other requirements listed below for OV and EV certificates.

It depends on the Servers software. The CSR generation process can be subtly different please refer to our partners knowledgeable article referenced here.

Certificate Installation can vary dependant on the server software type you may be using. Please refer to our partners knowledgebase article here for further information.

View our partner link here for further information.

View our partner link here for further information.