Details for Proxy 110.39.9.155:8080

IP 110.39.9.155
Port 8080
Protocols HTTPS
Host WGPON-399-155.wateen.net
Country Pakistan (PK) PK
ISP National WiMAXIMS environment
Date Added 2023-05-13 06:02:02
Date Last Checked 2023-11-28 00:06:14
HTTPS
Checks Total 114
Checks Successful 56
Checks Failed 58
Checks Failed Consecutive 4
Ø Uptime 49.12%
Last Successful Check 2023-11-21 00:06:59
Last Failed Check 2023-11-28 00:06:14
Last Response Time 6.03s
Ø Response Time 5.81s
Anonymity Level elite
Retries 0
Headers (in)
server  nginx/1.10.3 (Ubuntu)
Output (success)
Toggle
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
   "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<title>AZ Environment variables 1.04</title>
</head>
<body>
<pre>
HTTP_ACCEPT = */*
HTTP_USER_AGENT = Mozilla/5.0
HTTP_HOST = www.jremi.com
REMOTE_PORT = 37195
REMOTE_ADDR = 110.39.9.155
HTTPS = on
REQUEST_SCHEME = https
REQUEST_URI = /
REQUEST_METHOD = GET
REQUEST_TIME_FLOAT = 1700521619.1477
REQUEST_TIME = 1700521619
</pre>
</body>
</html>

*   Trying 110.39.9.155:8080...
* Connected to (nil) (110.39.9.155) port 8080 (#0)
* allocate connect buffer!
* Establish HTTP proxy tunnel to www.jremi.com:443
> CONNECT www.jremi.com:443 HTTP/1.1
> Host: www.jremi.com:443
> User-Agent: Mozilla/5.0
> Proxy-Connection: Keep-Alive
> 
< HTTP/1.1 200 OK
< 
* Proxy replied 200 to CONNECT request
* CONNECT phase completed!
* ALPN, offering h2
* ALPN, offering http/1.1
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* TLSv1.2 (IN), TLS header, Certificate Status (22):
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [98 bytes data]
* TLSv1.2 (IN), TLS header, Certificate Status (22):
{ [5 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [4570 bytes data]
* TLSv1.2 (IN), TLS header, Certificate Status (22):
{ [5 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [333 bytes data]
* TLSv1.2 (IN), TLS header, Certificate Status (22):
{ [5 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
} [5 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [70 bytes data]
* TLSv1.2 (OUT), TLS header, Finished (20):
} [5 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
} [5 bytes data]
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
* TLSv1.2 (IN), TLS header, Finished (20):
{ [5 bytes data]
* TLSv1.2 (IN), TLS header, Certificate Status (22):
{ [5 bytes data]
* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=*.jremi.com
*  start date: Sep 30 00:00:00 2022 GMT
*  expire date: Oct  3 23:59:59 2023 GMT
*  issuer: C=GB; ST=Greater Manchester; L=Salford; O=Sectigo Limited; CN=Sectigo RSA Domain Validation Secure Server CA
*  SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway.
* Using HTTP2, server supports multiplexing
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
} [5 bytes data]
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
} [5 bytes data]
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
} [5 bytes data]
* Using Stream ID: 1 (easy handle 0x5620bb223e90)
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
} [5 bytes data]
> GET / HTTP/2
> Host: www.jremi.com
> user-agent: Mozilla/5.0
> accept: */*
> 
* TLSv1.2 (IN), TLS header, Supplemental data (23):
{ [5 bytes data]
* Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
} [5 bytes data]
* TLSv1.2 (IN), TLS header, Supplemental data (23):
{ [5 bytes data]
* TLSv1.2 (IN), TLS header, Supplemental data (23):
{ [5 bytes data]
< HTTP/2 200 
< server: nginx/1.10.3 (Ubuntu)
< date: Mon, 20 Nov 2023 23:06:59 GMT
< content-type: text/html; charset=UTF-8
< 
{ [543 bytes data]
* Connection #0 to host (nil) left intact
Output (fail)
Toggle

                                        
*   Trying 110.39.9.155:8080...
* Connected to (nil) (110.39.9.155) port 8080 (#0)
* allocate connect buffer!
* Establish HTTP proxy tunnel to depts.washington.edu:443
> CONNECT depts.washington.edu:443 HTTP/1.1
> Host: depts.washington.edu:443
> User-Agent: Mozilla/5.0
> Proxy-Connection: Keep-Alive
> 
< HTTP/1.0 404 Not Found
< Content-Length: 736
< Content-Type: text/html
< Date: Mon, 27 Nov 2023 23:06:14 GMT
< Expires: Mon, 27 Nov 2023 23:06:14 GMT
< Server: Mikrotik HttpProxy
< Proxy-Connection: close
< 
* Received HTTP code 404 from proxy after CONNECT
* CONNECT phase completed!
* Closing connection 0
curl: (56) Received HTTP code 404 from proxy after CONNECT
Last Error Received HTTP code 404 from proxy after CONNECT