<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: List of Default Ports

Here you can find lists for all default ports used in PRTG:

Ports Used by Sensors

Sensors	Default Port Numbers	Description
Cloud HTTP and Cloud Ping	443	Port for the communication via the PRTG Cloud
Cloud Ping	80	Port for the TCP ping
Dell EMC	443	Port for the connection to the Dell EMC system
DICOM	104	Port for the connection to the DICOM interface
DNS v2	53	Port for the connection to the device that runs the DNS service
Docker Container Status	2376 (Docker over TLS)	Port for the connection to the Docker container
FortiGate	443	Port for the connection to the FortiGate system
FTP	21	Port for the connection to the file server
HL7	104	Port for the connection to the HL7 interface
HPE 3PAR	WSAPI port: 8080 (secure) 8008 (unsecure) SSH port: 22 (secure)	WSAPI and SSH port for the connections to the HPE 3PAR system
HTTP	8080	Port of the proxy
HTTP IoT Push Data Advanced	5051	Port on which the sensor listens for incoming HTTPS requests This port is fixed. You cannot change it.
HTTP Push	5051 (secure) 5050 (unsecure)	Port on which the sensor listens for incoming HTTP or HTTPS requests
IMAP	993 (secure) 143 (unsecure)	Port for the IMAP connection
LDAP	636 (secure) 389 (unsecure)	Port for the connection to the LDAP server
NetApp	443	Port for the NetApp API access
Microsoft SQL v2	1433	Port for the connection to the Microsoft SQL database
MySQL v2	3306	Port for the connection to the MySQL database
Modbus TCP Custom	502	Port for the connection to the Modbus TCP server
MQTT	8883 (secure) 1883 (unsecure)	Port for the MQTT connection
OPC UA	4840	Port for the connection to the OPC UA server
Oracle	1521	Port for the connection to the Oracle SQL database
POP3	995 (secure) 110 (unsecure)	Port for the POP3 connection
Port v2	443	Port for the TCP connection
PostgreSQL	5432	Port for the connection to the PostgreSQL database
QoS	50000	Port on which the sensor listens for the UDP packets
RADIUS v2	1812	Port for the connection to the RADIUS server
RDP (Remote Desktop)	3389	Port for the RDP connection
Redfish	443	Port for the Redfish connection
REST	8080	Port for the proxy
SIP Options Ping	5060	Port for the UDP connection
SMTP	465 or 587 (secure) 25 (unsecure)	Port used to send an email via SMTP
SMTP&IMAP Round Trip	993 (secure) 143 (unsecure)	Port for the IMAP connection
SMTP&POP3 Round Trip	995 (secure) 110 (unsecure)	Port for the POP3 connection
SNMP	161	Port for the SNMP connection
SNMP Trap Receiver	162	Port on which the sensor listens for SNMP traps and on which trap messages are sent
Soffico Orchestra Channel Health	8443 (secure) 8019 (unsecure)	Port for the connection to the Orchestra platform
SSH	22	Port for the connection via SSH
SSL	443	Port for the Secure Sockets Layer (SSL)/Transport Layer Security (TLS) connection
Syslog Receiver	514	Port on which the sensor listens for Syslog messages and on which Syslog messages are sent
TFTP	69	Port of the device on which the TFTP service runs
Veeam Backup Job Status	9398	Port for the connection to the Veeam Backup Enterprise Manager
VMware (SOAP)	443	Port for the VMware (SOAP) connection
WBEM	5988 (unsecure) 5989 (secure)	Port for the communication via WBEM
Windows Updates Status (PowerShell)	5985	Port for the connection to Microsoft or to the local WSUS server
WSUS Statistics	8530	Port for the connection to the device on which the WSUS server service runs

Ports Used in Other Contexts

Context	Default Port Numbers	Description
Active Directory integration	389 (unsecure) 636 (secure)	The LDAP port for Active Directory integration
Auto-update and activation	443	Port for auto-update and activation For more information, see the Knowledge Base: Which servers does PRTG connect to for software auto-update, activation, etc.?
Cluster communication	23570	Port for the communication between cluster nodes
Incoming probe connections	23560	Port on which PRTG listens for incoming remote probe connections
Notifications	443 (push) 25 (SMTP) 162 (SNMP trap) 514 (Syslog)	Port for the notifications The target URL for push is https://api.prtgcloud.com:443.
PRTG application server and PRTG core server	23580	Port for the connections between the PRTG application server and the PRTG core server
PRTG Cloud	443	Port used by the PRTG Cloud for support tickets, for example
PRTG web server	443 (secure) 80 (unsecure) Fallbacks: 8443 and 8443+ (secure) 8080+ (unsecure)	Port used by the PRTG web server PRTG app for desktop, PRTG MultiBoard, and the PRTG mobile apps also use this port to connect to the PRTG web server.
Remote probes and PRTG core server	23560	Port for the connections between remote probes and the PRTG core server It is sufficient to open or forward this TCP port only on the PRTG core server. If you need to change it, see the Knowledge Base: How can I customize ports for core-probe connections used by PRTG?
Report generation	8085 (PDF)	Port for the report generation
Update check and download	80	Port for the update check and download For more information, see the Knowledge Base: Which servers does PRTG connect to for software auto-update, activation, etc.?