316
Summary
- // if you see it open
- No CVE, advisory, or vulnerability report references port 316 or decAuth. No verified software or daemon implements this service in any source found. Only low-authority aggregator sites mirror the bare IANA registry text. Risk profile is Unknown rather than characterized as high or low.
- // analyst note
- An open port 316 has no documented legitimate software behind it; treat as an unverified/legacy curiosity and investigate rather than assume benign.
About port 316/tcp.
Port 316/tcp is registered with IANA under the service name decauth ("decAuth"), but no confirmed software, protocol specification, or real-world deployment for it turned up in this research pass, so whether it belongs on the public internet cannot be answered with confidence — it should be treated as an obscure, effectively unused legacy registration rather than assumed either safe or unsafe to expose.
The IANA Service Name and Transport Protocol Port Number Registry lists 316 as dual-registered for both TCP and UDP, with identical rows: service name decauth, description "decAuth," and both the assignee and contact fields listed as [Michael_Agishtein]. No RFC or IANA reference is cited, and no assignment or modification date is recorded — unlike neighboring entries in the same file (for example ptp-event/319, which carries an explicit 2010-07-27 date), so the blank date here reads as a genuine registry gap rather than a fetch error.
The "dec" prefix in the service name, combined with the registrant era, suggests a possible lineage connected to Digital Equipment Corporation authentication tooling, but this is contextual inference from the name and registrant pattern rather than documented protocol behavior. One tangential hit surfaced: Clavister's firewall application-control signature documentation lists a "DEC Auth" application-control category, indicating at least one vendor built a traffic-classification signature referencing the name at some point — but that document does not confirm port 316 specifically or provide a date.
Port 316 is not covered by Wikipedia's "List of TCP and UDP port numbers" article, and no scanning, exposure-prevalence, honeypot, vulnerability, or CVE data for the port was found. The only web results are low-authority port-lookup aggregator sites that mirror the bare IANA registry entry with generic auto-generated boilerplate and add no verifiable fact.
- IANA assignment
decauth— "decAuth"; reference (blank — no RFC cited); assignee/contact[Michael_Agishtein]; dual-registered 316/tcp + 316/udp [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry-644; https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt- Range class
- well-known (0–1023) [Confirmed]
- Prevalence
- no scanning, telemetry, or honeypot data found; not covered by Wikipedia's List of TCP and UDP port numbers [Unknown] — https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers
- Related ports
- neighboring 1990s-era individually registered ports in the same registry block (dpsi/315, zannet/317, pkix-timestamp/318) [Confirmed — registry adjacency] — IANA registry
Primary use
no documented protocol specification or RFC exists beyond the two-word IANA description "decAuth"
Other/unofficial uses
possible Digital Equipment Corporation authentication lineage inferred from the "dec" name prefix and registrant-era pattern; one vendor (Clavister) lists a "DEC Auth" application-control signature category with no port-316 confirmation
Security implications
no CVE or advisory references port 316 or decAuth; no verified software implements it, so risk cannot be characterized beyond "obscure/effectively unused" [Unknown]
Typically seen on
no verified deployments identified; treat any observed instance as anomalous pending further investigation [Unknown]
- Analyst note
- An open port 316 has no documented legitimate software behind it; treat as an unverified/legacy curiosity and investigate rather than assume benign.
About port 316/udp.
Port 316/udp is registered with IANA under the service name decauth ("decAuth"), but no primary-source specification, RFC, or vendor documentation describing what the service actually does has been found, so whether it belongs on the public internet cannot be confirmed either way — treat it as an obscure, apparently unimplemented registration rather than a service to knowingly expose or block.
The IANA Service Name and Transport Protocol Port Number Registry lists 316/udp as decauth, description "decAuth," assignee Michael Agishtein. The entry carries no RFC or IANA reference, and no registration or modification date is recorded in the registry — these fields are blank in the source data, not omitted. Port 316/tcp carries an identical decauth/decAuth entry with the same assignee, confirming dual tcp/udp registration.
The name "decauth" suggests an authentication-related function, and the "dec" prefix plausibly echoes Digital Equipment Corporation-era networking software, but this is speculation: no vendor documentation, product, or open-source implementation naming this port has been located. Third-party port-lookup aggregators (adminsub.net, tcp-udp-ports.com, speedguide.net) only mirror the IANA name with no added technical detail.
Port 316 does not appear in Wikipedia's List of TCP and UDP port numbers, and no CVEs or scanning-campaign write-ups reference it in this research pass, suggesting low real-world notability — though absence of evidence is not evidence of absence. One aggregator, auditmypc.com, explicitly flags the port as not associated with any known virus or trojan.
- IANA assignment
decauth— "decAuth"; reference (blank — no RFC cited); assignee Michael Agishtein; dual-registered 316/tcp + 316/udp [Confirmed] — IANA Service Name and Transport Protocol Port Number Registry (https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?page=6)- Range class
- well-known (0–1023) [Confirmed]
- Prevalence
- Unknown — no nmap-services or scanning-prevalence data found in this pass [Unknown]
- Related ports
- 316/tcp (identical decauth/decAuth dual registration) [Confirmed] — IANA registry
Primary use
Unknown — no primary-source spec, RFC, or vendor documentation found describing the actual protocol; the name implies an authentication-related function, possibly historically tied to DEC networking software [Unknown]
Other/unofficial uses
Unknown — no vendor product or open-source implementation found using this port [Unknown] — https://www.adminsub.net/tcp-udp-port-finder/316, https://tcp-udp-ports.com/port-316.htm, https://www.speedguide.net/port.php?port=316 (aggregators only mirror the IANA name)
Security implications
no CVEs or scanning-campaign write-ups found; not listed in Wikipedia's List of TCP and UDP port numbers; one aggregator reports no virus/trojan association
Typically seen on
Unknown — no documented deployments found [Unknown]
- Analyst note
- An open 316/udp is atypical given its near-total absence from mainstream documentation; treat as worth investigating rather than assuming routine/benign.
Service assignments.
| Name | Protocol | Description | Open frequency |
|---|---|---|---|
| decauth | UDP | — | 0.05% |
| decauth | TCP | — | 0.00% |
Service assignments from the IANA Service Name and Transport Protocol Port Number Registry, with open-frequency data from nmap-services.