Port 4336RESTCONF Call Home over TLS

TLS-protected RESTCONF Call Home listener for controllers; managed devices initiate connections back to it.

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

also known as restconf-ch-tls

Technical Details

what runs on :4336

TCP 4336 is the controller-side listener for RESTCONF Call Home over TLS (RFC 8071). The managed RESTCONF server initiates the TCP connection and acts as the TLS client; after the TLS handshake, RESTCONF uses HTTP semantics as specified in RFC 8040, with the managed device still serving the RESTCONF API. This is distinct from the more usual arrangement where a client connects to a device's HTTPS RESTCONF endpoint, commonly on port 443. The port has no separate application framing beyond HTTP over TLS.

Security Information

exposure of :4336

risk score

3/ 10caution

worth attention. how exposed you are depends on configuration — don't leave it reachable from the internet without a reason.

web services averages 3.1 across 191 ports — this one sits 0.1 below.

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

TLS protects the connection, and deployments should authenticate the connecting device and validate credentials and certificates appropriately. This listener provides access to a network-management API, so restrict it to expected devices or management networks and keep RESTCONF authorization and TLS configuration current; do not expose it broadly just because it uses TLS.

Record

iana registry entry

port: :4336
service: RESTCONF Call Home over TLS
transport: TCP
encryption: tls / encrypted
assignment: iana registered
risk: 3/10caution
category: Web Services Network Services
usage: A management controller listens on TCP 4336 while a managed device initiates a connection back to it, as defined by RFC 8071. This is a specialized management setup rather than the usual RESTCONF-over-HTTPS endpoint, and the port is rarely seen open in internet-wide scans.
lookups: 0rank 993
added: 2026-10-04
updated: 2026-10-04
references: IANA service name registry — port 4336
RFC 8071

Something wrong?

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

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 191 in web services →

the 8 most looked-up other ports in web services — 191 ports carry that label.

port	service	proto	category	risk	views
:8888	Sun Answerbook & Alt HTTP	TCP	Web Services	caution	123.9k
:8000	Intel Remote Desktop / Alternate HTTP Port	TCP	Web Services	safe	84.3k
:8888	NewsEDGE	TCPUDP	Web Services	caution	83.3k
:8888	HTTP Alternative Port	TCP	Web Services	caution	76.5k
:8888	GNUmp3d Streaming HTTP	TCP	Web Services	caution	76.3k
:9080	Groove RPC	TCPUDP	Web Services	caution	70.8k
:8881	Atlasz Secure Server	TCP	Web Services	caution	67.6k
:80	HTTP	TCPUDP	Web Services	caution	67.3k

risk mix of the 8 listed

safe13%
caution88%

0 of 8 encrypted

Port :4336RESTCONF Call Home over TLS

Technical Details

Security Information

Related Ports

Port 4336RESTCONF Call Home over TLS