whatportis.com
suggest an edit →

Port 674ACAP

**ACAP (Application Configuration Access Protocol)** is a protocol designed primarily for the storage, retrieval, and management of user configuration data and preferences across multiple devices or applications. It facilitates centralized access to user-related data such as bookmarks, contact lists, and email preferences, making user profiles portable and synchronized across distributed clients..

inEmailNetwork Services
transport
tcp

single transport

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
4/10

caution

lookups
9,967

rank 471 of 993 · top 47%

Technical Details

what runs on :674

Overview

ACAP, standardized in RFC 2244, is an application-layer protocol that enables clients to remotely access and manage structured hierarchical data, often related to user settings. It employs a client-server model using TCP to provide reliable communication between clients and servers, supporting authenticated and authorized access.

Structure and Capabilities

The protocol manages hierarchical data stores similar to lightweight directories, supporting capabilities such as:

  • Searching: Efficient server-side searching with filtering.
  • Fetching: Retrieval of selected configuration items.
  • Modification: Atomic updates, additions, and deletions.
  • Access Control: Integration with ACLs for user-specific permissions.

This design promotes seamless synchronization of user preferences across email clients, address books, bookmarks, and other compatible network-enabled applications.

Integration and Deployment

While initially envisioned to work closely with email-related protocols like IMAP and LDAP, ACAP remained relatively niche due to the rise of alternative synchronization technologies and proprietary solutions. However, its flexible, hierarchical data model remains an influential design for remote configuration services.

Security Information

exposure of :674

risk score

4/ 10caution

worth attention. how exposed you are depends on configuration — don't leave it reachable from the internet without a reason.

email averages 3.9 across 42 ports — this one sits 0.1 above.

in transit

cleartext

credentials and payloads are readable by anyone on path

assignment

official

registered with iana for this service — scanners fingerprint it by number

reachable over

tcp

every listening transport is another surface to filter at the edge

security overview

Common Vulnerabilities

  • Weak Authentication Mechanisms: If deployed without strong authentication (e.g., plaintext passwords), it can be vulnerable to credential interception.
  • Data Exposure: Since ACAP handles sensitive configuration and personal preferences, lack of encryption exposes this data to eavesdropping.
  • Access Control Misconfigurations: Poor ACL management can lead to unauthorized access or privilege escalation.
  • Injection Attacks: Malformed queries may exploit poorly-validated inputs.

Security Mitigations

  • Enable Strong Authentication: Use SASL mechanisms or other secure authentication protocols.
  • Enforce Encryption: Run ACAP over TLS to protect data in transit.
  • Harden Access Controls: Regularly review and restrict ACL permissions.
  • Patch Regularly: Keep server software updated to mitigate protocol implementation flaws.
  • Network Segmentation: Limit ACAP server exposure within trusted internal networks, avoiding direct Internet access unless necessary.

Related Ports

all 42 in email →

the 8 most looked-up other ports in email — 42 ports carry that label.

portservicerisk
:143IMAPcaution
:995POP3Scaution
:109POP2caution
:2096cPanel SSL Webmailsafe
:110POP3caution
:993IMAPScaution
:1352Lotus Notes RPCcaution
:24Private Mailcaution

risk mix of the 8 listed

  • safe13%
  • caution88%

3 of 8 encrypted