The php.ini file is where you declare changes to your PHP settings. You can edit the existing php.ini, or create a new text file in any subdirectory and name it php.ini.

Every SSL certificate requires a domain name and a dedicated IP address. Shared web hosting accounts can host multiple domains, but all of the domains share the same IP address. We can only assign one IP address per account, therefore we can only allow one private SSL certificate per cPanel.

If you need multiple SSL certificates or multiple IP addresses, please purchase a reseller account or multiple shared web hosting accounts.

Wordpress is being used by a lots of users as it is user-friendly in developing sites and is available free of cost. Despite these advantage it has many loopholes that cannot be ignored. Wordpress team is continuously working and bringing forth new versions to the market but still the vulnerabilites are increasing every day on the internet. Some of the security loopholes in wordpress sites are as given below :

1) Without-charge WordPress themes have security issues
2) WordPress’s default login is unsafe
3) It is vulnerable to URL hacking and other security attacks

Steps to decrease Vulnerablilites
=================================
1) Moving wp-config.php file:

wp-config.php is the most inportant file in wordpress which you need to protect from being accessed directly so instead of keeping it in public_html folder you can move it one folder back. Below are the steps.

STEP 1: Download your wp-config.php file to local computer.

STEP 2: Now upload this file to any folder just one level above public-html or www folders. In short you have to upload it outside to public-html folder (if you have installed WordPress in root).

STEP 3: Now open your original wp-config.php (old) file and replace everything inside it with this code.

======================
<?php
include('/home/username/wp-config.php');
?>
======================

2) Stop directory listing:

By default any readable folder that is not having index file lists all the files inside when browsed. To avoid listing your files you can create index files in all the readable folders. Here is a better, more trusted and less time consuming solution. Just open your .htaccess file and add this code anywhere within it.

=====================
IndexIgnore *
=====================

You need to go through the below url for further details on securing wordpress site
============
http://codex.wordpress.org/Hardening_WordPress
============

Securing your site is rather easy, if you know what, where, and how it needs to be completed. This article may only scratch the surface, but will provide you with enough advice to perform a major upgrade in your site’s security in a few, easy steps.

1. Change the default database prefix (jos_)

Most SQL injections that are written to hack a Joomla! website, try to retrieve data from the jos_users table. This way, they can retrieve the username and password from the super administrator of the website. Changing the default prefix into something random, will prevent (most / all) SQL injections.

You can set the database prefix when installing your Joomla! website. If you've already installed Joomla! and want to change your prefix, do the following:
   * Log on to your Joomla! back-end.
   * Go to your global configuration and search for the database
   * Change your database prefix (Example: fdasqw_) and press Save.
   * Go to phpMyAdmin to access your database.
   * Go to export, leave all default values and press Start. Exporting the database can take a while.
   * When done, select all code and copy it to notepad (or any other text editor)
   * In phpMyAdmin, select all tables and delete them
   * In notepad, do a Search & replace (Ctrl + H). Set the searchterm to jos_ and change it into your new prefix (Example: fdasqw_). Press "Replace all".
   * Select everything in your notepad file and copy it. In phpMyAdmin, go to SQL, paste the queries and press Start.

2. Remove version number / name of extensions

Most vulnerabilities only occur in a specific release of a specific extension. Showing MyExtension version 2.14 is a really bad thing. You can modify this message to only the name of the extension by doing the following:

    * Retrieve all files of the extension from your server.
    * Open up Dreamweaver.
    * Load any file from the extension that you just downloaded to your local machine.
    * Use the Search function and set the search to Search through specified folder. Navigate to the folder where you downloaded the exploit to.
    * Set the search term to "MyExtension version 2.14" and press OK.
    * When found the correct file, remove the version number.
    * Upload the changed file to your server and check if the changes are made.

3. Use a SEF component

Most hackers use the Google inurl: command to search for a vulnerable exploit. Use Artio, SH404SEF or another SEF component to re-write your URL's and prevent hackers from finding the exploits.

Additionally, you'll get a higher rank in Google when using search engine friendly URL's.

4. Keep Joomla! and extensions up to date

This one is pretty obvious. Always check for the latest versions of Joomla! and the extensions you're using. Many vulnerabilities are resolved most of the times in later versions.

5. Use the correct CHMOD for each folder and file

Setting files or folders to a CHMOD of 777 or 707 is only necessary when a script needs to write to that file or directory. All other files should have the following configuration:

    PHP files: 644
    Other folders: 755

6. Delete leftover files

When you installed an extension that you didn't like, don't set the extension to unbublished. If you do, the vulnerable files will still be on your website. So simply use the un-install function to totally get rid of the extension.

7. Change your .htaccess file

Add the following lines to your .htaccess file to block out some common exploits.

Open your .htaccess file
########## Begin - Rewrite rules to block out some common exploits
#
# Block out any script trying to set a mosConfig value through the URL
RewriteCond %{QUERY_STRING} mosConfig_[a-zA-Z_]{1,21}(=|%3D) [OR]
# Block out any script trying to base64_encode crap to send via URL
RewriteCond %{QUERY_STRING} base64_encode.*(.*) [OR]
# Block out any script that includes a < script> tag in URL
RewriteCond %{QUERY_STRING} (<|%3C).*script.*(>|%3E) [NC,OR]
# Block out any script trying to set a PHP GLOBALS variable via URL
RewriteCond %{QUERY_STRING} GLOBALS(=|[|%[0-9A-Z]{0,2}) [OR]
# Block out any script trying to modify a _REQUEST variable via URL
RewriteCond %{QUERY_STRING} _REQUEST(=|[|%[0-9A-Z]{0,2}) [OR]
# Block out any script that tries to set CONFIG_EXT (com_extcal2 issue)
RewriteCond %{QUERY_STRING} CONFIG_EXT([|%20|%5B).*= [NC,OR]
# Block out any script that tries to set sbp or sb_authorname via URL (simpleboard)
RewriteCond %{QUERY_STRING} sbp(=|%20|%3D) [OR]
RewriteCond %{QUERY_STRING} sb_authorname(=|%20|%3D)
# Send all blocked request to homepage with 403 Forbidden error!
RewriteRule ^(.*)$ index.php [F,L]
#
########## End - Rewrite rules to block out some common exploits