Port 6513NETCONF over TLS

TCP 6513 carries NETCONF network-device management sessions protected by TLS.

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

also known as netconf-tls

Technical Details

what runs on :6513

The client connects over TCP and establishes a TLS session before exchanging NETCONF XML messages. NETCONF then uses its hello and RPC message model, with message framing defined by the NETCONF-over-SSH framing specification (RFC 6242). TLS certificate authentication is used to identify the endpoints and support authorization. TCP 6513 is the TLS transport's assigned port; NETCONF over SSH is commonly associated with TCP 830.

Security Information

exposure of :6513

risk score

7/ 10risk

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

remote access averages 3.8 across 217 ports — this one sits 3.2 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

every listening transport is another surface to filter at the edge

security overview

A reachable NETCONF endpoint is a network-management interface: an authenticated user may be able to inspect or change device configuration, depending on authorization. TLS protects traffic in transit, but does not make the service safe to expose; restrict it to trusted management networks or VPNs, require strong certificate validation and authorization, and keep implementations current. Internet exposure is generally inappropriate.

Record

iana registry entry

port: :6513
service: NETCONF over TLS
transport: TCP
encryption: tls / encrypted
assignment: iana registered
risk: 7/10risk
category: Remote Access Network Services
usage: This is the IANA port for NETCONF over TLS, used to configure and monitor network devices through NETCONF operations. Engineers are more likely to encounter it on a management network than exposed to the internet; it has not appeared open in the cited nmap scan data.
lookups: 0rank 993
added: 2026-10-10
updated: 2026-10-10
references: IANA service name registry — port 6513
RFC 7589
RFC 9918

Something wrong?

This record is maintained by the engineers who use port 6513. 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-10-10.

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 217 in remote access →

the 8 most looked-up other ports in remote access — 217 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 :6513NETCONF over TLS

Technical Details

Security Information

Related Ports

Port 6513NETCONF over TLS