- Scan ID:
- 908d9731-3733-4a63-9c76-1f89fa797226Finished
- Submitted URL:
- https://www.lagado.com/tools/proxy-test
- Report Finished:
Links · 6 found
The outgoing links identified from the page
| Link | Text |
|---|---|
| http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.45 | rfc2616 |
| http://www.ics.uci.edu/pub/ietf/http/history/draft-ietf-http-v10-spec-01.html | draft-ietf-http-v10-spec-01 |
| http://squid.visolve.com/ | Squid Configuration Guide |
| http://www.linofee.org/~elkner/proxy/Squid/rel-notes-1_1.html#x | Squid Release Notes 1.1 |
| http://www.securiteam.com/securitynews/6W00X0035M.html | more background |
| http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9 | Cache-Control: no-cache |
JavaScript Variables · 3 found
Global JavaScript variables loaded on the window object of a page, are variables declared outside of functions and accessible from anywhere in the code within the current scope
| Name | Type |
|---|---|
| onbeforetoggle | string |
| documentPictureInPicture | string |
| onscrollend | string |
Console log messages · 1 found
Messages logged to the web console
| Type | Category | Log |
|---|---|---|
| error | network |
|
HTML
The raw HTML body of the page
<!DOCTYPE html><html><head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link rel="stylesheet" href="/module/frontlib/bootstrap-3.2.0/dist/css/bootstrap.css">
<link rel="stylesheet" href="/tools/inc/main.css">
<title>Proxy Test</title>
<style>
.testresult {
font-weight:bold; font-size:large;
}
#request-headers-table {
background:#F0F0F8;
border-collapse:collapse;
border:1px solid #666;
}
#request-headers-table td {
border:1px solid #666;
padding:0.1em 0.3em;
}
#summary { }
</style>
<meta name="description" content="The Lagado Proxy Test will show details of any proxy servers you are using. Shows hidden or transparent proxies.">
<meta name="keywords" content="http, proxy, test, transparent, hidden">
</head>
<body>
<div class="page_container">
<div class="header">
<a href="/tools" class="header-link"><img src="/tools/image/lagado-logo.gif" align="top" border="0" height="16" width="16">Lagado Tools</a>
</div>
<div class="main-panel">
<h1>Proxy Test</h1>
<div id="summary">
<p class="testresult">
This request appears to have come via a proxy.
</p>
<p>The proxy host is <b>server-130-176-170-69.mad51.r.cloudfront.net</b> which has ip address 130.176.170.69</p>
<p>The proxy server has announced itself as <b>2.0 bda01991f70d6041a75ac1d53fe4336a.cloudfront.net (CloudFront)</b></p>
<p>The proxy informs us that the client host ip address was 104.28.154.60</p>
<p> </p>
<p>The <a href="http://www.lagado.com">Lagado</a> Proxy Test shows details of any proxy servers you are using. It is especially useful to expose transparent proxies. These are proxies inserted between your browser and the web, typically by your ISP, and often without you knowing.</p>
<p>
Sometimes a proxy will be deliberately hidden so it won't be exposed by this test. In this case you can use the <a href="/tools/cache-test">Cache Test</a> to expose stealthed transparent proxy caches.</p>
<p> </p>
</div>
<h3>The Raw Details</h3>
<p>
Here are the raw details of the request received by this server.
</p>
<p>
<b>Remote Host</b> server-130-176-170-69.mad51.r.cloudfront.net <b>IP Address</b> 130.176.170.69
</p>
<p>
<b>Request Protocol</b> HTTP/1.1 <b>Method</b> GET
</p>
<b>Request Headers</b>
<table id="request-headers-table">
<tbody><tr><td align="right"><b>Host</b></td><td>toolspub.lagado.com</td></tr><tr><td align="right"><b>User-Agent</b></td><td>Amazon CloudFront</td></tr><tr><td align="right"><b>X-Amz-Cf-Id</b></td><td>PQrQqS5rc3QaXQpht6pv6jecahh-pwk7X2Jfp4JhZW64UHeubxq7HA==</td></tr><tr><td align="right"><b>Connection</b></td><td>Keep-Alive</td></tr><tr><td align="right"><b>Via</b></td><td>2.0 bda01991f70d6041a75ac1d53fe4336a.cloudfront.net (CloudFront)</td></tr><tr><td align="right"><b>X-Forwarded-For</b></td><td>104.28.154.60</td></tr><tr><td align="right"><b>Accept-Encoding</b></td><td>gzip</td></tr><tr><td align="right"><b>upgrade-insecure-requests</b></td><td>1</td></tr><tr><td align="right"><b>sec-ch-ua</b></td><td>"Google Chrome";v="126", "Not:A-Brand";v="8", "Chromium";v="119"</td></tr><tr><td align="right"><b>sec-ch-ua-platform</b></td><td>Win32</td></tr><tr><td align="right"><b>sec-fetch-site</b></td><td>none</td></tr><tr><td align="right"><b>sec-fetch-mode</b></td><td>navigate</td></tr><tr><td align="right"><b>sec-fetch-user</b></td><td>?1</td></tr><tr><td align="right"><b>sec-fetch-dest</b></td><td>document</td></tr><tr><td align="right"><b>cf-biso-devtools</b></td><td>1</td></tr><tr><td align="right"><b>cf-biso-request-id</b></td><td>e6a5a65e-71eb-4a37-80fe-3c531ba285a8</td></tr>
</tbody></table>
<p style="margin-top:1em">
<b>Date:</b> Monday 23 Sep 2024 12:09:40 GMT+1000</p>
<p><b>Please Note:</b> The conclusion that the request came via a proxy is based on the presence of at least one of the <b>Via</b>, <b>Forwarded</b>, <b>X-Forwarded-For</b> or <b>Client-ip</b> headers.
(see
<a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.45">rfc2616</a> &
<a href="http://www.ics.uci.edu/pub/ietf/http/history/draft-ietf-http-v10-spec-01.html">draft-ietf-http-v10-spec-01</a> &
<a href="http://squid.visolve.com/">Squid Configuration Guide</a> &
<a href="http://www.linofee.org/~elkner/proxy/Squid/rel-notes-1_1.html#x">Squid Release Notes 1.1</a>)
</p>
<div style="font-size:smaller; margin-top:3em">
<p>Update 08 Feb 2002 by Lagado:
Added support for Client-ip header used by some transparent proxies.
See <a href="http://www.securiteam.com/securitynews/6W00X0035M.html">more background</a>.
</p>
<p>Update 30 Apr 2001 by Lagado:
Added <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9">Cache-Control: no-cache</a> header to proxy-test responses. This discourages HTTP/1.1 compliant proxies from returning cached test results. Also freshened the document references.
</p>
<p>Copyright © 2000 Lagado. First release 21 May 2000</p>
</div>
</div>
</div>
</body></html>