full-disclosure - So how does THIS work? Solved.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20050921212952.311ed009@homebox.slave-tothe-box.net>
Date: Thu Sep 22 04:28:12 2005
From: jlay at slave-tothe-box.net (James Lay)
Subject: So how does THIS work? Solved.

Thanks for the great feedback people!

James

On Wed, 21 Sep 2005 20:58:19 -0600
James Lay <jlay@...ve-tothe-box.net> wrote:

> So ok...I'm scopin out my apache logs, when I see this:
> 
> 204.251.10.95 - - [21/Sep/2005:17:02:56 -0600] "GET
> http://domaincrunch.pozzer.com/ph/index.php HTTP/1.1" 400 353
> 
> Now....that domain name and host aren't even REMOTELY close to my
> domain, host, or even IP address.  So how did this get routed to me?
> Or is it something entirely different?
> 
> James
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.grok.org.uk/full-disclosure-charter.html
> Hosted and sponsored by Secunia - http://secunia.com/