whatportis.com
suggest an edit →

Port 843Adobe Flash Socket Policy

Port 843 is primarily associated with the Adobe Flash socket policy server, which was used historically to deliver cross-domain policy files to Flash applications. This enabled Flash clients embedded in browsers or standalone applications to determine whether they were allowed to establish socket connections to specific servers. Its usage peaked during the prominence of Adobe Flash content across the web, but it has since declined considerably due to the deprecation of Flash technology..

inWeb ServicesSecurity
transport
tcp

single transport

in transit
cleartext

payload readable on path

assignment
unofficial

used by convention

risk
4/10

caution

lookups
12,889

rank 296 of 993 · top 30%

Technical Details

what runs on :843

Port 843 was designated by Adobe Flash Player for serving socket policy files, which are XML documents that define permissions for Flash clients to connect to services on a server using sockets. When a Flash client attempts a socket connection, it sends a request to port 843 for the policy file to verify permissions, typically formatted in XML, before establishing a socket communication session.

This port was a standardized method allowing web administrators to define cross-domain rules in a centralized policy file. The server would respond to a policy-file request on this port, streamlining permission control for all Flash-based socket communications regardless of which port the actual application data uses.

Despite its once widespread use, the relevance of port 843 has greatly declined following the deprecation and end-of-life of Adobe Flash in 2020. Modern web applications and browsers no longer rely on Flash or its security model, favoring more secure and standardized methods such as WebSockets, CORS, or other API-based authentication and authorization techniques.

Security Information

exposure of :843

risk score

4/ 10caution

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

web services averages 3.9 across 112 ports — this one sits 0.1 above.

in transit

cleartext

credentials and payloads are readable by anyone on path

assignment

unofficial

used by convention, not registered — what answers here varies by deployment

reachable over

tcp

every listening transport is another surface to filter at the edge

security overview

Common vulnerabilities associated with port 843 and Flash socket policy servers include:

  • Serving permissive or wildcard policies (e.g., <allow-access-from domain='*' />), which can enable unrestricted cross-domain access, increasing the attack surface.
  • Allowing attackers to exploit misconfigured policies to perform Cross-Site Flashing (XSF) attacks, potentially leading to sensitive information leakage, cross-site scripting, or unauthorized access.
  • Running outdated or insecure Flash components which could be targeted for remote code execution or malware delivery.

Mitigations include:

  • Disabling or removing the socket policy server altogether since Flash is obsolete.
  • Ensuring policy files served (if still necessary) are restrictive, explicitly specifying trusted domains and ports.
  • Monitoring and firewalling port 843 to block unnecessary external access.
  • Replacing legacy Flash components with modern, secure alternatives.
  • Keeping server environments up to date and disabling deprecated technologies like Flash.

Related Ports

all 112 in web services →

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

portservicerisk
:8888Sun Answerbook & Alt HTTPcaution
:8000Intel Remote Desktop / Alternate HTTP Portsafe
:8888NewsEDGEcaution
:8888HTTP Alternative Portcaution
:8888GNUmp3d Streaming HTTPcaution
:9080Groove RPCcaution
:8881Atlasz Secure Servercaution
:80HTTPcaution

risk mix of the 8 listed

  • safe13%
  • caution88%

0 of 8 encrypted