RapidSSL certificate for only $19.99
Take advantage of our discounted offering on 1 year RapidSSL certificates.
- Single root certificate - issued in minutes, installed in seconds!
- The lowest cost single root install SSL certificate available
- Immediate SSL certificate issuance 24/7/365
- Automated two step online validation - no paperwork
- $10,000 warranty
- 99% browser recognition rate, no chained installation
- Web and email support - 9am to 5pm EST
- Strong 128 / 256 bit encryption, industry standard SSL
- FREE "Secured by RapidSSL" site seal
- Risk free: 7 day refund and reissue policy
- RapidSSL.com owns the root used to issue your certificate
How do can you offer RapidSSL certificates for less than RapidSSL?
We purchase in bulk and have very low overhead.
Is purchasing from RunSSL any different than buying direct from RapidSSL?
Yes, we are less expensive. Everything else is the same.
What is a token?
It is a link with a pin number and will be sent automatically after you complete payment. (Example below)
How long does it take to receive my token e-mail?
If you purchase via Paypal it takes around 3 minutes.
Do you accept checks?
Yes, you can pay via the Paypal eCheck system but you will not receive your token until after the check has cleared. This can take 3-5 business days.
Can I call RapidSSL for support?
Yes, you will be treated as if your purchased you SSL certificate directly from them.
Do you recognize the four ways to tell if you are connected to a website via SSL?
Earlier, we discussed how relying on SSL Certificate sites seals is not the proper way to confirm if you are connected to a website via SSL. In this tutorial we will outline the proper way.
Any time you are sending personal data or financial information look for the following:
1. Prefix in address bar will be https NOT http. This is not case sensitive.
2. You must have a lock in the status bar located at the bottom of your browser. NEVER as a image on the website itself.
What everyone ought to know about a SSL Certificate Site Seals.
You should never use use a site seal. Site seals train people improper ways of confirming whether or not they have a secure SSL connection. To correctly determine if you have a secure connection look for the lock icon on your browser and verify the credentials by double clicking the lock. Also make sure the web address has a "https" prefix not "http".
So that I do not give to much information away on how to fake a site seal, the images below are deliberately not complete. Additional steps could be taken to create a more believable affect. All trademarks are the property of their respective owners.
Do you really need a Wildcard SSL Certificate?
If you do not require a SGC or EV SSL Certificate and want to secure multiple sub domains that DO NOT require access via a mobile or cellular browser, a Wildcard SSL Certificate is perfect. Currently some mobile devices do not support Wildcard SSL certificates properly because they do not match the domain they are running on. For example *.runssl.com is the Wildcard SSL Certifciate for runssl.com. We could run it on store.runssl.com, www.runssl.com, and docs.runssl.com across different physical servers, running different operating systems, and different versions or types of web servers (apache, IIS, etc).
This is only cost effective if you have many sub-domains or different servers to protect because most Wildcard Certifcates cost 10 times the price as a single SSL Certificate. Therefore if you have 3 sub domains you want to protect (store.runssl.com, www.runssl.com, secure.runssl.com), it could make sense to purchase 3 separate single SSL Certificates vs. a Wildcard Certificate. The bonus is that if you do decide to purchase a Wildcard certificate, they are easier to manage.
As a part of the EV Certification, the CA/Browers Forum www.cabforum.org decided that EV Certificates must match the exact domain they run on (www.runssl.com, or store.runssl.com) and do not permit Wildcard EV SSL Certificates to be issued. If you need to run EV SSL Certificates across multiple servers/domains, please contact us for discount pricing.
How to redirect Drupal or Ubercart to a SSL connection with htaccess.
This tutorial outlines a quick and easy way of securing Ubercart by redirecting the cart and other directories to the SSL version.
Add the text below to the .htaccess file in your Drupal root directory AFTER any Drupal redirects you are already using. You will need to modify the RewriteRule lines below if your URLs do not match the ones I use in this example.
# Start code copy RunSSL.com Ubercart .htaccess redirect to SSL.
#
# Technique below is preferred over RewriteCond %{SERVER_PORT} 80
# because it does not require mod_ssl to be loaded
