Port 4827HTCP (Hypertext Caching Protocol)

HTCP lets HTTP caches query and manage peer caches, commonly over UDP on port 4827.

transport
tcp · udp

2 transports registered

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
2/10

safe

lookups
0

rank 993 of 5,296 · top 19%

also known as Hypertext Caching Protocol, RFC 2756

Technical Details

what runs on :4827

HTCP (specified in RFC 2756) carries cache queries and management operations such as testing whether an object is cached or requesting that it be cleared. Implementations commonly exchange framed HTCP messages over UDP; the registry also assigns TCP, but that is not the transport most typically encountered. Squid commonly uses port 4827 for HTCP. This is distinct from HTTP client traffic, which normally uses ports 80 or 443.

Security Information

exposure of :4827

risk score

2/ 10safe

routine exposure. this port is rarely the way in on its own — keep it patched and logged and move on.

web services averages 3.1 across 192 ports — this one sits 1.1 below.

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 · udp

udp is connectionless — source addresses are trivially spoofed and it is a reflection favourite

security overview

HTCP is not encrypted by default, and an exposed cache may reveal cache contents or metadata and accept cache-management requests, depending on its configuration. Do not expose it to the public internet; restrict it to trusted cache peers with firewall rules and the implementation's access controls.

the 8 most looked-up other ports in web services — 192 ports carry that label.

risk mix of the 8 listed

  • safe13%
  • caution88%

0 of 8 encrypted