The following scripts have all been updated…

Crafty Syntax: v2.16.3
Drupal: v6.14
Elgg: v1.6.1
MediaWiki: v1.15.1
Nucleus: v3.51
Osticket: v1.6RC5
PHPcoin: v1.6.5
Roundcube: v0.3.1
Typo3: v4.3.0
Wordpress: v2.8.6

This now completes our latest updates and all scripts provided via the Hosting control panel are on the latest versions!

• 50 FREE POP3/IMAP Email Accounts
• Bpeinternet 2GB Webmail
• Web Forwarding (multiple types)
• Unlimited Email Forwarding
• Catch-All Email Forwarding
• Domain “For Sale” Page
• Change Name Servers
• Change Domain Contact Information

• No Fee For Changing Nominet Tag
• Full DNS Management
• Nominet Whois Opt Out
• Manage Everything Online Easily
• No Hidden Fees
• Upgrade to Web Hosting Instantly
• 24 x 7 x 365 Technical Support

This is a fantastic new feature from Bpeinternet. Click here to order today…

Even if you require just a personal web page or something quite small or if you happen to require a site more suitable for a business, then you’ll need to contact a specialist company who provide web hosting as one of their services to make sure you get the best deal and best service possible. Heart Internet are experts at providing web hosting facilities. We provide a range of services that allow you to fully manage and maintain your website.

Most web hosting companies will provide basic features such as FTP for uploading files. However, this is where the services offered by some companies stops. We provide advanced database support and application development platforms such as Ruby and Rails. Features like these allow our customers to write and install scripts for applications on their website. We also provide out customers with an advanced control panel. This control panel has loads of features that allow you to manage your email, setup databases, manage servers, view bandwidth statistics and much more.

Nothing
The first thing you do is absolutely nothing. Sit back, chillax and wait. The search engines are constantly fiddling with their algorithms and the weighting of ranking factors which affect how websites are ranked in the results. Sometimes a change can occur that doesn’t have the desired effect they wanted and penalises sites that were previously well ranked. When this occurs (and they notice it) the changes may be rolled back or amended and you can find your site jumps back to its previous positions over night. Give it a couple of weeks or so before you start making any changes.

SEO audit: Is your site fully optimized?
Do an audit of your on-site SEO to make sure you have covered all the areas you can optimize. Your website doesn’t exist within a vacuum and there are thousands of websites working to grab your position and who are squeezing every bit of juice out of their website to do it. Make sure you are using your target keyword(s) across these areas: title tag, H tags, image alt tag, image file name, internal link anchor text, internal link alt tag, site map, first paragraph of copy and page URLs.

Roll back any ‘black hat’ tactics you have undertaken
You can click here to read Google’s guidelines for webmasters which spell out what Google expects from a website as well as what not to do. If you have recently undertaken any of the following practices you may have been slapped by Google!

» Bought links
» Used hidden text or hidden links
» Introduced cloaking or underhand redirects
» Created pages with irrelevant keywords
» Added multiple pages, sub-domains, or domains with substantially duplicate content
» Set up a “doorway” page created just for search engines
Not necessarily ‘black hat’ but if a larger proportion of your website is now allocated to advertising space rather than original copy Google is going to take a dislike to you…”If your site participates in an affiliate program, make sure that your site adds value. Provide unique and relevant content that gives users a reason to visit your site first”

Update content more regularly
Google likes fresh content and sites that are updated regularly. If you haven’t made any changes for a long time go back and review your web copy or investigate ways you can introduce regular content to your site e.g. articles, news, a blog etc.

Build up alternative sources of traffic
Because of Google’s dominance in search and putting your eggs all in one basket can almost become unavoidable, but direct traffic is still a source! Once they arrive to you from a search engine do everything you can to turn them in to a repeat visitor. As well as increasing repeat visitors percentages build a following on social media sites e.g. Twitter, Facebook et al as well as within your websites community e.g. forums, blogs et al.

What is SSL?
Secure Sockets Layer (SSL) provides two different services: encryption (preventing the traffic from being read in transit) and authentication (verifying that the site is who they claim to be). Although the term most commonly associated with SSL (“certificate”) refers only to authentication, people often see that as being synonymous with encryption instead. I’m going to explain why (and summarise how) it does both.

Why do we need them?
First, imagine the scenarios which SSL is intended to protect against. Let’s say there’s a user, Alice, who wants to buy a wig from Bob’s wig store. The most obvious risk is if an attacker, Eve, can somehow directly receive the traffic, e.g. through a poorly secured wifi access point. I’m going to call that scenario 1. The other (less common) risk is if Alice’s connection to Bob runs though one of Eve’s computers (because she controls one of the routers involved, or has provided false DNS records to Alice, for example), allowing Eve to alter the content arbitrarily. That’s scenario 2.

In scenario 1, the risk is that when Alice sends Bob her credit card details to buy a wig, Eve will note them down and use them to steal money. That’s bad for Alice, and even for Bob (who will probably be blamed). In scenario 2, Eve can still steal the card number, but she can also perform a more subtle attack, for example changing Alice’s request to deliver to Eve’s address and sending Alice back a page which says that the transaction failed. In that case, Alice and Bob will have every reason to blame each other.

So, the first thing to do is to stop Eve getting the card number – and that means encryption. Encrypted data is roughly analogous to a series of combination-locked boxes, of which Alice and Bob somehow both know the combination (and nobody else does). Alice can send boxes to Bob (and vice versa), while Eve can do nothing without knowing the combination. That would perfectly solve the problem, except that Alice and Bob still need a way to agree on a combination to use.

Since Alice and Bob don’t already have a mutually-known combination to use at the start, they have to use a slightly different approach called public key encryption. The basic idea is that there is a way for anyone to encrypt data that only Bob can decrypt. In the “boxes” metaphor, this would be latch-lock boxes that Bob gives to everyone he sees: you don’t need to know the combination to lock it, only to unlock it. That’s absolutely perfect for scenario 1: Bob sends Alice a latch-lock box; Alice sends it back with a suggested combination written on a piece of paper inside. This is roughly the security level you get with a self-signed certificate.

Unfortunately, scenario 2 is still a problem: Alice gets Eve’s latch-lock box, and Bob gets Eve’s suggested combination, making it no more secure than if no encryption has been used at all. This is where authentication comes in: Alice and Bob need to know they’re talking directly to each other.

For this, Bob makes a CSR (metaphorically a label saying “this is Bob’s lockbox”, firmly attached to each lockbox), and he gets someone they both trust, Charlie, to sign it (making a complete certificate). When Alice receives the lockbox, she knows that it’s Bob’s (or isn’t) based on whether Charlie has signed it as being so; Bob still doesn’t know he’s talking to Alice, but since Eve never knows Alice’s suggested combination, Alice will know that something is wrong when she doesn’t get a lockbox back which she can open with her combination. So, finally, Alice and Bob can be assured that they’re communicating in secret.

In terms of the practical implementation, Alice has already got knowledge of the Certification Authority (Charlie) because it came on her computer when she bought it, and what the certificate says is that the public key it contains is genuinely from the web site address that appears in her address bar.

Mixed Content Warnings
If you’ve built an SSL site before, you will probably have encountered this. If the browser loads some content over SSL, but loads some content unencrypted, it no longer knows whether all the content that the user perceives as secure actually is, and so issues a hard-to-ignore warning – this even extends to things like CSS (which can hide some text and add some of its own), so be sure that you don’t use full URLs for src= and href= if you’re running a site that you want to work on both HTTP and HTTPS.