Check Connectivity to Agent Server

Purpose

This document describes how to check if the Agent has contact with the Agent server.

Introduction

Agents must maintain network connectivity with the Agent Server to enroll, receive scanning schedules, send results, and fetch updates. The Check Connectivity to Agent Server feature guides administrators in verifying this connection by testing if the agent-host can reach the Agent Server over its HTTPS port (typically 443). Ensuring this link works properly is critical to avoid failures in remote assessments, missed data synchronization, or degraded visibility into asset security.

Checking Connectivity

For the Agent to work properly, it has to have access to teddysalad.outpost24.com and appliancek8s.outpost24.com.

To ensure that you can reach Outpost24 Agent server, check that the following URLs are reachable from the target where the Agent is installed:

From a Browser

You can use any browser to access https://appliancek8s.outpost24.com and https://teddysalad.outpost24.com to check for connectivity.

From Command Line

In the case you do not have access to a graphical interface the following command line methods can also be applied.

Windows

Run the following command in a PowerShell prompt (Windows):

Test-NetConnection -ComputerName teddysalad.outpost24.com -Port 443
Test-NetConnection -ComputerName appliancek8s.outpost24.com -Port 443

Example:

PS C:\Users\jdoe> Test-NetConnection -ComputerName appliancek8s.outpost24.com -Port 443

ComputerName     : appliancek8s.outpost24.com
RemoteAddress    : 80.254.228.250
RemotePort       : 443
InterfaceAlias   : Ethernet
SourceAddress    : 203.0.113.82
TcpTestSucceeded : True


PS C:\Users\jdoe>

A failed connection would look like this:

PS C:\Users\jdoe> Test-NetConnection -ComputerName appliancek8s.outpost24.com -Port 443
WARNING: Name resolution of appliancek8s.outpost24.com failed


ComputerName   : appliancek8s.outpost24.com
RemoteAddress  :
InterfaceAlias :
SourceAddress  :
PingSucceeded  : False

Linux

Run the following command in a console (Linux):

curl -I teddysalad.outpost24.com 443
curl -I appliancek8s.outpost24.com 443

Example

$ curl -I https://appliancek8s.outpost24.com 443
HTTP/1.1 404 Not Found
Server: nginx/1.29.1
Date: Wed, 10 Sep 2025 09:36:59 GMT
Content-Type: text/html
Content-Length: 153
Connection: keep-alive
$

A failed connection would result in:

$ curl -I https://cumulus.example.com
curl: (6) Could not resolve host: cumulus.example.com; Unknown error
$

Telnet

Telnet can still be used in those cases it is available. Note that later versions of Windows do not support telnet.

telnet teddysalad.outpost24.com 443
telnet appliancek8s.outpost24.com 443

Example

$ telnet teddysalad.outpost24.com 443
Trying 80.254.228.14 ...
Connected to teddy salad.outpost24.com.
Escape character is '^]'.
^CConnection closed by foreign host.
$

A failed connection could look like this:

Host resolves, but no service is listening on the port (connection refused)

telnet: Unable to connect to remote host: Connection refused

Timeout due to network issues

telnet: connect to address 80.254.228.14: Connection timed out

Firewall blocks the connection or the host is unreachable

telnet: Unable to connect to remote host: No route to host

Host cannot be resolved (DNS failure)

telnet: could not resolve telnet teddysalad.outpost24.com/443: Name or service not known

_Copyright

_{© 2025 Outpost24® All rights reserved. This document may only be redistributed unedited and unaltered. This document may be cited and referenced only if clearly crediting Outpost24® and this document as the source. Any other reproduction and redistribution in print or electronically is strictly prohibited without explicit permission.}

_Trademark

_{Outpost24® and OUTSCAN™ are trademarks of Outpost24® and its affiliated companies. All other brand names, product names or trademarks belong to their respective owners.}