How to not expose your Tor socks port

nmap -AO

Starting Nmap 7.94SVN ( ) at 2024-03-21 15:56 CST
Nmap scan report for localhost (
Host is up (0.000055s latency).
Not shown: 997 closed tcp ports (reset)
53/tcp   open  domain    dnsmasq 1.32
| dns-nsid: 
|_  bind.version: dnsmasq-1.32
3306/tcp open  mysql     MySQL 5.5.5-03.02.1-MariaDB-2
| mysql-info: 
|   Protocol: 10
|   Version: 5.5.5-03.02.1-MariaDB-2
|   Thread ID: 51
|   Capabilities flags: 63486
|   Some Capabilities: LongColumnFlag, SupportsCompression, Speaks41ProtocolNew, FoundRows, ConnectWithDatabase, Speaks41ProtocolOld, ODBCClient, IgnoreSigpipes, Support41Auth, InteractiveClient, DontAllowDatabaseTableColumn, IgnoreSpaceBeforeParenthesis, SupportsLoadDataLocal, SupportsTransactions, SupportsAuthPlugins, SupportsMultipleStatments, SupportsMultipleResults
|   Status: Autocommit
|   Salt: 6{,d7"BhfGmrtnNx6?yg
|_  Auth Plugin Name: mysql_native_password
**9050/tcp open  tor-socks Tor SOCKS proxy**
**| socks-open-proxy: **
**|   status: open**
**|   versions: **
**|     socks4**
**|_    socks5**
**| socks-auth-info: **
**|   Username and password**
**|_  No authentication**
No exact OS matches for host (If you know what OS is running on it, see ).
Nmap done: 1 IP address (1 host up) scanned in 27.88 seconds

How to prevent scans from exposing this information to the tor

Nmap has scanned localhost of a computer, I suppose from localhost of that computer, and finds DNS, mySQL and a Tor client socks port opened.
No issue with that, as long as the external address of the host computer is not forwarded to localhost.
Localhost is by default not accessible from the outside.
If a firewall is available all inbound ports that are not needed can be closed.


tanks for you

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.