Port 830NETCONF over SSH

Encrypted SSH transport for NETCONF network-device management, normally listening on TCP port 830.

transport: tcp · udp
in transit: encrypted
assignment: official
risk: 7/10
lookups: 0

also known as netconf-ssh, NETCONF subsystem, TCP 830

Technical Details

what runs on :830

NETCONF over SSH uses an SSH connection, conventionally on TCP port 830, with the NETCONF subsystem requested after SSH authentication. The client and server exchange XML <hello> messages containing capabilities, then exchange NETCONF RPCs and replies. NETCONF 1.0 uses the ]]>]]> end-of-message delimiter, while NETCONF 1.1 uses chunked framing as defined by RFC 6242. UDP is not a normal transport for SSH-based NETCONF.

Security Information

exposure of :830

risk score

7/ 10risk

treat as sensitive. widely scanned and regularly exploited when reachable — restrict it to known sources.

remote access averages 3.7 across 174 ports — this one sits 3.3 above.

in transit

encrypted

payloads are protected on the wire

assignment

official

registered with iana for this service — scanners fingerprint it by number

reachable over

tcp · udp

udp is connectionless — source addresses are trivially spoofed and it is a reflection favourite

security overview

The SSH transport encrypts and authenticates the session, but NETCONF provides powerful remote configuration and operational access to network infrastructure. Internet exposure is generally inappropriate: restrict port 830 to trusted management networks or VPNs, enforce strong SSH authentication and authorization, and monitor for password guessing, credential attacks, and unauthorized configuration changes.

Record

iana registry entry

port: :830
service: NETCONF over SSH
transport: TCPUDP
encryption: tls / encrypted
assignment: iana registered
risk: 7/10risk
category: Remote Access Network Services
usage: Network devices and controllers expose NETCONF over SSH on TCP port 830 for authenticated configuration, state retrieval, and operational management. Clients connect using SSH and request the NETCONF subsystem; although IANA lists both TCP and UDP, SSH-based NETCONF is normally TCP-only.
lookups: 0rank 994
added: 2026-09-15
updated: 2026-09-15
references: IANA service name registry — port 830
RFC 6242

Something wrong?

This record is maintained by the engineers who use port 830. Every field on it is editable — change what's wrong, say how you know, and a reviewer publishes it, usually within a minute. Last touched 2026-09-15.

01edit any field on a page of its own
02a model checks it for accuracy and spam
03clean and confident goes live immediately

edit this record →back to the registry

Related Ports

all 174 in remote access →

the 8 most looked-up other ports in remote access — 174 ports carry that label.

port	service	proto	category	risk	views
:8000	Intel Remote Desktop / Alternate HTTP Port	TCP	Web Services	safe	84.3k
:8888	D2GS Admin Console	TCP	Remote Access	caution	83.7k
:8881	Atlasz Secure Server	TCP	Web Services	caution	67.6k
:5938	TeamViewer	TCPUDP	Remote Access	caution	65.0k
:8291	Winbox MikroTik Admin	TCP	Security	caution	62.9k
:8008	IBM HTTP Server Admin	TCP	Web Services	caution	58.3k
:135	Microsoft EPMAP	TCPUDP	Security	caution	51.9k
:23	Telnet	TCP	Remote Access	caution	34.8k

risk mix of the 8 listed

safe13%
caution88%

0 of 8 encrypted

Port :830NETCONF over SSH

Technical Details

Security Information

Related Ports

Port 830NETCONF over SSH