> For the complete documentation index, see [llms.txt](https://www.osdeploy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.osdeploy.com/command-reference/osd/test-webconnection.md).

# Test-WebConnection

Tests web connectivity to a target URI using a live TCP connection and HTTP HEAD request.

| Property | Value                 |
| -------- | --------------------- |
| Module   | OSD                   |
| Platform | WinPE (amd64 / arm64) |

## Description

Opens a live TCP connection and sends HTTP HEAD requests to the specified URI, returning $true when the request succeeds and $false otherwise. If a URI is provided without a scheme, both https\:// and http\:// are tested.

## Syntax

```powershell
Test-WebConnection [[-Uri] <Uri>] [-ProgressAction <ActionPreference>] [<CommonParameters>]
```

## Parameters

| Parameter | Type  | Required | Description                                          |
| --------- | ----- | -------- | ---------------------------------------------------- |
| `-Uri`    | `Uri` | False    | URI to test. Values from the pipeline are supported. |

## Examples

### Example

```powershell
Test-WebConnection -Uri 'http://example.com'
Returns $true when the target responds to an HTTP HEAD request.
```

### Example

```powershell
'google.com' | Test-WebConnection
Tests a bare URI supplied from the pipeline by checking both HTTPS and HTTP.
```

## Related

* <https://github.com/OSDeploy/OSD/tree/master/docs>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.osdeploy.com/command-reference/osd/test-webconnection.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
