45.134.225.36

nginx 1.18.0

http://45.134.225.36/

Status

200  OK

Body Hash

sha1:e40606373151d67324d2904ad971fff800fcfcb6

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.

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.

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:[email protected]). 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.
    

linux

Handshake

Version Selected

TLSv1_3

Cipher Selected

TLS_AES_256_GCM_SHA384

Certificate

Fingerprint

981b0c7eeefb9fbda8924e0a7c3afb491cb802bbd082379a0710a095b2c03c26

Subject

CN=www.e4zj63drxokpza.net

Issuer

CN=www.xotmyhdekcq4ni7z.com

Names

www.e4zj63drxokpza.net

Fingerprint

JARM

2ad2ad16d2ad2ad00042d42d000000332dc9cd7d90589195193c8bb05d84fa

JA3S

15af977ce25de452b96affa2addb1036

linux

Handshake

Version Selected

TLSv1_3

Cipher Selected

TLS_AES_256_GCM_SHA384

Certificate

Fingerprint

5d1e79bce8b2911bb569f6e1ea702ec095b18614374571156fdc25a793fad95f

Subject

CN=www.n3hyezmjx4rc6ikxudpd.net

Issuer

CN=www.tfostdm3aztrbmwymhah.com

Names

www.n3hyezmjx4rc6ikxudpd.net

Fingerprint

JARM

2ad2ad16d2ad2ad00042d42d000000332dc9cd7d90589195193c8bb05d84fa

JA3S

15af977ce25de452b96affa2addb1036

linux

Handshake

Version Selected

TLSv1_3

Cipher Selected

TLS_AES_256_GCM_SHA384

Certificate

Fingerprint

393b7d0b773b1753773143c55dda89825b60bdaa35a70fdcba54a6e9fa6dffc2

Subject

CN=www.6acrbu5id4kgstypowic.net

Issuer

CN=www.im5wkob3fdeuzvsaxj.com

Names

www.6acrbu5id4kgstypowic.net

Fingerprint

JARM

2ad2ad16d2ad2ad00042d42d000000332dc9cd7d90589195193c8bb05d84fa

JA3S

15af977ce25de452b96affa2addb1036

linux

Handshake

Version Selected

TLSv1_3

Cipher Selected

TLS_AES_256_GCM_SHA384

Certificate

Fingerprint

3a1be30f150e26f65bea91dd2559cb41ee45a5457681f60e6efd8613000040fb

Subject

CN=www.mqn5m76rm4ylc.net

Issuer

CN=www.o3yo7pe3eau7ylnzfx7.com

Names

www.mqn5m76rm4ylc.net

Fingerprint

JARM

2ad2ad16d2ad2ad00042d42d000000332dc9cd7d90589195193c8bb05d84fa

JA3S

15af977ce25de452b96affa2addb1036

nginx 1.18.0

http://45.134.225.36:9035/

Status

401  Unauthorized

Body Hash

sha1:1a6b2b7fa1b0c887c0d17755de73737b48e76d19

HTML Title

401 Authorization Required

Response Body

Expand

      # 401 Authorization Required

* * *

nginx/1.18.0 (Ubuntu)
    

nginx 1.18.0

http://45.134.225.36:9036/

Status

401  Unauthorized

Body Hash

sha1:1a6b2b7fa1b0c887c0d17755de73737b48e76d19

HTML Title

401 Authorization Required

Response Body

Expand

      # 401 Authorization Required

* * *

nginx/1.18.0 (Ubuntu)
    

nginx 1.18.0

http://45.134.225.36:9037/

Status

401  Unauthorized

Body Hash

sha1:1a6b2b7fa1b0c887c0d17755de73737b48e76d19

HTML Title

401 Authorization Required

Response Body

Expand

      # 401 Authorization Required

* * *

nginx/1.18.0 (Ubuntu)
    

nginx 1.18.0

http://45.134.225.36:9038/

Status

401  Unauthorized

Body Hash

sha1:1a6b2b7fa1b0c887c0d17755de73737b48e76d19

HTML Title

401 Authorization Required

Response Body

Expand

      # 401 Authorization Required

* * *

nginx/1.18.0 (Ubuntu)
    

nginx 1.18.0

http://45.134.225.36:9039/

Status

401  Unauthorized

Body Hash

sha1:1a6b2b7fa1b0c887c0d17755de73737b48e76d19

HTML Title

401 Authorization Required

Response Body

Expand

      # 401 Authorization Required

* * *

nginx/1.18.0 (Ubuntu)
    

nginx 1.18.0

http://45.134.225.36:9040/

Status

401  Unauthorized

Body Hash

sha1:1a6b2b7fa1b0c887c0d17755de73737b48e76d19

HTML Title

401 Authorization Required

Response Body

Expand

      # 401 Authorization Required

* * *

nginx/1.18.0 (Ubuntu)
    

nginx 1.18.0

http://45.134.225.36:9041/

Status

401  Unauthorized

Body Hash

sha1:1a6b2b7fa1b0c887c0d17755de73737b48e76d19

HTML Title

401 Authorization Required

Response Body

Expand

      # 401 Authorization Required

* * *

nginx/1.18.0 (Ubuntu)
    

nginx 1.18.0

http://45.134.225.36:9042/

Status

401  Unauthorized

Body Hash

sha1:1a6b2b7fa1b0c887c0d17755de73737b48e76d19

HTML Title

401 Authorization Required

Response Body

Expand

      # 401 Authorization Required

* * *

nginx/1.18.0 (Ubuntu)
    

nginx 1.18.0

http://45.134.225.36:9100/

Status

401  Unauthorized

Body Hash

sha1:1a6b2b7fa1b0c887c0d17755de73737b48e76d19

HTML Title

401 Authorization Required

Response Body

Expand

      # 401 Authorization Required

* * *

nginx/1.18.0 (Ubuntu)
    

nginx 1.18.0

http://45.134.225.36:9167/

Status

401  Unauthorized

Body Hash

sha1:1a6b2b7fa1b0c887c0d17755de73737b48e76d19

HTML Title

401 Authorization Required

Response Body

Expand

      # 401 Authorization Required

* * *

nginx/1.18.0 (Ubuntu)
    

linux

Handshake

Version Selected

TLSv1_3

Cipher Selected

TLS_AES_256_GCM_SHA384

Certificate

Fingerprint

81fa05ef4d01b6125aef1dc5b56d19d237a11f52776328a821ef7eae19b7daf7

Subject

CN=www.i6kfw7d7eowfkav.net

Issuer

CN=www.rikfk6bg7npxhwspif.com

Names

www.i6kfw7d7eowfkav.net

Fingerprint

JARM

2ad2ad16d2ad2ad00042d42d000000332dc9cd7d90589195193c8bb05d84fa

JA3S

15af977ce25de452b96affa2addb1036

linux

Handshake

Version Selected

TLSv1_3

Cipher Selected

TLS_AES_256_GCM_SHA384

Certificate

Fingerprint

da404240cc81d5cdf7606fd9a63a1fe43caeb716f27fada0b516f60724f1fa98

Subject

CN=www.oe2ltbhdgzdvk.net

Issuer

CN=www.lde4ilxzhd.com

Names

www.oe2ltbhdgzdvk.net

Fingerprint

JARM

2ad2ad16d2ad2ad00042d42d000000332dc9cd7d90589195193c8bb05d84fa

JA3S

15af977ce25de452b96affa2addb1036

linux

Handshake

Version Selected

TLSv1_3

Cipher Selected

TLS_AES_256_GCM_SHA384

Certificate

Fingerprint

0fc443ad1fb149dc7cb2a7760db8319792fbe4eeb16774ec578a15d41eb7ca33

Subject

CN=www.wic7bmwothzxpds.net

Issuer

CN=www.ysd3ob7cal5r4.com

Names

www.wic7bmwothzxpds.net

Fingerprint

JARM

2ad2ad16d2ad2ad00042d42d000000332dc9cd7d90589195193c8bb05d84fa

JA3S

15af977ce25de452b96affa2addb1036

linux

Handshake

Version Selected

TLSv1_3

Cipher Selected

TLS_AES_256_GCM_SHA384

Certificate

Fingerprint

adf6fbb6a0f35b35e181af2956fc4bfc0f93ee0e8ebe90dfe934d8c03f3010a1

Subject

CN=www.iwhk6d4edjdsx.net

Issuer

CN=www.gpxyuiwtsuqb7js7xgr.com

Names

www.iwhk6d4edjdsx.net

Fingerprint

JARM

2ad2ad16d2ad2ad00042d42d000000332dc9cd7d90589195193c8bb05d84fa

JA3S

15af977ce25de452b96affa2addb1036