413
Summary
- // typical exposure
- Anomalous (rarely legitimately open) — No IANA-referenced specification, vendor product, or observed real-world traffic exists for smsp on port 413, so this port should never be expected to face the public internet and any activity on it should be treated as anomalous and investigated.
- // analyst note
- An open/active 413/tcp has no known legitimate real-world use beyond the bare IANA name; treat as anomalous and worth investigating rather than a routine service.
- // if you see it open
- No CVEs, advisories, or malware associations specific to 413/tcp were found. The port has no documented working protocol, vendor product, or real-world deployment beyond the bare IANA name registration, so unexpected traffic on it should be treated as anomalous and investigated rather than assumed legitimate.
About port 413/tcp.
Port 413/tcp carries no documented working protocol in practice — it is IANA-registered under the name smsp ("Storage Management Services Protocol"), but no RFC, vendor product, or real-world deployment describing that protocol was found, so it should not be expected to face the public internet and any traffic on it is unusual rather than routine.
The IANA registry lists 413/tcp (and 413/udp, dual-registered) under service name smsp, description "Storage Management Services Protocol," with contact/assignee recorded as Murthy Srinivas. The Reference column is blank in the authoritative registry — there is no RFC backing this assignment, and none should be invented.
Beyond the bare registry line, which is echoed verbatim by generic port-lookup directories (t1shopper, SpeedGuide, adminsub.net, auditmypc.com, my-addr.com) and by nmap-services, no substantive material exists. No specification, no named software product, and no forum, blog, or game-client discussion of real traffic on this port turned up in research.
No scanning, honeypot, or exposure-telemetry writeup specific to 413/tcp was found in external research, but the repo's own nmap-services-derived dataset (this site's own tooling) records an open-frequency prevalence of 0.000013 for this port and transport, indicating scan/exposure activity is rare.
- IANA assignment
smsp— "Storage Management Services Protocol"; reference (blank — no RFC cited); assignee/contact Murthy Srinivas; dual-registered 413/tcp + 413/udp [Confirmed] — IANA Service Name and Transport Protocol Port Number Registry- Range class
- well-known (0–1023) [Confirmed]
- Prevalence
- 0.000013 (nmap-services open-frequency) [Confirmed] — this site's own tooling
- Related ports
- none directly related identified in this research pass [Unknown]
Primary use
registered name only ("Storage Management Services Protocol"); no publicly available protocol spec, RFC, or documented implementation found
Other/unofficial uses
none documented in this research pass [Unknown]
Security implications
no CVEs, advisories, or malware associations found specific to 413/tcp; obscurity and absence of any real deployment make unexpected traffic worth investigating
Typically seen on
no documented hosts or software; not expected to appear in normal deployments [Unknown]
- Analyst note
- An open/active 413/tcp has no known legitimate real-world use beyond the bare IANA name; treat as anomalous and worth investigating rather than a routine service.
About port 413/udp.
Port 413/udp carries no actively deployed service in practice; IANA registers it as smsp (Storage Management Services Protocol), but no RFC or currently-shipping software has been confirmed using it, so a responsive port 413/udp is unusual and should not be exposed to the public internet.
IANA's Service Name and Transport Protocol Port Number Registry lists 413 as dual-registered on both TCP and UDP under the name smsp, described only as "Storage Management Services Protocol," with assignee Murthy Srinivas and a blank reference field — no RFC document defines the protocol's wire format or behavior.
Because the registration has no accompanying specification and no vendor or open-source project has been found implementing it, 413/udp functions today mainly as a dormant IANA entry rather than a live service. GRC's Port Authority lists a low-confidence, historical trojan sighting ("Coma") tied to port 413, but this is not corroborated by current threat intelligence. AuditMyPC's own port page, by contrast, records no virus/Trojan association for 413/udp — its "flagged as a virus" language is site-wide template boilerplate with only the port number swapped, not port-413-specific evidence.
- IANA assignment
smsp— "Storage Management Services Protocol"; reference (blank — no RFC cited); assignee Murthy Srinivas; dual-registered 413/tcp + 413/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=8)- Range class
- well-known (0–1023) [Confirmed]
- Prevalence
- 0.000395 (nmap-services open-frequency) [Confirmed] — this site's own tooling
- Related ports
- 413/tcp (identical dual registration, same
smsprecord) [Confirmed]
Primary use
no RFC-defined or actively deployed protocol found; the registration appears dormant
Other/unofficial uses
none confirmed; no vendor or open-source implementation of smsp found [Unknown]
Security implications
essentially never legitimately open; GRC Port Authority notes a low-confidence historical trojan association ("Coma"), not corroborated by current threat intel; auditmypc.com's own verdict line for 413/udp reads "Virus / Trojan: No" — none documented there
Typically seen on
background-radiation scan responses; legacy or decoy anomalies [Likely]
- Analyst note
- a responsive 413/udp should be treated as an anomaly to investigate, not a routine service [Likely]
Service assignments.
| Name | Protocol | Description | Open frequency |
|---|---|---|---|
| smsp | UDP | — | 0.04% |
| smsp | TCP | Storage Management Services Protocol | 0.00% |
Service assignments from the IANA Service Name and Transport Protocol Port Number Registry, with open-frequency data from nmap-services.