45.134.225.36

As of: May 20, 2024 2:42am UTC | Latest

Basic Information

Forward DNS
fretnutty.synology.me
Routing
45.134.225.0/24  via COLOCATIONX-DATACENTER Dedicated Server Provider, GB (AS208046)
OS
linux
Services (19)
80/HTTP, 443/UNKNOWN, 444/UNKNOWN, 8443/UNKNOWN, 8444/UNKNOWN, 9035/HTTP, 9036/HTTP, 9037/HTTP, 9038/HTTP, 9039/HTTP, 9040/HTTP, 9041/HTTP, 9042/HTTP, 9100/HTTP, 9167/HTTP, 10444/UNKNOWN, 11444/UNKNOWN, 12444/UNKNOWN, 13444/UNKNOWN

HTTP 80/TCP
05/18/2024 14:14 UTC


Software

nginx 1.18.0

Details

http://45.134.225.36/
Status
200  OK
Body Hash
sha1:e40606373151d67324d2904ad971fff800fcfcb6
HTML Title
This is a Tor Exit Router
Response Body
      # 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.
    

UNKNOWN 443/TCP
05/18/2024 12:42 UTC


Software

linux

Details

TLS

Handshake
Version Selected
TLSv1_3
Cipher Selected
TLS_AES_256_GCM_SHA384
Certificate
Fingerprint
59f7a28d6be5cab9b090c55eef93f63e38191f83d5810db5a12b9c944a5b5dc6
Subject
CN=www.m2tq6nx5x5drobxc.net
Issuer
CN=www.xyjw2boivfrcym.com
Names
www.m2tq6nx5x5drobxc.net
Fingerprint
JARM
2ad2ad16d2ad2ad00042d42d000000332dc9cd7d90589195193c8bb05d84fa
JA3S
15af977ce25de452b96affa2addb1036
JA4S
t120200_544c535f4145535f3235365f47434d5f534841333834_9f090db0cf15

UNKNOWN 444/TCP
05/19/2024 16:58 UTC


Software

linux

Details

TLS

Handshake
Version Selected
TLSv1_3
Cipher Selected
TLS_AES_256_GCM_SHA384
Certificate
Fingerprint
4756e30948e5c20559c05f37b37e232f12de35040bd79d41b3274a11aab7eb09
Subject
CN=www.g6umvdaxc4577t64m.net
Issuer
CN=www.zeuvkhc757n2pcsy.com
Names
www.g6umvdaxc4577t64m.net
Fingerprint
JARM
2ad2ad16d2ad2ad00042d42d000000332dc9cd7d90589195193c8bb05d84fa
JA3S
15af977ce25de452b96affa2addb1036
JA4S
t120200_544c535f4145535f3235365f47434d5f534841333834_9f090db0cf15

UNKNOWN 8443/TCP
05/20/2024 01:39 UTC


Details

TLS

Handshake
Version Selected
TLSv1_3
Cipher Selected
TLS_AES_256_GCM_SHA384
Certificate
Fingerprint
c1234db1e0922f7c5acce6c92f03c0ec2bccf5523371cfd8e1f328cdd864028e
Subject
CN=www.7s3mfv4tzreiufmli3t.net
Issuer
CN=www.kevl63s2qy.com
Names
www.7s3mfv4tzreiufmli3t.net
Fingerprint
JARM
2ad2ad16d2ad2ad00042d42d000000332dc9cd7d90589195193c8bb05d84fa
JA3S
15af977ce25de452b96affa2addb1036
JA4S
t120200_544c535f4145535f3235365f47434d5f534841333834_9f090db0cf15

UNKNOWN 8444/TCP
05/19/2024 18:31 UTC


Software

linux

Details

TLS

Handshake
Version Selected
TLSv1_3
Cipher Selected
TLS_AES_256_GCM_SHA384
Certificate
Fingerprint
1b2c8e457c5ebae461b3011672be005a639aaea1cdf4a4a93bdd2dbb59d6b61b
Subject
CN=www.xbck5gtpkzp2hkikuz7i.net
Issuer
CN=www.j3yfmpgxf2uhfeyj.com
Names
www.xbck5gtpkzp2hkikuz7i.net
Fingerprint
JARM
2ad2ad16d2ad2ad00042d42d000000332dc9cd7d90589195193c8bb05d84fa
JA3S
15af977ce25de452b96affa2addb1036
JA4S
t120200_544c535f4145535f3235365f47434d5f534841333834_9f090db0cf15

HTTP 9035/TCP
05/19/2024 18:24 UTC


Software

nginx 1.18.0

Details

http://45.134.225.36:9035/
Status
401  Unauthorized
Body Hash
sha1:1a6b2b7fa1b0c887c0d17755de73737b48e76d19
HTML Title
401 Authorization Required
Response Body
      # 401 Authorization Required

* * *

nginx/1.18.0 (Ubuntu)
    

HTTP 9036/TCP
05/19/2024 17:27 UTC


Software

nginx 1.18.0

Details

http://45.134.225.36:9036/
Status
401  Unauthorized
Body Hash
sha1:1a6b2b7fa1b0c887c0d17755de73737b48e76d19
HTML Title
401 Authorization Required
Response Body
      # 401 Authorization Required

* * *

nginx/1.18.0 (Ubuntu)
    

HTTP 9037/TCP
05/19/2024 17:48 UTC


Software

nginx 1.18.0

Details

http://45.134.225.36:9037/
Status
401  Unauthorized
Body Hash
sha1:1a6b2b7fa1b0c887c0d17755de73737b48e76d19
HTML Title
401 Authorization Required
Response Body
      # 401 Authorization Required

* * *

nginx/1.18.0 (Ubuntu)
    

HTTP 9038/TCP
05/19/2024 18:07 UTC


Software

nginx 1.18.0

Details

http://45.134.225.36:9038/
Status
401  Unauthorized
Body Hash
sha1:1a6b2b7fa1b0c887c0d17755de73737b48e76d19
HTML Title
401 Authorization Required
Response Body
      # 401 Authorization Required

* * *

nginx/1.18.0 (Ubuntu)
    

HTTP 9039/TCP
05/19/2024 18:26 UTC


Software

nginx 1.18.0

Details

http://45.134.225.36:9039/
Status
401  Unauthorized
Body Hash
sha1:1a6b2b7fa1b0c887c0d17755de73737b48e76d19
HTML Title
401 Authorization Required
Response Body
      # 401 Authorization Required

* * *

nginx/1.18.0 (Ubuntu)
    

HTTP 9040/TCP
05/19/2024 18:21 UTC


Software

nginx 1.18.0

Details

http://45.134.225.36:9040/
Status
401  Unauthorized
Body Hash
sha1:1a6b2b7fa1b0c887c0d17755de73737b48e76d19
HTML Title
401 Authorization Required
Response Body
      # 401 Authorization Required

* * *

nginx/1.18.0 (Ubuntu)
    

HTTP 9041/TCP
05/19/2024 19:03 UTC


Software

nginx 1.18.0

Details

http://45.134.225.36:9041/
Status
401  Unauthorized
Body Hash
sha1:1a6b2b7fa1b0c887c0d17755de73737b48e76d19
HTML Title
401 Authorization Required
Response Body
      # 401 Authorization Required

* * *

nginx/1.18.0 (Ubuntu)
    

HTTP 9042/TCP
05/19/2024 18:28 UTC


Software

nginx 1.18.0

Details

http://45.134.225.36:9042/
Status
401  Unauthorized
Body Hash
sha1:1a6b2b7fa1b0c887c0d17755de73737b48e76d19
HTML Title
401 Authorization Required
Response Body
      # 401 Authorization Required

* * *

nginx/1.18.0 (Ubuntu)
    

HTTP 9100/TCP
05/19/2024 19:12 UTC


Software

nginx 1.18.0

Details

http://45.134.225.36:9100/
Status
401  Unauthorized
Body Hash
sha1:1a6b2b7fa1b0c887c0d17755de73737b48e76d19
HTML Title
401 Authorization Required
Response Body
      # 401 Authorization Required

* * *

nginx/1.18.0 (Ubuntu)
    

HTTP 9167/TCP
05/19/2024 18:36 UTC


Software

nginx 1.18.0

Details

http://45.134.225.36:9167/
Status
401  Unauthorized
Body Hash
sha1:1a6b2b7fa1b0c887c0d17755de73737b48e76d19
HTML Title
401 Authorization Required
Response Body
      # 401 Authorization Required

* * *

nginx/1.18.0 (Ubuntu)
    

UNKNOWN 10444/TCP
05/19/2024 18:20 UTC


Software

linux

Details

TLS

Handshake
Version Selected
TLSv1_3
Cipher Selected
TLS_AES_256_GCM_SHA384
Certificate
Fingerprint
fa5cc0e321c892d61fd9bb88a66011dac62fb12b3e69d180e0ff94a38f3bd008
Subject
CN=www.dqzkm4qw.net
Issuer
CN=www.axrz6lxt4febqkcsublf.com
Names
www.dqzkm4qw.net
Fingerprint
JARM
2ad2ad16d2ad2ad00042d42d000000332dc9cd7d90589195193c8bb05d84fa
JA3S
15af977ce25de452b96affa2addb1036
JA4S
t120200_544c535f4145535f3235365f47434d5f534841333834_9f090db0cf15

UNKNOWN 11444/TCP
05/19/2024 18:04 UTC


Software

linux

Details

TLS

Handshake
Version Selected
TLSv1_3
Cipher Selected
TLS_AES_256_GCM_SHA384
Certificate
Fingerprint
8d23efe4804031a66e5bb4a1322be54676b218140903a2421cf281a4a2590687
Subject
CN=www.whh5ktkz33t.net
Issuer
CN=www.pzpduvpwrcjq.com
Names
www.whh5ktkz33t.net
Fingerprint
JARM
2ad2ad16d2ad2ad00042d42d000000332dc9cd7d90589195193c8bb05d84fa
JA3S
15af977ce25de452b96affa2addb1036
JA4S
t120200_544c535f4145535f3235365f47434d5f534841333834_9f090db0cf15

UNKNOWN 12444/TCP
05/19/2024 18:01 UTC


Software

linux

Details

TLS

Handshake
Version Selected
TLSv1_3
Cipher Selected
TLS_AES_256_GCM_SHA384
Certificate
Fingerprint
b6c1ebcfe3fc53fca45c8f81382ea0a9ac121eee4c64d1da21d71ff94a77302f
Subject
CN=www.w4bxdsxs7atu23splg.net
Issuer
CN=www.lknp5hmvl2mwtmk5.com
Names
www.w4bxdsxs7atu23splg.net
Fingerprint
JARM
2ad2ad16d2ad2ad00042d42d000000332dc9cd7d90589195193c8bb05d84fa
JA3S
15af977ce25de452b96affa2addb1036
JA4S
t120200_544c535f4145535f3235365f47434d5f534841333834_9f090db0cf15

UNKNOWN 13444/TCP
05/17/2024 15:40 UTC

Pending Removal

Software

linux

Details

TLS

Handshake
Version Selected
TLSv1_3
Cipher Selected
TLS_AES_256_GCM_SHA384
Certificate
Fingerprint
37eaa96c3e08ed9e69543485c814a4ee8d3c102592f8b5c1de87b5024439a4fb
Subject
CN=www.pxivrfbx4ep.net
Issuer
CN=www.6gtc6rqih47mypfr.com
Names
www.pxivrfbx4ep.net
Fingerprint
JARM
2ad2ad16d2ad2ad00042d42d000000332dc9cd7d90589195193c8bb05d84fa
JA3S
15af977ce25de452b96affa2addb1036
JA4S
t120200_544c535f4145535f3235365f47434d5f534841333834_9f090db0cf15

Geographic Location

City
Amsterdam
Province
North Holland
Country
Netherlands (NL)
Coordinates
52.37403, 4.88969
Timezone
Europe/Amsterdam