High Ports 8080 and 8443 Open – Just Double-Checking

Hi all,


I recently ran a local network scan and noticed that ports 8080 (http-proxy) and 8443 (https-alt) showed up as open. Naturally, I got curious.


To investigate further, I did the following:

  1. Used Terminal to check which services might be using those ports:
  2. sudo lsof -i :8080
  3. sudo lsof -i :8443

No output—so nothing appears to be actively using those ports at the moment.


Noticed that my macOS Firewall was actually turned off (oops!). It’s now on. 😄


Checked my launch daemons and agents: /Library/LaunchDaemons:

    • Malwarebytes entries (expected)
    • ClamXAV entries (expected)


~/Library/LaunchAgents:

    • Only Google software update entries


All of which seem legit.


I also did some grep checks across those folders for references to those ports—still nothing suspicious.


So, my system looks clean to me, but I’d really appreciate a second opinion:


  • Could these ports have been opened temporarily by an app and left idle?
  • Any other diagnostics you’d suggest running?
  • Or am I just being a bit too watchful?


Thanks in advance for your thoughts!


iMac (2017 – 2020)

Posted on Apr 17, 2025 3:17 AM

Reply
Question marked as ⚠️ Top-ranking reply

Posted on Apr 17, 2025 6:55 AM

Are you running a web server locally on the computer?

Why would you not want to run etrecheck to gather and post information that would help us diagnose your issue. We do not have access to your computer and the information you have provided is not sufficient to solve your perceived problem. The information collected and posted by etrecheck does not contain nor share sensitive or private information.

12 replies
Sort By: 
Question marked as ⚠️ Top-ranking reply

Apr 17, 2025 6:55 AM in response to DavosCat

Are you running a web server locally on the computer?

Why would you not want to run etrecheck to gather and post information that would help us diagnose your issue. We do not have access to your computer and the information you have provided is not sufficient to solve your perceived problem. The information collected and posted by etrecheck does not contain nor share sensitive or private information.

Reply

Apr 18, 2025 12:43 PM in response to DavosCat

So, if those ports being "open" is of concern to you, then you will need to configure the router properly. It's possible they were open to provide a way to access the router's control panel under certain circumstances (e.g., if you have a dynamic DNS service). This can be a risk - but of course it also depends on whether you are using the router's default password, or have set your own (and its entropic strength).


Best of luck with your configuring.

Reply

Apr 17, 2025 4:11 AM in response to DavosCat

Ports can be opened and apps started when accessed, and other ports can have apps already using the ports. (There’s a list of what gets automatically started stored in /etc/services.)


Please download and run (free) EtreCheck, and when the run completes share the report to the clipboard. Then open a new reply here, and press the additional-text button that looks like a printed page to get a text input box big enough to paste the hardware and software configuration report here, and paste and post that report here.

Reply

Apr 17, 2025 6:26 AM in response to MrHoffman

MrHoffman wrote:

Ports can be opened and apps started when accessed, and other ports can have apps already using the ports. (There’s a list of what gets automatically started stored in /etc/services.)


Thank you. 🙂


I found:-


http-alt 8080/udp # HTTP Alternate (see port 80)

http-alt 8080/tcp # HTTP Alternate (see port 80)


pcsync-https 8443/udp # PCsync HTTPS

pcsync-https 8443/tcp # PCsync HTTPS


Please download and run (free) EtreCheck, and when the run completes share the report to the clipboard.


I'd prefer not to do so.

Reply

Apr 17, 2025 7:17 PM in response to DavosCat

Ran a network scan with which tool, using what settings, and from where (local network, outside your network firewall)? Some of them make assumptions about post status based on flags coming back on packets in response to their scans that don't always mean what they think those flags mean - especially if the OS is being assumed because the tool can't fingerprint it.

Reply

Apr 18, 2025 1:13 AM in response to g_wolfman

g_wolfman wrote:

Ran a network scan with which tool, using what settings, and from where (local network, outside your network firewall)? Some of them make assumptions about post status based on flags coming back on packets in response to their scans that don't always mean what they think those flags mean - especially if the OS is being assumed because the tool can't fingerprint it.


Thank you for your reply. The tool used was Linux NMAP. I asked a long-standing friend, located more than 200 miles away, to check that all is well here and then let me know. This is what he's said in response to your posting:-


"I really don't have the time for a full run down analysis for random posters in groups I'm not involved with mate... it was a basic quick scan on the fly before I'd even woken up and finished my coffee... I did two scans, one from my local machine and one using a vps via ssh for the very reasons stated by your poster... and I didn't even finish the probes before our conversation moved on!"


I am NOT running a web server (if "BobTheFisherman" is reading here!)

Reply

Apr 18, 2025 1:46 AM in response to BobTheFisherman

BobTheFisherman wrote:

Are you running a web server locally on the computer?
Why would you not want to run etrecheck to gather and post information that would help us diagnose your issue. We do not have access to your computer and the information you have provided is not sufficient to solve your perceived problem. The information collected and posted by etrecheck does not contain nor share sensitive or private information.

Maybe the OP has had a problem with etrecheck - perhaps he/she could clarify?

Reply

Apr 18, 2025 7:52 AM in response to DavosCat

Is your computer actually connected directly to your ISP's cable or fibre modem in an "advanced DMZ"? because if not, you are sitting behind a router (either the ISP Modem's router function, or your own router if the ISPis bridged). Those "open ports" would be on the router which receives traffic to your WAN IP, not your computer which is sitting behind Network Address Translation on a private address.

Reply

Apr 18, 2025 12:07 PM in response to g_wolfman

g_wolfman wrote:

Is your computer actually connected directly to your ISP's cable or fibre modem in an "advanced DMZ"? because if not, you are sitting behind a router (either the ISP Modem's router function, or your own router if the ISPis bridged). Those "open ports" would be on the router which receives traffic to your WAN IP, not your computer which is sitting behind Network Address Translation on a private address.


I agree - 100% - the open ports were on my router, not on my computer.


Thanks for your helpful comments. 🙂

Reply

Apr 18, 2025 12:07 PM in response to DavosCat

DavosCat wrote:

g_wolfman wrote:

Ran a network scan with which tool, using what settings, and from where (local network, outside your network firewall)? Some of them make assumptions about post status based on flags coming back on packets in response to their scans that don't always mean what they think those flags mean - especially if the OS is being assumed because the tool can't fingerprint it.

Thank you for your reply. The tool used was Linux NMAP. I asked a long-standing friend, located more than 200 miles away, to check that all is well here and then let me know. This is what he's said in response to your posting:-

"I really don't have the time for a full run down analysis for random posters in groups I'm not involved with mate... it was a basic quick scan on the fly before I'd even woken up and finished my coffee... I did two scans, one from my local machine and one using a vps via ssh for the very reasons stated by your poster... and I didn't even finish the probes before our conversation moved on!"

I am NOT running a web server (if "BobTheFisherman" is reading here!)


So to summarize the Mac snd network configuration details known so far, you “recently ran a local network scan” from 200 miles using an as-yet-unknown nmap commands and unknown results performed by somebody else, are apparently either directly connected to a publicly-routable IP address or have a VPN server running somewhere or have port-forwarding open to the Mac, and have at least two anti-malware apps running on the Mac.


Depending on the nmap commands used and Mac and gateway / firewall / router/ NAT box configuration details (if there is such a gateway box installed here), nmap may not be reporting accurately. I’m not entirely certain the Mac was scanned, and not the gateway box, for instance. Or that the gateway box was not otherwise injecting itself, as some do.


And while this is and remains entirely your choice, you are unwilling to post Mac configuration details, meaning we are left to guess and ask questions about that, and about the local network setup. Which is inefficient, at best.


And more generally, it seems your friend is apparently either not familiar with macOS support, or is not in a position to assist with macOS support. That as you could potentially provide the configuration report or related details to them, or open up ssh access.


TL;DR: This question is shaping up to be a bit of a project itself.

Reply

High Ports 8080 and 8443 Open – Just Double-Checking

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.