<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
	>
<channel>
	<title>Comments on: How To Block Annoying Referrer Spammers?</title>
	<atom:link href="http://www.symphonious.net/2006/04/01/how-to-block-annoying-referrer-spammers/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.symphonious.net/2006/04/01/how-to-block-annoying-referrer-spammers/</link>
	<description>Living in a state of accord.</description>
	<pubDate>Wed, 07 Jan 2009 19:46:35 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Stephen Thorne</title>
		<link>http://www.symphonious.net/2006/04/01/how-to-block-annoying-referrer-spammers/comment-page-1/#comment-15362</link>
		<dc:creator>Stephen Thorne</dc:creator>
		<pubDate>Sat, 01 Apr 2006 02:16:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.symphonious.net/2006/04/01/how-to-block-annoying-referrer-spammers/#comment-15362</guid>
		<description>I don't know exactly how to handle referrer spam, but I do know how to spot a spam url.

Given any url, for example, http://hostname.example.com/foo/bar/baz.html

take hostname.example.com, and append .multi.surbl.org to it. Then do a DNS lookup on it, i.e. "hostname.example.com.multi.surbl.org". if the query comes back with an ip address, (it will be 127.0.0.XX, where XX will change according to the blacklists that list that hostname) then it is spam. Remove elements from the hostname until you're left with nothing but the root (.com, .cx, .com.au, etc, there's a list of them on surbl.org for you convenience).

As for how to make apache drop HTTP connections based on the referrer, I don't know how to do that, but it would be a fun mod_anti_spam. ;)

Heck, you could probably use the same technique to stop comment spam, if you inspect the HTTP GET/POST data as well as the Referrer: header...</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know exactly how to handle referrer spam, but I do know how to spot a spam url.</p>
<p>Given any url, for example, <a href="http://hostname.example.com/foo/bar/baz.html" rel="nofollow">http://hostname.example.com/foo/bar/baz.html</a></p>
<p>take hostname.example.com, and append .multi.surbl.org to it. Then do a DNS lookup on it, i.e. &#8220;hostname.example.com.multi.surbl.org&#8221;. if the query comes back with an ip address, (it will be 127.0.0.XX, where XX will change according to the blacklists that list that hostname) then it is spam. Remove elements from the hostname until you&#8217;re left with nothing but the root (.com, .cx, .com.au, etc, there&#8217;s a list of them on surbl.org for you convenience).</p>
<p>As for how to make apache drop HTTP connections based on the referrer, I don&#8217;t know how to do that, but it would be a fun mod_anti_spam. ;)</p>
<p>Heck, you could probably use the same technique to stop comment spam, if you inspect the HTTP GET/POST data as well as the Referrer: header&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
