[148623] in North American Network Operators' Group
Re: US DOJ victim letter
daemon@ATHENA.MIT.EDU (PC)
Thu Jan 19 16:35:00 2012
In-Reply-To: <20120119211922.GG32702@hiwaay.net>
Date: Thu, 19 Jan 2012 14:34:12 -0700
From: PC <paul4004@gmail.com>
To: Chris Adams <cmadams@hiwaay.net>, "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Knowing it's JS, I looked at the source, and here's the "rogue" ranges:
var IP_RANGES = [
[[85, 255, 112, 0], [85, 255, 127, 255]],
[[67, 210, 0, 0], [67, 210, 15, 255]],
[[93, 188, 160, 0], [93, 188, 167, 255]],
[[77, 67, 83, 0], [77, 67, 83, 255]],
[[213, 109, 64, 0], [213, 109, 79, 255]],
[[64, 28, 176, 0], [64, 28, 191, 255]]
];
On Thu, Jan 19, 2012 at 2:19 PM, Chris Adams <cmadams@hiwaay.net> wrote:
> Once upon a time, Andrew D. Dibble <adibble@quantcast.com> said:
> > FBI seems to have a list of netblocks hosting rogue DNS servers here:
> > https://forms.fbi.gov/check-to-see-if-your-computer-is-using-rogue-DNS
>
> So should I try to type in all the IPs on my network, one at a time? Oh
> wait, that page requires Javascript to check an IP; like I'm going to
> allow the FBI to run JS on my computer.
>
> --
> Chris Adams <cmadams@hiwaay.net>
> Systems and Network Administrator - HiWAAY Internet Services
> I don't speak for anybody but myself - that's enough trouble.
>
>
