Delivery-Date: Mon, 27 Jul 2015 15:13:44 -0400
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_RP_MATCHES_RCVD,UNPARSEABLE_RELAY
	autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 2896C1E0B25;
	Mon, 27 Jul 2015 15:13:43 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 4EE623641E;
	Mon, 27 Jul 2015 19:13:37 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id DBE093638E
 for <tor-talk@lists.torproject.org>; Mon, 27 Jul 2015 19:13:33 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id uO3OG0y-KS0g for <tor-talk@lists.torproject.org>;
 Mon, 27 Jul 2015 19:13:33 +0000 (UTC)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id B1A5F3635A
 for <tor-talk@lists.torproject.org>; Mon, 27 Jul 2015 19:13:33 +0000 (UTC)
Received: from piha.riseup.net (unknown [10.0.1.162])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK))
 by mx1.riseup.net (Postfix) with ESMTPS id 23D3541362
 for <tor-talk@lists.torproject.org>; Mon, 27 Jul 2015 19:13:31 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1438024411; bh=+nz0t4LXiA1Vy2skJ/PUKr19lDOHulmahYKIdx6W2i4=;
 h=Subject:To:References:From:Date:In-Reply-To:From;
 b=OyBKi2FvN4tzE31oHaqlWuA2oM0gOekgGrkX7x+2EtxyXUs4A7ozmJ3mt7axgoAAm
 GyJX4wj/aieC3iT+VRqv2/j/tSxcokQ5qu1mdwOZe0Jee4s85oAnT9DWPvMk3+Rqyr
 Q+dliyPHoa+RPvEBDr+1+qE+T8fqUFZX42Ifw7Tk=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: when2plus2is5) with ESMTPSA id 43FE614182A
To: tor-talk@lists.torproject.org
References: <CA+9D9DHi3aXsXtwNWobpRKu1gNo3F3LAv+1asT6_kn2t0TC2xQ@mail.gmail.com>
 <2025598331.3201281.1438023299784.JavaMail.yahoo@mail.yahoo.com>
From: Speak Freely <when2plus2is5@riseup.net>
X-Enigmail-Draft-Status: N1110
Message-ID: <55B682D7.3090306@riseup.net>
Date: Mon, 27 Jul 2015 19:13:27 +0000
MIME-Version: 1.0
In-Reply-To: <2025598331.3201281.1438023299784.JavaMail.yahoo@mail.yahoo.com>
X-Virus-Scanned: clamav-milter 0.98.7 at mx1
X-Virus-Status: Clean
Subject: Re: [tor-talk] comicskingdom.com inaccessible by Tor?
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

They are most likely using one of 3 options to block Tor.

1) They use Tor-provided lists of Tor exit relays
2) They use publicly available block lists
3) They rolled their own block list generator

The point is, this information is publicly available.

So, the question isn't how they did it, but why they did it.

The answer is whatever reason they chose.

Your best option is to attempt to contact them directly and ask.


Matt
Speak Freely
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

