460

Port 460/tcp is registered with IANA under the name skronk, but no documented protocol, software, or functional description exists for it anywhere in the sources reviewed, so there is no basis to call it safe for public internet exposure — it should be treated as internal-only or investigated, not assumed benign, until its purpose is identified.

IANA registers 460 as skronk on both TCP and UDP, with assignee Henry_Strickland and blank Reference and Registration Date fields; the IANA Description column literally reads "skronk," with no elaboration of what the service does.

SANS Internet Storm Center's port-460 lookup page corroborates the same name but likewise offers no functional description. Targeted searches across game-client, P2P, vendor, and forum documentation for software actually using port 460 returned only port-directory mirrors of the IANA name, so no application attribution can be made for this port.

Observed activity on the port is consistent with routine internet background noise rather than anything specific: SANS ISC's live scanner data for port 460 shows only low-volume probing from scattered source IPs, with the overall threat level shown as "green" (no elevated alert) at the time of checking.

The nmap-services corpus records this port as essentially never seen open: 460/tcp has an open-frequency of roughly 0.0013%, and the paired 460/udp roughly 0.061% — both negligible, consistent with an obscure, rarely-if-ever-deployed legacy registration rather than an active service.

IANA assignment

skronk — "skronk"; reference (blank — no RFC cited); assignee Henry_Strickland; dual-registered 460/tcp + 460/udp [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry skronk 460/tcp and 460/udp

Range class

well-known/system (0-1023) [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry

Prevalence

nmap-services open-frequency 460/tcp ≈ 0.000013 (~0.0013%); 460/udp ≈ 0.00061 (~0.061%), both negligible [Confirmed] — this site's own tooling (built from nmap-services)

Related ports

none identified as a paired or companion service for skronk [Unknown]

Primary use

Unknown/undocumented — no functional description of the skronk protocol was found in the IANA registry or any secondary source

Other/unofficial uses

none identified — no vendor docs, blog posts, or forum/game-client threads attribute any software to this port; searches surfaced only port-directory mirrors of the IANA name

Security implications

no CVE or named malware family documented for 460/tcp as of an August 2026 search; SANS ISC records only generic, green-level background-scan traffic, not application- or campaign-specific activity; a generic "flagged" verdict page could not be verified with real content and is not cited as evidence

Typically seen on

no known deployment pattern identified; treat a responsive host as an anomaly warranting investigation [Unknown]

Analyst note

skronk is a sparsely-documented legacy IANA registration with no published protocol or software behind it — an open 460/tcp cannot be assumed routine; investigate rather than assume benign traffic.

Port 460/udp carries skronk, an IANA-registered service name with no documented protocol specification or known software behind it; whether it belongs on the public internet is Unknown rather than something this entry will guess at.

IANA registers 460 on both TCP and UDP under the service name skronk, description "skronk" (i.e. no functional description beyond the name itself), assignee/contact Henry Strickland. The Reference column is blank (no RFC cited) and no registration or modification date is recorded in the registry.

The name "skronk" is not tied to any documented product, RFC, or protocol specification found in this research. The only community trace found is a 2005 Kalamazoo Linux Users Group (KLUG) mailing-list post titled "skronk - port 460?" in which a user asks what generates traffic on the port and reports being unable to find an answer — an unresolved question, not a confirmed sighting of any application.

Generic port-lookup aggregators (SpeedGuide, t1shopper, adminsub.net, jamesbrine.com.au) mirror only the bare IANA name and assignee and add no independent application attribution. No CVE or named malware family is documented against 460/udp specifically, and AuditMyPC's port-460 pages could not be fetched with usable content in this search, so no malware verdict, positive or negative, is drawn from that source.

IANA assignment

skronk — "skronk"; reference (blank — no RFC cited); assignee Henry_Strickland; dual-registered 460/tcp + 460/udp [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry skronk 460/udp; cross-checked https://www.iana.org/assignments/service-names-port-numbers

Range class

well-known (0–1023) [Confirmed]

Prevalence

nmap-services open-frequency 460/udp = 0.00061 (~0.061%); 460/tcp = 0.000013 (~0.0013%) [Confirmed] — this site's own tooling (built from nmap-services)

Related ports

none confirmed as a paired/companion assignment

Primary use

no documented protocol specification beyond the IANA name "skronk"; functional purpose Unknown

Other/unofficial uses

none confirmed; one 2005 KLUG mailing-list post asks what generates traffic on the port without resolution

Security implications

no CVE or named malware family documented for 460/udp as of an August 2026 search; AuditMyPC's port-460 pages did not return usable content, so no malware verdict is drawn from that source

Typically seen on

Unknown — no current software is attributed to this port in the research found [Unknown]

Analyst note

skronk is a bare, undocumented IANA name-only assignment with no known deployment; an open 460/udp is unusual and worth investigating rather than assuming routine traffic.