A DDoS attack can overwhelm a Windows server or its network connection with unwanted traffic. Connection checks and monitoring can help investigate a suspected attack, but they need to be compared with the server’s normal workload.

Check traffic and service health

Review the provider’s bandwidth graphs, application logs and Windows performance monitoring. Record when the problem started and which services are affected. High CPU usage or a slow website can also result from an application fault or legitimate demand.

Inspect TCP connections

Open PowerShell on the server with permission to inspect its connections. For a website using ports 80 and 443, run:

Get-NetTCPConnection -LocalPort 80,443 |
    Select-Object LocalAddress,LocalPort,RemoteAddress,RemotePort,State

To group established connections by remote address:

Get-NetTCPConnection -LocalPort 80,443 -State Established |
    Group-Object RemoteAddress |
    Sort-Object Count -Descending |
    Select-Object Count,Name

These are snapshots. Replace the port list if the affected service uses other ports. You can also run netstat -ano in Command Prompt to see connection endpoints and process IDs.

Decide what the evidence means

Large connection counts do not prove an attack. A proxy or CDN can represent many legitimate visitors through the same address, and TCP checks do not show every kind of network traffic.

If service is disrupted or the connection is saturated, contact your provider with the time, affected address and monitoring evidence. Do not automatically block addresses or stop services solely because a count is high.