315
Summary
- // if you see it open
- No malware/trojan association found; auditmypc.com explicitly lists 'Virus/Trojan: No' for TCP 315. No documented real-world software footprint. An aggregator claim linking this port number to an unrelated 'Automated Tag Audit Protocol (ATAP)' conflicts with the primary IANA record and is treated as likely noise, not included as fact.
- // analyst note
- treat any live 315/tcp listener as unexpected given the absence of a confirmed protocol or deployed software behind the registration.
About port 315/tcp.
Port 315/tcp carries no confirmed protocol beyond IANA's bare registry entry, and no sourced evidence describes real-world software using it — so there is no verified basis for calling it safe for public exposure, and a live listener here is unexpected and worth investigating rather than something to whitelist.
IANA's Service Name and Transport Protocol Port Number Registry lists 315/tcp as dpsi, description "DPSI," with assignee and contact both recorded as Tony Scamurra. The Registration Date, Modification Date, and Reference (RFC) columns are all blank in IANA's own data. The port is dual-registered, with 315/udp carrying an identical entry aside from the transport.
IANA gives no expansion of what "DPSI" stands for or does. Several secondary port-lookup aggregator sites (SpeedGuide, tcp-udp-ports.com, portlookup.com, my-addr.com) expand it as "Distributed Process System Interface," but none cite a primary source, and the phrase does not appear in IANA's own text — that expansion is treated here as unverified secondary-source material, not a confirmed fact.
No specific vendor, product, or deployment documented to use port 315/tcp turned up in research. This reads as a rarely used, largely dormant IANA registration rather than an active service with an established footprint on live networks.
- IANA assignment
dpsi— "DPSI"; reference (blank — no RFC cited); assignee/contact Tony Scamurra; dual-registered 315/tcp + 315/udp [Confirmed] — IANA Service Name and Transport Protocol Port Number Registry, https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv- Range class
- well-known (0–1023)
- Prevalence
- no quantitative scan/telemetry data gathered this pass [Unknown]
- Related ports
- none identified as meaningfully related
Primary use
Unknown — IANA gives no expansion beyond the literal name "DPSI"; no authoritative protocol spec, RFC, or vendor documentation located [Unknown]
Other/unofficial uses
secondary aggregator sites expand it as "Distributed Process System Interface," uncited and unverified
Security implications
no malware/trojan association found; auditmypc.com lists "Virus/Trojan: No"
Typically seen on
no documented real-world deployment found; appears to be a dormant registration [Unknown]
- Analyst note
- treat any live 315/tcp listener as unexpected given the absence of a confirmed protocol or deployed software behind the registration.
About port 315/udp.
Port 315/udp is IANA-registered under the service name dpsi ("DPSI"), but the registry supplies no protocol description, no RFC reference, and no registration date, and no independent source verified in this pass confirms what software actually listens on it — so whether it belongs on the public internet cannot be determined with confidence. Treat it as a rarely-seen, thinly-documented legacy assignment rather than a known public-facing service.
The IANA registry lists dpsi as dual-registered on both 315/tcp and 315/udp, with assignee and contact "Tony_Scamurra" and blank Registration Date, Modification Date, and Reference columns. These blanks are a property of the registry entry itself, not an omission on our part, and this record was confirmed via two independent live fetches of IANA's own CSV and HTML registry pages.
Beyond the bare IANA listing, secondary research found nothing solid. An expansion of "dpsi" as "Distributed Process System Interface" appears on unsourced SEO-style port-lookup sites and was not asserted here as fact. A Juniper Threat Labs application-signature page nominally about "DPSI" lists monitored ports that don't include 315, and a Clavister page nominally on "dpsi" actually describes DNS-over-HTTPS — both were discarded as unreliable rather than cited.
No CVE, malware family, or scan-prevalence data (Shodan, SANS ISC, or similar) was found linking 315/udp to any known behavior. Given the total absence of a documented legitimate use case, an analyst who sees live traffic on this port should treat it as unusual and worth investigating rather than assuming benign, standards-based use.
- IANA assignment
dpsi— "DPSI"; reference (blank — no RFC cited in IANA registry); assignee/contact Tony_Scamurra; dual-registered 315/tcp + 315/udp [Confirmed] — the IANA Service Name and Transport Protocol Port Number Registry, https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv- Range class
- well-known (0–1023)
- Prevalence
- no scan-prevalence or telemetry data found for this port in this pass [Unknown] — https://www.grc.com/port_315.htm
- Related ports
- 315/tcp (dual IANA registration, same assignee and description)
Primary use
Unknown — no protocol description in the IANA registry and no independent source verified during this pass documents the actual function [Unknown]
Other/unofficial uses
an expansion "Distributed Process System Interface" appears on unsourced SEO-style port-lookup pages; not verified and not asserted as fact [Unknown]
Security implications
no CVE, malware family, or exploit reported for this port in this pass; two secondary vendor pages referencing "dpsi" were found unreliable (mismatched ports / mismatched protocol content) and excluded [Unknown]
Typically seen on
Unknown — no verified deployment context found
- Analyst note
- rare and thinly documented; absent a confirmed legitimate use, treat a responsive port 315/udp as worth investigating rather than routine.
Service assignments.
| Name | Protocol | Description | Open frequency |
|---|---|---|---|
| dpsi | UDP | — | 0.04% |
| dpsi | TCP | — | 0.00% |
Service assignments from the IANA Service Name and Transport Protocol Port Number Registry, with open-frequency data from nmap-services.