284
Summary
- // if you see it open
- No confirmed malware or trojan association. One low-authority port-lookup aggregator (auditmypc.com) marks TCP port 284 as having no known virus/trojan entries, but this is a hobbyist database, not a security vendor or CERT source, so it is weak corroboration only, not clearance. No IDS/IPS signatures or live-scanning data were reviewed. Because the underlying protocol is undocumented, an active listener on this port cannot be confirmed benign and should be investigated.
- // analyst note
- Sparse legacy IANA registration with no corroborating protocol documentation; treat an open 284/tcp or 284/udp as unexplained until the responding service is identified.
About port 284/tcp.
Port 284/tcp (and its paired 284/udp registration) carries a service IANA lists only as corerjd; no public specification, RFC, or vendor documentation describes what the protocol actually does, so it should not be treated as an internet-facing service and any live listener merits investigation rather than assumption.
IANA's Service Name and Transport Protocol Port Number Registry confirms the bare facts: service name corerjd, dual-registered on TCP and UDP, assignee and contact Chris Thornhill, and a blank Reference column — meaning no RFC backs the entry. No registration or modification date is published for this entry, and none is invented here.
Beyond the registry listing, this pass found no mainstream application, daemon, or product documented as defaulting to port 284, and no primary source describing the corerjd protocol's purpose. One low-authority port-lookup aggregator (auditmypc.com) notes no known virus/trojan association, but that is weak corroboration from a hobbyist database, not a security vendor or CERT finding — treat it as a mild negative signal, not clearance.
- IANA assignment
corerjd— description field contains only the literal string "corerjd"; reference (blank — no RFC cited); assignee/contact Chris Thornhill; dual-registered 284/tcp + 284/udp [Confirmed] — IANA Service Name and Transport Protocol Port Number Registry- Range class
- well-known (0–1023)
- Prevalence
- Not assessed in this pass (no SANS ISC/Shodan/Censys data pulled) [Unknown]
- Related ports
- none identified
Primary use
Unknown — no public specification, RFC, or vendor documentation found describing the corerjd protocol [Unknown]
Other/unofficial uses
None identified in this pass [Unknown]
Security implications
no confirmed malware/trojan association; one low-authority aggregator (auditmypc.com) reports no known virus/trojan tie for 284/tcp, but this is weak, non-primary corroboration
Typically seen on
Unknown — no software or platform documented as using this port by default
- Analyst note
- Sparse legacy IANA registration with no corroborating protocol documentation; treat an open 284/tcp or 284/udp as unexplained until the responding service is identified.
About port 284/udp.
Port 284/udp has no confirmed function and no verified reason to be reachable from the public internet. IANA registers it under the bare service name corerjd (registrant Chris Thornhill), but publishes no RFC, no protocol description, and no assignment date beyond that name — so what actually listens here, if anything, is Unknown.
The registry entry (the IANA Service Name and Transport Protocol Port Number Registry, line 617) shows a matching 284/tcp row under the same name, confirming dual tcp/udp registration, but the Description field simply repeats "corerjd" rather than explaining it. Registration date, modification date, IANA reference, and assignment notes are all blank in the source — reported here as null, not invented.
Independent web research turned up no RFC, vendor specification, or software product that implements a "corerjd" service, and no credible evidence of scanning or exploitation activity tied to port 284/udp. Several aggregator sites (SpeedGuide, T1 Shopper, ports.my-addr.com, AdminSub) only mirror the same bare IANA entry; one low-quality site's "no virus" note is generic boilerplate reused across all its port pages and isn't port-specific evidence.
- IANA assignment
corerjd— description field also reads "corerjd" (no expanded text); assignee/contact Chris_Thornhill; dual-registered 284/tcp + 284/udp [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry, line 617 (udp) / line 616 (tcp)- Range class
- well-known (0–1023)
- IANA reference (RFC)
- blank in the registry — not invented [Confirmed]
- Assignment/modification date
- blank in the registry — not invented [Confirmed]
Primary use
Unknown — no RFC, vendor spec, or protocol document found beyond the bare registry name
Common software
none identified in any source [Unknown]
- Security/scanning notes
- no credible evidence of scanning, exploitation, or malware association found; one aggregator's "no virus" note is generic template text, not port-specific [Likely] — https://www.auditmypc.com/udp-port-284.asp, https://isc.sans.edu/services.html, https://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers
- Secondary mirrors
- SpeedGuide, T1 Shopper, ports.my-addr.com, AdminSub all mirror the bare IANA entry with no independent detail; treated as registry mirrors, not sources [Confirmed]
Service assignments.
| Name | Protocol | Description | Open frequency |
|---|---|---|---|
| corerjd | TCP | — | 0.00% |
| corerjd | UDP | — | 0.00% |
Service assignments from the IANA Service Name and Transport Protocol Port Number Registry, with open-frequency data from nmap-services.