104.244.74.159

http://104.244.74.159/

Status

200  OK

Body Hash

sha1:5d32794f97cc7c14cd865d054ce43789f7f77f47

HTML Title

This is a Tor Exit Router

Response Body

Expand

      # This is a Tor Exit Router

You are most likely accessing this website because you've had some issue with
the traffic coming from this IP. This router is part of the [Tor Anonymity
Network](https://www.torproject.org/), which is dedicated to [providing
privacy](https://2019.www.torproject.org/about/overview) to people who need it
most: average computer users. This router IP should be generating no other
traffic, unless it has been compromised.

Tor works by running user traffic through a random chain of encrypted servers,
and then letting the traffic exit the Tor network through an exit node like
this one. This design makes it very hard for a service to know which user is
connecting to it, since it can only see the IP-address of the Tor exit node:

Illustration showing how a user might connect to a service through the Tor
network. The user first sends their data through three daisy-chained encrypted
Tor servers that exist on three different continents. Then the last Tor server
in the chain connects to the target service over the normal internet. The user
This server Your service Tor encrypted link Unencrypted link

[Read more about how Tor
works.](https://2019.www.torproject.org/about/overview)

Tor sees use by [many important segments of the
population](https://2019.www.torproject.org/about/torusers), including whistle
blowers, journalists, Chinese dissidents skirting the Great Firewall and
oppressive censorship, abuse victims, stalker targets, the US military, and
law enforcement, just to name a few. While Tor is not designed for malicious
computer users, it is true that they can use the network for malicious ends.
In reality however, the actual amount of
[abuse](https://support.torproject.org/abuse/) is quite low. This is largely
because criminals and hackers have significantly better access to privacy and
anonymity than do the regular users whom they prey upon. Criminals can and do
[build, sell, and
trade](https://web.archive.org/web/20200131013910/http://voices.washingtonpost.com/securityfix/2008/08/web_fraud_20_tools.html)
far larger and [more powerful
networks](https://web.archive.org/web/20200131013908/http://voices.washingtonpost.com/securityfix/2008/08/web_fraud_20_distributing_your.html)
than Tor on a daily basis. Thus, in the mind of this operator, the social need
for easily accessible censorship-resistant private, anonymous communication
trumps the risk of unskilled bad actors, who are almost always more easily
uncovered by traditional police work than by extensive monitoring and
surveillance anyway.

In terms of applicable law, the best way to understand Tor is to consider it a
network of routers operating as common carriers, much like the Internet
backbone. However, unlike the Internet backbone routers, Tor routers
explicitly do not contain identifiable routing information about the source of
a packet, and no single Tor node can determine both the origin and destination
of a given transmission.

As such, there is little the operator of this router can do to help you track
the connection further. This router maintains no logs of any of the Tor
traffic, so there is little that can be done to trace either legitimate or
illegitimate traffic (or to filter one from the other). Attempts to seize this
router will accomplish nothing.

Furthermore, this machine also serves as a carrier of email, which means that
its contents are further protected under the ECPA. [18 USC
2707](https://www.law.cornell.edu/uscode/text/18/2707) explicitly allows for
civil remedies ($1000/account _plus_ legal fees) in the event of a seizure
executed without good faith or probable cause (it should be clear at this
point that traffic with an originating IP address of FIXME_DNS_NAME should not
constitute probable cause to seize the machine). Similar considerations exist
for 1st amendment content on this machine.

If you are a representative of a company who feels that this router is being
used to violate the DMCA, please be aware that this machine does not host or
contain any illegal content. Also be aware that network infrastructure
maintainers are not liable for the type of content that passes over their
equipment, in accordance with [DMCA "safe harbor"
provisions](https://www.law.cornell.edu/uscode/text/17/512). In other words,
you will have just as much luck sending a takedown notice to the Internet
backbone providers. Please consult [EFF's prepared
response](https://community.torproject.org/relay/community-resources/eff-tor-
legal-faq/tor-dmca-response/) for more information on this matter.

For more information, please consult the following documentation:

[Tor Overview](https://2019.www.torproject.org/about/overview) [Tor Abuse
FAQ](https://support.torproject.org/abuse/) [Tor Legal
FAQ](https://community.torproject.org/relay/community-resources/eff-tor-legal-
faq/)

That being said, if you still have a complaint about the router, you may email
the [maintainer](mailto:FIXME_YOUR_EMAIL_ADDRESS). If complaints are related
to a particular service that is being abused, I will consider removing that
service from my exit policy, which would prevent my router from allowing that
traffic to exit through it. I can only do this on an IP+destination port
basis, however. Common P2P ports are already blocked.

You also have the option of blocking this IP address and others on the Tor
network if you so desire. The Tor project provides a [web
service](https://check.torproject.org/torbulkexitlist) to fetch a list of all
IP addresses of Tor exit nodes that allow exiting to a specified IP:port
combination, and an official [DNSRBL](https://dist.torproject.org/tordnsel/)
is also available to determine if a given IP address is actually a Tor exit
server. Please be considerate when using these options. It would be
unfortunate to deny all Tor users access to your site indefinitely simply
because of a few bad apples.
    

Handshake

Version Selected

TLSv1_3

Cipher Selected

TLS_AES_256_GCM_SHA384

Certificate

Fingerprint

6697b4d4ebb76b126b525df15cfe3d880494ab9c36f5c4634cebc51c79e8ce25

Subject

CN=www.2bffzzovr2t2.net

Issuer

CN=www.r3whtsgu4uhg6np5pq.com

Names

www.2bffzzovr2t2.net

Fingerprint

JARM

2ad2ad16d2ad2ad00042d42d000000332dc9cd7d90589195193c8bb05d84fa

JA3S

15af977ce25de452b96affa2addb1036

nginx 1.18.0

http://104.244.74.159:8080/

Status

404  Not Found

Body Hash

sha1:e461d072a6ba8f0082d6f187eba7f053343529c6

HTML Title

404 Not Found

Response Body

Expand

      # 404 Not Found

* * *

nginx/1.18.0
    

nginx 1.18.0

http://104.244.74.159:8081/

Status

400  Bad Request

Body Hash

sha1:f57c75a285c5d29c0237b0b287478584a86c91da

HTML Title

400 The plain HTTP request was sent to HTTPS port

Response Body

Expand

      # 400 Bad Request

The plain HTTP request was sent to HTTPS port

* * *

nginx/1.18.0
    

nginx 1.18.0

http://104.244.74.159:8716/

Status

404  Not Found

Body Hash

sha1:e461d072a6ba8f0082d6f187eba7f053343529c6

HTML Title

404 Not Found

Response Body

Expand

      # 404 Not Found

* * *

nginx/1.18.0