Details for Proxy 66.42.224.229:41679

IP 66.42.224.229
Port 41679
Protocols SOCKS4, SOCKS5
Host fuse-dedicated-66-42-224-229.fuse.net
Country United States (US) US
City -
Region -
ISP FUSE-NET
Date Added 2022-03-18 06:18:13
Date Last Checked 2022-08-07 10:15:03
SOCKS4
Checks Total 188
Checks Successful 152
Checks Failed 36
Checks Failed Consecutive 0
Ø Uptime 80.85%
Last Successful Check 2022-08-07 10:15:03
Last Failed Check 2022-08-06 09:08:03
Last Response Time 10.66s
Ø Response Time 9.12s
Anonymity Level Elite
Via -
Gateway -
Retries 0
Headers -
Output (success)
{"headers":{"Host":"proxydb.net","User-Agent":"curl\/7.57.0"},"id":"ProxyDB","ip":"66.42.224.229"}
*   Trying 66.42.224.229...
* TCP_NODELAY set
* SOCKS4 communication to proxydb.net:80
* SOCKS4 connect to IPv4 85.214.115.35 (locally resolved)
* SOCKS4 request granted.
* Connected to 66.42.224.229 (66.42.224.229) port 41679 (#0)
> GET /judge HTTP/1.1
> Host: proxydb.net
> User-Agent: curl/7.57.0
> 
< HTTP/1.1 200 OK
< Content-Type: application/json;charset=UTF-8
< Date: Sun, 07 Aug 2022 08:14:50 GMT
< Content-Length: 98
< 
{ [98 bytes data]
* Connection #0 to host 66.42.224.229 left intact
Output (fail)

                                
*   Trying 66.42.224.229...
* TCP_NODELAY set
* Connected to 66.42.224.229 (66.42.224.229) port 41679 (#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 175
Checks Successful 118
Checks Failed 57
Checks Failed Consecutive 0
Ø Uptime 67.43%
Last Successful Check 2022-08-07 10:15:03
Last Failed Check 2022-08-06 09:08:03
Last Response Time 11.70s
Ø Response Time 8.27s
Anonymity Level Elite
Via -
Gateway -
Retries 0
Headers -
Output (success)
{"headers":{"Host":"proxydb.net","User-Agent":"curl\/7.57.0"},"id":"ProxyDB","ip":"66.42.224.229"}
*   Trying 66.42.224.229...
* TCP_NODELAY set
* SOCKS5 communication to proxydb.net:80
* SOCKS5 connect to IPv4 85.214.115.35 (locally resolved)
* SOCKS5 request granted.
* Connected to 66.42.224.229 (66.42.224.229) port 41679 (#0)
> GET /judge HTTP/1.1
> Host: proxydb.net
> User-Agent: curl/7.57.0
> 
< HTTP/1.1 200 OK
< Content-Length: 98
< Date: Sun, 07 Aug 2022 08:15:02 GMT
< Content-Type: application/json;charset=UTF-8
< 
{ [98 bytes data]
* Connection #0 to host 66.42.224.229 left intact
Output (fail)

                                
*   Trying 66.42.224.229...
* TCP_NODELAY set
* Connected to 66.42.224.229 (66.42.224.229) port 41679 (#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