Port 3316AICC Computer-Managed Instruction (CMI)

Registered for AICC/CMI courseware communication, which typically uses an LMS's HTTP(S) endpoint rather than a dedicated port 3316 listener.

transport
tcp · udp

2 transports registered

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
2/10

safe

lookups
0

rank 993 of 4,625 · top 21%

also known as aicc-cmi, AICC HACP, Computer-Managed Instruction

Technical Details

what runs on :3316

Port 3316 is registered for AICC/CMI. AICC HACP exchanges course and learner data using HTTP requests and responses, commonly with courseware sending data to an LMS endpoint; deployments generally use the LMS's web service on HTTP or HTTPS ports such as 80 or 443 rather than a dedicated listener on 3316. The registration lists both TCP and UDP, but HTTP-based HACP uses TCP; the UDP listing does not establish a normal AICC/CMI UDP protocol or a particular handshake or framing on that transport.

Security Information

exposure of :3316

risk score

2/ 10safe

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

web services averages 3.2 across 184 ports — this one sits 1.2 below.

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

AICC exchanges can contain learner identifiers, session state, and course progress. Plain HTTP does not protect those contents in transit, so use HTTPS where available; as with other LMS endpoints, restrict access and keep the LMS software current. A port-3316 listener is uncommon, and an open port alone does not confirm that it is AICC/CMI.

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

risk mix of the 8 listed

  • safe13%
  • caution88%

0 of 8 encrypted