NPT 0.0 beta

Coming from ThePlanet addys

[bcolflesh]

Typically in the form:

Mozilla/3.01 (compatible; NPT 0.0 beta)

Anyone have any info about this?

[uncle_bob]

Just seems to be gathering robot.txt and index pages, not scurrying about the site. I'm never keen on robots or spiders that don't have a url in their user-agent - especially beta ones.

[wilderness]

I had some unidentified crawling from the planet some time back.

This recent change in the UA appeaered as well however I had them denied from the previously crawling.

NPT?
Name Protect?

[Matt Probert]

We have had serious trouble with this bot sending large volumes of fake search requests (collections of apparently random words) to our search script - thereby overloading the server. We have contacted the abuse department at ThePlanet.com, and sent them relavant log file entries, but still no joy. Does anyone know who runs this bot?

Matt

[wilderness]

Matt,
As is our tradition, Welcome to Webmaster World.

If the UA "Mozilla/3.01 (compatible; NPT 0.0 beta)"
is in fact Nameprotect dot com?
It wouldn't surprise anybody here. They don't have a very reputable compliance as related to webmasters.

I have "Mozilla/3.01 (compatible; NPT 0.0 beta)" serving higher than average activity (during July) in my logs and eating 403's as a result of a denial in my htaccess. The access was from both a ThePlanet and another co-location server. (sticky mail me if you desire the second IP.)

I have no idea if the UA's are shown in your DOS attacks and/or search scripts?
If the UA is shown?
It's a simple procedure to deny access as I previously advised you in alt.www.webamster to review this thread;
A simple beginning
[webmasterworld.com...]

If you add the following lines into your htaccess file of your root folder than it will apply to all folders below that. Should you desire an individual htaccess for an individual folder that is a acceptable use as well. [please note exception below]

Options -Indexes
<Limit GET>
SetEnvIf User-Agent NPT keep_out
order allow,deny
deny from 12.148.196.
deny from 12.148.209.
allow from all
deny from env=keep_out
</Limit>
RewriteEngine on
RewriteCond %{REMOTE_ADDR} ^12\.175\.0\.(3[2-9]¦4[0-7])$ [OR]
RewriteCond %{REMOTE_ADDR} ^64\.251\.([0-9]¦[12][0-9]¦3[01])\. [OR]
RewriteCond %{REMOTE_ADDR}^69\.56\.(12[8-9]¦1[3-9][0-9]¦2[0-4][0-9]¦25[0-5])\. [OR]
RewriteRule .*$ - [F]

Exceptions:
1)this fourum changes the pipe character to a broken straight line and you will need to edit those entries when copying lines.
2)In the event the 2nd-last line of data in your htacess is the "RewriteCond" I've provide above? Than you need to remove the closing "[OR]"
3) the opening two lines OPTIONS and LIMITS are set for me by my host. Others in some instances are required to use other options.

Don

edited by wilderness:
Matt, almost forgot. Name has a new service named Adtracker. http: //www.nameprotect.com/html/services/internet/snapshot.html
Is it possible that toll was either being used or crawling your site?

[wilderness]

[quote] assume you don't actually mean .htaccess, but rather the master
Apache config file? (Or in our case we have two, config and access).

Matt[\quote]

could anybody possibly explain to myself and Matt the difference in an Apache based htaccess and the files he's referring to?

Is it possible he's using an IIS server?

Thanks in advance

Don

[Matt Probert]

quote]
assume you don't actually mean .htaccess, but rather the master
Apache config file? (Or in our case we have two, config and access).
Matt
could anybody possibly explain to myself and Matt the difference in an Apache based htaccess and the files he's referring to?

Is it possible he's using an IIS server?

Thanks in advance

[\quote]

Er, I'm not sure why this has cropped up here. The quote of me was taken from Usenet, and a bit out of contect here.

.htaccess is an Apache configuration file that over rides the main Apache configuartion files (often found in /etc/httpd/conf)

In our case, we have httpd.conf which is the master Apache configuration file and a second access.conf which declares Apache global access.

Individual .htaccess files are used to override the global Apache settings, and should generally be avoided if possible - I refer one to the Apache documentation.

Suffice to say, it's better to block access in the primary Apache configuration file or files than in a .htaccess file overriding previously allowed access!

Matt

[wilderness]

[/quote]it's better to block access in the primary Apache configuration file or files than in a .htaccess file [/quote]

Only if you have access to those files Matt ;-)

Don

[wilderness]

BTW Matt,
Here's an old Webmaster World link to IIS:
[webmasterworld.com...]