<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>ThisWebHost - The Official Blog &#187; tips</title>
	<atom:link href="http://www.thiswebhost.com/blog/category/tips/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.thiswebhost.com/blog</link>
	<description>Keep up to date with ThisWebHost</description>
	<lastBuildDate>Wed, 04 Jan 2012 13:40:58 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Be Wary of Host Rating Sites</title>
		<link>http://www.thiswebhost.com/blog/2009/05/28/be-wary-of-host-rating-sites/</link>
		<comments>http://www.thiswebhost.com/blog/2009/05/28/be-wary-of-host-rating-sites/#comments</comments>
		<pubDate>Thu, 28 May 2009 14:29:37 +0000</pubDate>
		<dc:creator>Doug</dc:creator>
				<category><![CDATA[guides]]></category>
		<category><![CDATA[tips]]></category>

		<guid isPermaLink="false">http://www.thiswebhost.com/blog/?p=53</guid>
		<description><![CDATA[I don&#8217;t know about you, but when I look into purchasing a product or service, my first point of call is usually a quick google search. Terms such as: &#8220;&#60;product name&#62; review&#8221; or &#8220;&#60;product name&#62; sucks&#8221; will pretty soon let you know if your decision is going to be a potentially bad one. The great [...]]]></description>
			<content:encoded><![CDATA[<p>I don&#8217;t know about you, but when I look into purchasing a product or service, my first point of call is usually a quick google search. Terms such as: &#8220;&lt;product name&gt; review&#8221; or &#8220;&lt;product name&gt; sucks&#8221; will pretty soon let you know if your decision is going to be a potentially bad one. The great part about looking for information this way is that you&#8217;re less likely to come across biased (particularly financially) results that may give you the wrong impression.</p>
<p>It&#8217;s a sad fact that most, if not all host rating websites, are based on not how good a host is &#8211; but how much money the hosts pay to appear in their lists. That&#8217;s right. Hosts pay to have their names appear in the top 10 list. The number 1 spot? That&#8217;s right, like an eBay auction it goes to the highest bidder.</p>
<p>Please be wary of these so-called &#8220;host rating&#8221; websites. The best way to obtain an accurate representation of a hosting service is to utilise social methods. Take a look on Twitter, see what people are saying. Look on various forums, particularly <a title="WebHostingTalk" href="http://www.webhostingtalk.com">www.webhostingtalk.com</a> and discover what REAL people are saying about these services.</p>
<p>Good luck in your search.</p>
<div class="tweetthis" style="text-align:left;"><p> <a class="tt" href="http://twitter.com/intent/tweet?text=Be+Wary+of+Host+Rating+Sites+http%3A%2F%2Fthiswebhost.com%2Fblog%2F%3Fp%3D53+%40thiswebhost" title="Post to Twitter"><img class="nothumb" src="http://www.thiswebhost.com/blog/wp-content/plugins/tweet-this/icons/en/twitter/tt-twitter.png" alt="Post to Twitter" /></a> <a class="tt" href="http://twitter.com/intent/tweet?text=Be+Wary+of+Host+Rating+Sites+http%3A%2F%2Fthiswebhost.com%2Fblog%2F%3Fp%3D53+%40thiswebhost" title="Post to Twitter">Tweet This Post</a></p></div>]]></content:encoded>
			<wfw:commentRss>http://www.thiswebhost.com/blog/2009/05/28/be-wary-of-host-rating-sites/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Quick WordPress/Forum Admin Security Tip</title>
		<link>http://www.thiswebhost.com/blog/2009/05/13/quick-wordpressforum-admin-security-tip/</link>
		<comments>http://www.thiswebhost.com/blog/2009/05/13/quick-wordpressforum-admin-security-tip/#comments</comments>
		<pubDate>Thu, 14 May 2009 00:54:33 +0000</pubDate>
		<dc:creator>Doug</dc:creator>
				<category><![CDATA[tips]]></category>
		<category><![CDATA[admin]]></category>
		<category><![CDATA[wordpress]]></category>

		<guid isPermaLink="false">http://www.thiswebhost.com/blog/?p=49</guid>
		<description><![CDATA[WordPress, vBulletin, PHPBB, &#60;insert name of your favourite PHP script with admin backend here&#62;. All very fantastic scripts that work to make our websites even more awesome. It&#8217;s no surprise that with scripts this popular, security vulnerabilities are found from time to time. Whilst these are often not that serious, what can we do to [...]]]></description>
			<content:encoded><![CDATA[<p>WordPress, vBulletin, PHPBB, &lt;insert name of your favourite PHP script with admin backend here&gt;. All very fantastic scripts that work to make our websites even more awesome. It&#8217;s no surprise that with scripts this popular, security vulnerabilities are found from time to time. Whilst these are often not that serious, what can we do to make these even more secure?</p>
<p>One method we often try and implement around our own sites, and suggest to clients, is that they lock down the administration backends of their scripts via IP address. Now, this isn&#8217;t an ideal solution if you have a dynamic IP address or want to access things on the move, but it can certainly dramatically reduce the &#8220;hack&#8221; attempts on your websites, even if someone manages to obtain your password!</p>
<p>To explain what we mean, imagine a clean installation of wordpress. Most people know that to access the wordpress admin panel you simply add /wp-admin/ to the end of the URL, right? To add an additional layer of security, we can create a very simple .htaccess file in this wp-admin folder, denying all accesses but to a single IP address:</p>
<p><code><br />
Deny from all # Deny access to everyone<br />
Allow from 127.0.0.1 # Allow our IP address<br />
ErrorDocument 403 http://www.google.com # Redirect<br />
</code></p>
<p>Simply broken down, this .htaccess file will deny everyone access to the wp-admin folder except for the IP address(es) listed in the &#8220;Allow from&#8221; lines. Anyone not in that list will be redirected to the URL From within the &#8220;ErrorDocument 403&#8243; line. As you can probably guess, even if they have a valid username and password, it won&#8217;t make any difference. If their IP address isn&#8217;t in the file, they aren&#8217;t getting in! </p>
<p>To use this you would naturally replace &#8220;127.0.0.1&#8243; with your IP address. Not sure what your IP address is? Find out <a href="http://www.whatismyip.com">here</a>. Want to add multiple IP addresses? Just add multiple &#8220;Allow from&#8221; lines, one after the other.</p>
<p>A very quick and &#8220;dirty&#8221; tip, but one that can often be very useful for those with static IP addresses.</p>
<div class="tweetthis" style="text-align:left;"><p> <a class="tt" href="http://twitter.com/intent/tweet?text=Quick+WordPress%2FForum+Admin+Security+Tip+http%3A%2F%2Fthiswebhost.com%2Fblog%2F%3Fp%3D49+%40thiswebhost" title="Post to Twitter"><img class="nothumb" src="http://www.thiswebhost.com/blog/wp-content/plugins/tweet-this/icons/en/twitter/tt-twitter.png" alt="Post to Twitter" /></a> <a class="tt" href="http://twitter.com/intent/tweet?text=Quick+WordPress%2FForum+Admin+Security+Tip+http%3A%2F%2Fthiswebhost.com%2Fblog%2F%3Fp%3D49+%40thiswebhost" title="Post to Twitter">Tweet This Post</a></p></div>]]></content:encoded>
			<wfw:commentRss>http://www.thiswebhost.com/blog/2009/05/13/quick-wordpressforum-admin-security-tip/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>

