Default ports used by SQL Server Services

Firewall systems help prevent unauthorized access to computer resources. If a firewall is turned on but not correctly configured, connections to SQL Server instances and related services will be blocked. So database administrators need to ensure that firewalls are properly configured to allow inbound and outbound traffic to the SQL Server instance.
Below table list the default ports used by SQL Server services.

Service	Port	Description
SQL Server Database Services	1433 1434 1433 or Dynamic Port	Default Instance Dedicated Admin Connection Named Instance (If named instance is the only instance of the Database Engine installed, it will probably use TCP port 1433 otherwise it uses different port.UDP port 1434 might be required for the SQL Server Browser Service when you are using named instances.)
SQL Server Browser Service	UDP 1434 TCP 2382	Default
SQL Server Service Broker	TCP 4022	Default
SQL Server Analysis Services	TCP 2383	Default Instance. When using Named Instances, TCP port 2382 is needed.
SQL Server Integration Services	TCP 135	Default
SQL Server Reporting Services	TCP 80 TCP 443	Non-SSL (http://) SSL (https://)

Port 135

TCP port 135 is used for many services.

• Transact-SQL debugger
• Microsoft Distributed Transaction Coordinator (MS DTC)
• Windows Management Instrumentation (WMI) - SQL Server Configuration Manager uses WMI to list and manage services.
• Microsoft remote procedure calls (MS RPC) - used to start, stop, and control SQL Server Integration Services and is required only if you connect to a remote instance of the service from SSMS

View sys.tcp_endpoints helps to list ports used by various services such as Service Broker, Mirroring, etc.,

SELECT name, protocol_desc, port, state_desc FROM sys.tcp_endpoints WHERE type_desc in ('SERVICE_BROKER','DATABASE_MIRRORING')

For detailed information about ports used by SQL Server, refer Microsoft article
"Configure the Windows Firewall to Allow SQL Server Access"