Port 32774FileNET Rules Engine

Port 32774 is assigned to the FileNET Rules Engine on TCP and UDP.

transport: tcp · udp
in transit: cleartext
assignment: official
risk: 1/10
lookups: 0

also known as filenet-re

Technical Details

what runs on :32774

FileNET Rules Engine is registered on port :32774 over tcp and udp to Chris Adkins, assigned August 2003. We don't have a technical write-up for it beyond the IANA registry entry.

In nmap's internet-wide scan data this port is never observed open, so if it's open on your network it's more likely a custom or misconfigured service than the registered one.

find what's listening on :32774

this machine

# linux
sudo ss -tulpn 'sport = :32774'

# macos / bsd
sudo lsof -nP -i :32774

# windows (then: tasklist /FI "PID eq <pid>")
netstat -ano | findstr :32774

another host

nmap -sV -p T:32774 <host>
sudo nmap -sU -sV -p U:32774 <host>

run it? the handshake, the implementations you meet in the wild and the flags that matter come from the engineers who do.

add technical details

Security Information

exposure of :32774

risk score

1/ 10safe

routine exposure. this port is rarely the way in on its own — keep it patched and logged and move on.

in transit

cleartext

credentials and payloads are readable by anyone on path

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

no security notes recorded for :32774 yet

known exploits, hardening advice, what a compromise looks like — suggest an edit if you know its exposure.

Record

iana registry entry

port: :32774
service: FileNET Rules Engine
transport: TCPUDP
encryption: cleartext
assignment: iana registered
risk: 1/10safe
category: uncategorised
usage: IANA assigns TCP and UDP port 32774 to the FileNET Rules Engine, registered by Chris Adkins. Its actual protocol behavior and deployment are not established here.
lookups: 0rank 993
added: 2026-10-20
updated: 2026-10-20
references: IANA service name registry — port 32774

Something wrong?

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

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

browse categories →

ports registered around :32774, by lookups.

port	service	proto	category	risk	views
:32769	FileNet RPC	TCP	File Transfer	caution	9.5k
:32768	FileNet TMS	TCPUDP	—	safe	0
:32767	FileNet BPM WS-ReliableMessaging Client	TCPUDP	Web Services	safe	0
:32770	FileNet NCH	TCPUDP	Network Services	safe	0
:32771	FileNET RMI	TCPUDP	—	safe	0
:32772	FileNET Process Analyzer	TCPUDP	—	safe	0
:32773	FileNET Component Manager	TCPUDP	Network Services	safe	0
:32775	Performance Clearinghouse	TCPUDP	Network Services	safe	0

risk mix of the 8 listed

safe88%
caution13%

0 of 8 encrypted

Port :32774FileNET Rules Engine

Technical Details

Security Information

Related Ports

Port 32774FileNET Rules Engine