>

Test Ports With Test-NetConnection

Check connectivity, DNS resolution and a specific TCP port with one cmdlet.

WindowsnetworkpowershellDiagnosticsLow risk
Run Test-NetConnection example.com -Port 443 to test DNS, ping and TCP reachability.

01Command

Command
$ Test-NetConnection example.com -Port 443

02What it does

The cmdlet returns a structured object with DNS resolution results, ping replies and TCP test results, so a script can branch on connectivity without parsing text. That makes it the natural building block for health checks and preflight validation on Windows.

03Risk

RiskLow risk
RequirementsWindows 10/11 with PowerShell 5.1 or PowerShell 7+
!Warning: TCP tests are blocked in some networks and ICMP may be disabled; interpret failures with the other fields, not in isolation.

04Undo

✓No undo needed — this command does not change persistent state.

05Sources

  • Test-NetConnection
    Microsoft Learn · vendor-doc · 2026-09-20
    Evidence: Tests network connectivity and TCP port reachability.

Last verified: 2026-10-13 · Category: Network

06Related solutions

Reset the Windows network stack with netsh
WindowsnetworksystemDiagnostics

The nuclear option for broken connectivity: rebuild Winsock and the TCP/IP stack to defaults when adapters show 'no internet' despite everything else working.

Medium risk ✓ 2026-09-17
Test a TCP port connection on Windows with Test-NetConnection
Windowsnetworktroubleshootingpowershell

A built-in PowerShell one-liner that answers 'is port 5432/3389/443 actually open through this network?' — no telnet client needed.

Low risk ✓ 2026-09-17
Read Deep Hardware Details with Get-ComputerInfo
WindowshardwarepowershellDiagnostics

PowerShell cmdlet that exposes BIOS, firmware, RAM and OS properties as a filterable object.

Low risk ✓ 2026-09-17