Colo's

[wilderness]

Is everybody see the rash of colo's that I am.

They seem to be coming to my sites like flies on. . .

[incrediBILL]

You made me look!

Sorry, no rash, not even an itch.

However, I'm seeing a disturbing amount of reverse DNS results saying "localhost."

[wilderness]

Bill,
I manually ARIN most everything.

For some time, I've been saving my colo notations in their own directory. Not sure when I began this method and/or moved the previous colo saves to this directory.

In any event and since June 1 this year, I've 23 new colo ranges added.
That may not seem like an invasion, however considering the focus of "my widgets", I find it quite excessive (at least compared to the additions made previously.

[Ocean10000]

In Dot.Net depending how you use the DNS lookup code. When a result returns "LocalHost", dot.net will behind the scenes return the local(the computer doing the lookup) computer's hostname instead. This can be used to bypass some authentication checks which are based on weather the caller is localhost or not.

[Pfui]

@wilderness: Could you please explain? For example, what do you mean by "23 new colo ranges"? New Class As? Or 23 new somethings co-located -- somewhere? Or--? Thanks!

@Bill: FWIW, three localhost = Host hits in as many weeks have all been from Viet Nam. They've got some serious server misconfigurations going on (unintentional or otherwise...). The localhosts hit a page where I was able to snag a few additional details:

222.253.0.nnn
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14

123.16.228.nnn
Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; Trident/4.0; SLCC1; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30618)

proxy(nn)-hcm.vnn.vn
Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; GTB6; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; .NET CLR 3.0.04506)

(I now block VN by Host and all IPs. Never got a single 'legit' hit from the entire country for as long as I could remember.)

[wilderness]

@wilderness: Could you please explain? For example, what do you mean by "23 new colo ranges"? New Class As? Or 23 new somethings co-located -- somewhere? Or--? Thanks!

colo= provider whose primary business is colocation hosting.

23 new colo's= colo's that either had not crossed my doorstep previously or had done so in a fashion that allowed detection.

Class A= 012.345.678.900
012=Class A
345=Class B
678= Class C
900= Class D

I've long denied colo's and (as others may provide) it's my belief that providing their names and/or IP ranges in this forum simply provides free advertising, as a result, I make every effort not to do so

[wilderness]

Pfui,
dstiles plea with you in this thread [webmasterworld.com] was because the Class A was obscured, and thus he had no method to even get close to the identity of host/provider.

Don

[Pfui]

wilderness, thanks for the clarification about what you mean by colos. I thought so but wasn't sure. I tend to call 'em server farms.

About that other thread: As I explained in detail, the rules, plus our server-based rDNS, etc., directly affect the type and extent of the info I provide(d). As far as advertising is concerned, I did ID the Host, yes, as block-worthy. The upstream colo was ID'd by someone else.

Back on the subject of advertising: We share the same aversion to inadvertent advertising. But unless WW opts to exclude this forum from all SEs (yes, please!), every bot/crawler/spider/whatever we post about gets free advertising, via its UA, and many, many times its intra-UA site info, ditto its Host/IP/ISP -- and/or colo. (I've long had a love-hate thing about reporting new bots for precisely those reasons.)

[blend27]

-- gets free advertising --

for the lack of better expression, the ones that do make it here, usually get MOTHERFIED, and then everybody blocks them anyway... Look at Planet/Soft-L/NetDirect/OVH/NAC(in Jersey) for example; every body and their neighbors cousin's dogs vet blocks those ranges.... Try Advertising that...