Details for Proxy 190.97.238.87:999

IP 190.97.238.87
Port 999
Protocols HTTP, HTTPS
Country Venezuela (VE) VE
ISP VIGINET C.A
Date Added 2024-02-11 16:05:49
Date Last Checked 2024-02-27 01:15:59
HTTP
Checks Total 3
Checks Successful 1
Checks Failed 2
Checks Failed Consecutive 2
Ø Uptime 33.33%
Last Successful Check 2024-02-24 03:54:59
Last Failed Check 2024-02-27 01:15:59
Last Response Time 8.73s
Ø Response Time 8.73s
Anonymity Level transparent
Via 1.1 ::ffff:190.97.238.82 (Mikrotik HttpProxy)
Gateway 190.97.231.195
Retries 1
Headers
via              1.1 ::ffff:190.97.238.82 (Mikrotik HttpProxy)
x-forwarded-for  85.214.115.35
x-proxy-id       715925424
Headers (in)
server  Apache
Output (success)
Toggle
<html><head><title>Env.cgi</title></head><body>
I am <B>uid=2001(ken) gid=15(users) groups=15(users)</B> on <B>depts03.u.washington.edu</B><br>
Don't know who you are

<h3><a name=env>My environment follows:</h3>
<pre>
_=*20695*/usr/bin/env
CONTEXT_DOCUMENT_ROOT=/hw00/d01/ken/.
CONTEXT_PREFIX=/ken
DOCUMENT_ROOT=/www
GATEWAY_INTERFACE=CGI/1.1
HTTP_ACCEPT=*/*
HTTP_CONNECTION=close
HTTP_HOST=depts.washington.edu
HTTP_USER_AGENT=Mozilla/5.0
HTTP_VIA=1.1 ::ffff:190.97.238.82 (Mikrotik HttpProxy)
HTTP_X_FORWARDED_FOR=85.214.115.35
HTTP_X_PROXY_ID=715925424
PATH=/usr/local/bin:/usr/bin:/bin
PWD=/nfs/bronfs/uwfs/hw00/d01/ken
QUERY_STRING=
REMOTE_ADDR=190.97.231.195
REMOTE_PORT=34074
REQUEST_METHOD=GET
REQUEST_SCHEME=http
REQUEST_URI=/ken/env.cgi
SCRIPT_FILENAME=/hw00/d01/ken/env.cgi
SCRIPT_NAME=/ken/env.cgi
SERVER_ADDR=128.208.61.62
SERVER_ADMIN=help@uw.edu
SERVER_NAME=depts.washington.edu
SERVER_PORT=80
SERVER_PROTOCOL=HTTP/1.1
SERVER_SIGNATURE=
SERVER_SOFTWARE=Apache
SHLVL=1
A__z="*SHLVL
</pre>
<h3>Stuff on stdin follows</h3>
<pre>
</pre>
End of stdin
</body></html>

*   Trying 190.97.238.87:999...
* Connected to (nil) (190.97.238.87) port 999 (#0)
> GET http://depts.washington.edu/ken/env.cgi HTTP/1.1
> Host: depts.washington.edu
> User-Agent: Mozilla/5.0
> Accept: */*
> Proxy-Connection: Keep-Alive
> 
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< date: Sat, 24 Feb 2024 02:53:59 GMT
< server: Apache
< vary: Accept-Encoding
< transfer-encoding: chunked
< content-type: text/html
< 
{ [1101 bytes data]
* Connection #0 to host (nil) left intact
Output (fail)
Toggle

                                        
*   Trying 190.97.238.87:999...
* After 15000ms connect time, move on!
* connect to 190.97.238.87 port 999 failed: Connection timed out
* Connection timeout after 15000 ms
* Closing connection 0
curl: (28) Connection timeout after 15000 ms
Last Error Connection timeout after 15000 ms
HTTPS
Checks Total 10
Checks Successful 4
Checks Failed 6
Checks Failed Consecutive 4
Ø Uptime 40.00%
Last Successful Check 2024-02-20 01:34:37
Last Failed Check 2024-02-27 01:15:59
Last Response Time 11.95s
Ø Response Time 8.30s
Anonymity Level elite
Gateway 190.97.231.195
Retries 0
Headers (in)
server      Apache
set-cookie  _affinity=d04|ZdPzo; path=/; HttpOnly; Secure
Output (success)
Toggle
<html><head><title>Env.cgi</title></head><body>
I am <B>uid=2001(ken) gid=15(users) groups=15(users)</B> on <B>depts04.u.washington.edu</B><br>
Don't know who you are

<h3><a name=env>My environment follows:</h3>
<pre>
_=*24142*/usr/bin/env
CONTEXT_DOCUMENT_ROOT=/hw00/d01/ken/.
CONTEXT_PREFIX=/ken
DOCUMENT_ROOT=/www
GATEWAY_INTERFACE=CGI/1.1
HTTPS=on
HTTP_ACCEPT=*/*
HTTP_HOST=depts.washington.edu
HTTP_USER_AGENT=Mozilla/5.0
PATH=/usr/local/bin:/usr/bin:/bin
PWD=/nfs/bronfs/uwfs/hw00/d01/ken
QUERY_STRING=
REMOTE_ADDR=190.97.231.195
REMOTE_PORT=53370
REQUEST_METHOD=GET
REQUEST_SCHEME=https
REQUEST_URI=/ken/env.cgi
SCRIPT_FILENAME=/hw00/d01/ken/env.cgi
SCRIPT_NAME=/ken/env.cgi
SERVER_ADDR=128.208.60.162
SERVER_ADMIN=help@uw.edu
SERVER_NAME=depts.washington.edu
SERVER_PORT=443
SERVER_PROTOCOL=HTTP/2.0
SERVER_SIGNATURE=
SERVER_SOFTWARE=Apache
SHLVL=1
SSL_CIPHER=ECDHE-RSA-AES256-GCM-SHA384
SSL_CIPHER_ALGKEYSIZE=256
SSL_CIPHER_EXPORT=false
SSL_CIPHER_USEKEYSIZE=256
SSL_CLIENT_VERIFY=NONE
SSL_COMPRESS_METHOD=NULL
SSL_PROTOCOL=TLSv1.2
SSL_SECURE_RENEG=true
SSL_SERVER_A_KEY=rsaEncryption
SSL_SERVER_A_SIG=sha256WithRSAEncryption
SSL_SERVER_I_DN=CN=R3,O=Let's Encrypt,C=US
SSL_SERVER_I_DN_C=US
SSL_SERVER_I_DN_CN=R3
SSL_SERVER_I_DN_O=Let's Encrypt
SSL_SERVER_M_SERIAL=03EE33209EC2004C7DDC404E9B4D82B9CC43
SSL_SERVER_M_VERSION=3
SSL_SERVER_SAN_DNS_0=courses.washington.edu
SSL_SERVER_SAN_DNS_1=depts.washington.edu
SSL_SERVER_SAN_DNS_2=faculty.washington.edu
SSL_SERVER_SAN_DNS_3=staff.washington.edu
SSL_SERVER_SAN_DNS_4=www.courses.washington.edu
SSL_SERVER_SAN_DNS_5=www.depts.washington.edu
SSL_SERVER_SAN_DNS_6=www.faculty.washington.edu
SSL_SERVER_SAN_DNS_7=www.staff.washington.edu
SSL_SERVER_S_DN=CN=depts.washington.edu
SSL_SERVER_S_DN_CN=depts.washington.edu
SSL_SERVER_V_END=May 13 18:05:28 2024 GMT
SSL_SERVER_V_START=Feb 13 18:05:29 2024 GMT
SSL_SESSION_ID=c014c9cd7c5e9556ecf1f01e4c4931f71b3c8090eaab4f86bd95695e964854f2
SSL_SESSION_RESUMED=Resumed
SSL_VERSION_INTERFACE=mod_ssl/2.4.56
SSL_VERSION_LIBRARY=OpenSSL/1.0.2k-fips
A__z="*SHLVL
</pre>
<h3>Stuff on stdin follows</h3>
<pre>
</pre>
End of stdin
</body></html>

*   Trying 190.97.238.87:999...
* Connected to (nil) (190.97.238.87) port 999 (#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.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):
{ [122 bytes data]
* TLSv1.2 (IN), TLS header, Finished (20):
{ [5 bytes data]
* TLSv1.2 (IN), TLS header, Supplemental data (23):
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
{ [19 bytes data]
* TLSv1.2 (IN), TLS header, Supplemental data (23):
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Certificate (11):
{ [2779 bytes data]
* TLSv1.2 (IN), TLS header, Supplemental data (23):
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
{ [264 bytes data]
* TLSv1.2 (IN), TLS header, Supplemental data (23):
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Finished (20):
{ [52 bytes data]
* TLSv1.2 (OUT), TLS header, Finished (20):
} [5 bytes data]
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Finished (20):
} [52 bytes data]
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=depts.washington.edu
*  start date: Feb 13 18:05:29 2024 GMT
*  expire date: May 13 18:05:28 2024 GMT
*  issuer: C=US; O=Let's Encrypt; CN=R3
*  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 0x55a55a52be90)
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
} [5 bytes data]
> GET /ken/env.cgi HTTP/2
> Host: depts.washington.edu
> user-agent: Mozilla/5.0
> accept: */*
> 
* TLSv1.2 (IN), TLS header, Supplemental data (23):
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [265 bytes data]
* TLSv1.2 (IN), TLS header, Supplemental data (23):
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [265 bytes data]
* old SSL session ID is stale, removing
* TLSv1.2 (IN), TLS header, Supplemental data (23):
{ [5 bytes data]
* 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 
< vary: Accept-Encoding
< content-type: text/html
< date: Tue, 20 Feb 2024 00:34:37 GMT
< server: Apache
< set-cookie: _affinity=d04|ZdPzo; path=/; HttpOnly; Secure
< cache-control: private
< 
{ [219 bytes data]
* TLSv1.2 (IN), 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]
* Connection #0 to host (nil) left intact
Output (fail)
Toggle

                                        
*   Trying 190.97.238.87:999...
* Connected to (nil) (190.97.238.87) port 999 (#0)
* allocate connect buffer!
* Establish HTTP proxy tunnel to www.jreming.com:443
> CONNECT www.jreming.com:443 HTTP/1.1
> Host: www.jreming.com:443
> User-Agent: Mozilla/5.0
> Proxy-Connection: Keep-Alive
> 
* Proxy CONNECT aborted due to timeout
* CONNECT phase completed!
* Operation timed out after 15000 milliseconds with 0 bytes received
* Closing connection 0
curl: (28) Proxy CONNECT aborted due to timeout
Last Error Proxy CONNECT aborted due to timeout