1118
Summary
- // if you see it open
- RFC 3767 requires credential servers to support TLS and DIGEST-MD5; clients must support DIGEST-MD5 and TLS with server authentication. The assigned port alone does not establish that a listener implements these safeguards.
About port 1118/tcp.
TCP port 1118 is assigned to sacred, the port name for SACRED, a protocol for exchanging cryptographic credentials with a credential server. RFC 3767 says SACRED SHOULD run on this port. The assignment and recommendation do not establish that any host currently runs it or that it belongs on the public internet, so public exposure is Unknown.
SACRED supports credential upload, download, and deletion, as well as optional account management. RFC 3767 specifies XML payloads and a BEEP profile. It requires credential servers to support TLS and DIGEST-MD5; clients must support DIGEST-MD5 and TLS with server authentication. These protocol safeguards do not establish the security or configuration of a particular service.
No supplied evidence measures deployment or traffic prevalence, identifies current operators, or documents malware use. A listener on 1118 should therefore be identified from its protocol behavior and configuration rather than assumed to be SACRED from the port number alone.
- Protocol
- IANA assigns TCP 1118 the service name
sacred; RFC 3767 describes SACRED credential exchange. [Confirmed] - Exposure
- Unknown. Assignment and protocol specification do not establish the intended audience of current deployments. [Unknown]
- Security
- SACRED specifies TLS and DIGEST-MD5 support requirements; a port number alone does not establish that a listener uses them. [Confirmed]
- Prevalence
- Unknown; no scoped measurement is supplied. [Unknown]
- IANA service name
- sacred [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv
Protocol and purpose
SACRED exchanges cryptographic credentials with a credential server; RFC 3767 says it SHOULD run over port 1118
- Security requirements
- Credential servers must support TLS and DIGEST-MD5; clients must support DIGEST-MD5 and TLS with server authentication [Confirmed] — https://www.rfc-editor.org/rfc/rfc3767.txt
- Current deployment, prevalence, and public audience
- Unknown [Unknown] — https://www.rfc-editor.org/rfc/rfc3767.txt
About port 1118/udp.
The IANA registry assigns UDP port 1118 the service name sacred, and RFC 3767 specifies SACRED for exchanging cryptographic credentials with a credential server. The evidence does not establish whether SACRED is deployed over UDP in practice or whether any host is reachable on this port, so its intended public-internet exposure is unknown.
RFC 3767 describes credential upload, download, deletion, and account operations. Its security requirements include support for TLS and DIGEST-MD5. The specification says SACRED should run over port 1118, but that recommendation does not demonstrate current traffic or deployment.
Because the available evidence identifies the protocol but does not establish its intended network audience or UDP deployment, do not infer a public-facing access policy. Credential services can handle private keys and related material; where SACRED is deployed, access controls and the specified authentication and confidentiality protections matter.
- Exposure
- Unknown. The registry and protocol specification do not establish the intended audience or whether any UDP service is deployed on this port.
- Protocol
- IANA assigns
sacred; RFC 3767 describes secure exchange of cryptographic credentials with a credential server. - Security
- RFC 3767 requires credential servers to support TLS and DIGEST-MD5; registry assignment alone does not establish that a deployment uses these protections.
- Service name
sacred[Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv
Protocol purpose
Exchange cryptographic credentials with a credential server
- RFC reference
- RFC 3767 [Confirmed] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv
- UDP deployment or public reachability
- Unknown [Unknown] — https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.csv
Service assignments.
| Name | Protocol | Description | Open frequency |
|---|---|---|---|
| sacred | TCP | — | 0.01% |
| sacred | UDP | — | 0.00% |
Service assignments from the IANA Service Name and Transport Protocol Port Number Registry, with open-frequency data from nmap-services.