104.244.74.57
As of: Dec 09, 2023 5:02am UTC |
Latest
Basic Information
- Reverse DNS
- tor1.panhu.xyz
- Routing
- 104.244.74.0/24 via PONYNET, US (AS53667)
- Services (5)
- 80/HTTP, 443/HTTP, 8081/HTTP, 8443/HTTP, 9002/UNKNOWN
Details
http://104.244.74.57/
- Status
- 200 OK
- Body Hash
-
sha1:8ea4782bda9b9b2cd63d82f4d4f13d8721199207
- HTML Title
-
This is a Tor Exit Router
- Response Body
-
This is a Tor Exit Router Most likely you are accessing this website because you 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://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. [  ](https://www.torproject.org/about/overview) Tor sees use by [many important segments of the population](https://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://www.torproject.org/docs/faq-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](http://voices.washingtonpost.com/securityfix/2008/08/web_fraud_20_tools.html) far larger and [more powerful networks](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](http://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 104.244.74.57 or 2605:6400:30:f625:20:20:0:2 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](http://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://www.torproject.org/eff/tor-dmca-response) for more information on this matter. For more information, please consult the following documentation: 1. [Tor Overview](https://www.torproject.org/about/overview) 2. [Tor Abuse FAQ](https://www.torproject.org/docs/faq-abuse) 3. [Tor Legal FAQ](https://www.torproject.org/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/cgi-bin/TorBulkExitList.py) 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://www.torproject.org/tordnsel/dist/) 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.
Details
https://104.244.74.57/
- Status
- 200 OK
- Body Hash
-
sha1:8ea4782bda9b9b2cd63d82f4d4f13d8721199207
- HTML Title
-
This is a Tor Exit Router
- Response Body
-
This is a Tor Exit Router Most likely you are accessing this website because you 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://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. [  ](https://www.torproject.org/about/overview) Tor sees use by [many important segments of the population](https://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://www.torproject.org/docs/faq-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](http://voices.washingtonpost.com/securityfix/2008/08/web_fraud_20_tools.html) far larger and [more powerful networks](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](http://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 104.244.74.57 or 2605:6400:30:f625:20:20:0:2 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](http://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://www.torproject.org/eff/tor-dmca-response) for more information on this matter. For more information, please consult the following documentation: 1. [Tor Overview](https://www.torproject.org/about/overview) 2. [Tor Abuse FAQ](https://www.torproject.org/docs/faq-abuse) 3. [Tor Legal FAQ](https://www.torproject.org/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/cgi-bin/TorBulkExitList.py) 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://www.torproject.org/tordnsel/dist/) 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.
TLS
Handshake
- Version Selected
- TLSv1_3
- Cipher Selected
- TLS_AES_256_GCM_SHA384
Certificate
- Fingerprint
- a5e6f69765e75c52777667de4c74be8e6c0b1294731bd1637f3196dc8f33a70b
- Subject
- CN=tor1.panhu.xyz
- Issuer
- C=US, O=Let's Encrypt, CN=R3
- Names
- tor1.panhu.xyz
Fingerprint
Details
http://104.244.74.57:8081/
- Status
- 200 OK
- Body Hash
-
sha1:8ea4782bda9b9b2cd63d82f4d4f13d8721199207
- HTML Title
-
This is a Tor Exit Router
- Response Body
-
This is a Tor Exit Router Most likely you are accessing this website because you 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://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. [  ](https://www.torproject.org/about/overview) Tor sees use by [many important segments of the population](https://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://www.torproject.org/docs/faq-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](http://voices.washingtonpost.com/securityfix/2008/08/web_fraud_20_tools.html) far larger and [more powerful networks](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](http://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 104.244.74.57 or 2605:6400:30:f625:20:20:0:2 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](http://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://www.torproject.org/eff/tor-dmca-response) for more information on this matter. For more information, please consult the following documentation: 1. [Tor Overview](https://www.torproject.org/about/overview) 2. [Tor Abuse FAQ](https://www.torproject.org/docs/faq-abuse) 3. [Tor Legal FAQ](https://www.torproject.org/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/cgi-bin/TorBulkExitList.py) 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://www.torproject.org/tordnsel/dist/) 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.
Details
https://104.244.74.57:8443/
- Status
- 200 OK
- Body Hash
-
sha1:8ea4782bda9b9b2cd63d82f4d4f13d8721199207
- HTML Title
-
This is a Tor Exit Router
- Response Body
-
This is a Tor Exit Router Most likely you are accessing this website because you 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://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. [  ](https://www.torproject.org/about/overview) Tor sees use by [many important segments of the population](https://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://www.torproject.org/docs/faq-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](http://voices.washingtonpost.com/securityfix/2008/08/web_fraud_20_tools.html) far larger and [more powerful networks](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](http://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 104.244.74.57 or 2605:6400:30:f625:20:20:0:2 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](http://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://www.torproject.org/eff/tor-dmca-response) for more information on this matter. For more information, please consult the following documentation: 1. [Tor Overview](https://www.torproject.org/about/overview) 2. [Tor Abuse FAQ](https://www.torproject.org/docs/faq-abuse) 3. [Tor Legal FAQ](https://www.torproject.org/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/cgi-bin/TorBulkExitList.py) 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://www.torproject.org/tordnsel/dist/) 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.
TLS
Handshake
- Version Selected
- TLSv1_3
- Cipher Selected
- TLS_AES_256_GCM_SHA384
Certificate
- Fingerprint
- 74619ae0173ce1f5c4dea655a7629e0a99c464f93ca63046bd7fb982a7b8eeb6
- Subject
- CN=t.panhu.xyz
- Issuer
- C=US, O=Let's Encrypt, CN=Let's Encrypt Authority X3
- Names
- t.panhu.xyz
Fingerprint
Details
TLS
Handshake
- Version Selected
- TLSv1_3
- Cipher Selected
- TLS_AES_256_GCM_SHA384
Certificate
- Fingerprint
- 997d6a1716e589ddae059da0eb796c82f8e9da955724e1505f53c28e88ddf8e6
- Subject
- CN=www.w2rehtat5o.net
- Issuer
- CN=www.72pxnm7r5jcugr3bbt6.com
- Names
- www.w2rehtat5o.net
Fingerprint
Geographic Location
- City
- Luxembourg
- Province
- Luxembourg
- Country
- Luxembourg (LU)
- Coordinates
- 49.61167, 6.13
- Timezone
- Europe/Luxembourg