Details for Proxy 72.210.252.134:46164

IP 72.210.252.134
Port 46164
Protocols SOCKS4, SOCKS5
Host
Country United States (US) US
City -
Region -
ISP ASN-CXA-ALL-CCI-22773-RDC
Date Added 2020-03-24 18:51:01
Date Last Checked 2022-01-17 16:21:58
SOCKS4
Checks Total 513
Checks Successful 425
Checks Failed 88
Checks Failed Consecutive 0
Ø Uptime 82.85%
Last Successful Check 2022-01-17 16:21:58
Last Failed Check 2021-11-15 02:06:38
Last Response Time 0.85s
Ø Response Time 2.37s
Anonymity Level Elite
Via -
Gateway -
Retries 0
Headers -
Output (success)
{"headers":{"Host":"proxydb.net","User-Agent":"curl\/7.57.0"},"id":"ProxyDB","ip":"72.210.252.134"}
*   Trying 72.210.252.134...
* TCP_NODELAY set
* SOCKS4 communication to proxydb.net:80
* SOCKS4 connect to IPv4 85.214.115.35 (locally resolved)
* SOCKS4 request granted.
* Connected to 72.210.252.134 (72.210.252.134) port 46164 (#0)
> GET /judge HTTP/1.1
> Host: proxydb.net
> User-Agent: curl/7.57.0
> 
< HTTP/1.1 200 OK
< Date: Mon, 17 Jan 2022 15:21:56 GMT
< Content-Length: 99
< Content-Type: application/json;charset=UTF-8
< 
{ [99 bytes data]
* Connection #0 to host 72.210.252.134 left intact
Output (fail)

                                
*   Trying 72.210.252.134...
* TCP_NODELAY set
* Connected to 72.210.252.134 (72.210.252.134) port 46164 (#0)
> GET http://proxydb.net/judge HTTP/1.1
> Host: proxydb.net
> User-Agent: curl/7.57.0
> Proxy-Connection: Keep-Alive
> 
* Operation timed out after 60001 milliseconds with 0 bytes received
* Closing connection 0
curl: (28) Operation timed out after 60001 milliseconds with 0 bytes received
SOCKS5
Checks Total 513
Checks Successful 422
Checks Failed 91
Checks Failed Consecutive 0
Ø Uptime 82.26%
Last Successful Check 2022-01-17 16:21:58
Last Failed Check 2021-11-15 02:06:38
Last Response Time 1.07s
Ø Response Time 2.62s
Anonymity Level Elite
Via -
Gateway -
Retries 0
Headers -
Output (success)
{"headers":{"Host":"proxydb.net","User-Agent":"curl\/7.57.0"},"id":"ProxyDB","ip":"72.210.252.134"}
*   Trying 72.210.252.134...
* TCP_NODELAY set
* SOCKS5 communication to proxydb.net:80
* SOCKS5 connect to IPv4 85.214.115.35 (locally resolved)
* SOCKS5 request granted.
* Connected to 72.210.252.134 (72.210.252.134) port 46164 (#0)
> GET /judge HTTP/1.1
> Host: proxydb.net
> User-Agent: curl/7.57.0
> 
< HTTP/1.1 200 OK
< Date: Mon, 17 Jan 2022 15:21:57 GMT
< Content-Length: 99
< Content-Type: application/json;charset=UTF-8
< 
{ [99 bytes data]
* Connection #0 to host 72.210.252.134 left intact
Output (fail)

                                
*   Trying 72.210.252.134...
* TCP_NODELAY set
* Connected to 72.210.252.134 (72.210.252.134) port 46164 (#0)
> GET http://proxydb.net/judge HTTP/1.1
> Host: proxydb.net
> User-Agent: curl/7.57.0
> Proxy-Connection: Keep-Alive
> 
* Operation timed out after 60001 milliseconds with 0 bytes received
* Closing connection 0
curl: (28) Operation timed out after 60001 milliseconds with 0 bytes received