486
Summary
- // typical exposure
- Anomalous (rarely legitimately open) — The IANA registration has no protocol specification and open-frequency is near zero (486/tcp ~0.000025 per nmap-services), so a responsive 486/tcp has no known legitimate deployment and should be treated as anomalous rather than expected traffic.
- // analyst note
- An open 486/tcp has no documented legitimate use and near-zero observed prevalence — treat it as anomalous and worth investigating rather than routine.
- // if you see it open
- No CVE or malware association is recorded for port 486 as of an August 2026 search; SANS ISC shows a low/green threat indicator with no linked advisory. The protocol behind 'avian' is undocumented (blank IANA Reference), and open-frequency is near zero, so a responsive 486/tcp is anomalous rather than expected and warrants investigation.
About port 486/tcp.
Port 486/tcp is IANA-registered under the service name "avian," but the registry publishes no protocol description, no RFC, and no reference document, so there is no known legitimate service to expose; it should not be opened to the public internet, and a responsive 486/tcp is better treated as anomalous than as expected traffic.
IANA's Service Name and Transport Protocol Port Number Registry lists "avian" as dual-registered on both 486/tcp and 486/udp, with assignee contact "[Robert_Ullmann_2]" and a blank Reference column — no RFC or spec is cited, and no registration or modification date is populated in the published data.
The repo's own nmap-services derived dataset shows a naming quirk worth flagging: the 486/udp row is labeled "avian" (open-frequency ≈0.000379), while the 486/tcp row is labeled "sstats" with description field "avian" (open-frequency ≈0.000025, roughly 0.0025% of scanned hosts). SANS ISC's port page independently lists both names against this port, corroborating the split.
No CVE is recorded against port 486 in the sources checked, and SANS Internet Storm Center shows a low/green threat indicator with no linked advisory as of an August 2026 check. No independent write-up of what the "avian" protocol actually does, and no community-sourced report of real software using 486/tcp, was found in this pass.
- IANA assignment
avian— dual-registered 486/tcp + 486/udp; assignee[Robert_Ullmann_2]; Reference column blank [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry avian 486/tcp- Range class
- well-known / IANA "System Ports" (0–1023) [Confirmed] — port number is self-evidently in this range
- Prevalence
- nmap-services open-frequency for 486/tcp ("sstats") ≈0.000025 (~0.0025%); 486/udp ("avian") ≈0.000379 [Confirmed] — this site's own tooling
- Related ports
- 486/udp (same IANA "avian" dual registration) [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry avian 486/udp
Primary use
undocumented — no protocol description, RFC, or reference is published for "avian"
Other/unofficial uses
nmap-services labels the 486/tcp row "sstats" (description "avian"), distinct from the "avian" name used for 486/udp
Security implications
no CVE or malware association found as of an August 2026 search; SANS ISC shows a low/green threat indicator
Typically seen on
no known legitimate deployment identified in this pass [Unknown]
- Analyst note
- An open 486/tcp has no documented legitimate use and near-zero observed prevalence — treat it as anomalous and worth investigating rather than routine.
About port 486/udp.
Port 486/udp carries the IANA-registered service name "avian"; no protocol specification, vendor implementation, or real-world sighting has surfaced, so an open 486/udp should be treated as anomalous rather than expected on any network, public or internal.
The port sits in IANA's System Port range (0–1023) and is registered to service name avian with assignee code [Robert_Ullmann_2] and a blank Reference column — the registry cites no RFC or other defining document. The same name, avian, is also registered on 486/tcp.
Beyond the bare registry entry, nothing describes what the protocol actually does. No RFC, IETF draft, vendor manual, or forum/blog post naming a piece of software that uses 486/udp turned up in an August 2026 search pass; the name itself is undocumented and should not be assumed to reference any specific product or standard.
Observed prevalence is negligible. The repo's port-data corpus (built from nmap-services) records an open-frequency of 0.000379 for 486/udp — essentially never seen open in scan telemetry. The 486/tcp row in that same corpus is separately labeled "sstats" (frequency 0.000025) while carrying "avian" as its description, a naming mismatch between the nmap-services and IANA datasets rather than evidence of two distinct services.
- IANA assignment
avian— description "avian"; Reference column blank; assignee[Robert_Ullmann_2]; also registered on 486/tcp [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry avian 486/udp- Range class
- System Port (0–1023) [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry avian 486/udp
- Prevalence
- nmap-services open-frequency 486/udp = 0.000379 (~0.038%); 486/tcp appears in the same corpus as "sstats" (freq 0.000025) with description "avian" — a dataset naming discrepancy, not two services [Confirmed] — this site's own tooling
- Related ports
- 486/tcp (same IANA name
avian; nmap-services corpus labels it "sstats") [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry avian 486/tcp
Primary use
Unknown — no protocol specification, RFC, or vendor document describing "avian" was found
Other/unofficial uses
none found as of an August 2026 search
Security implications
SANS ISC shows green/low threat level, no CVE, no populated scan counts as of an Aug 2026 search; no malware/trojan association verified
Typically seen on
Unknown — no confirmed real-world deployment surfaced [Unknown]
- Analyst note
- near-zero observed prevalence combined with an undocumented protocol make an open 486/udp worth flagging as anomalous and investigating rather than assuming legitimate use.
Service assignments.
| Name | Protocol | Description | Open frequency |
|---|---|---|---|
| avian | UDP | — | 0.04% |
| sstats | TCP | avian | 0.00% |
Service assignments from the IANA Service Name and Transport Protocol Port Number Registry, with open-frequency data from nmap-services.