# data[].attributes.body
TCP port: Portas 22, 443, 3389, 18083, e 49152-65534 são configuraveis

https://docs.oracle.com/cd/E26217_01/E26214/html/firewalls.html#:~:text=Ports%2022%2C%20443%2C%203389%2C,used%20to%20connect%20to%20desktops.

# data[].attributes.attachment_link.readable_text
Firewalls can be used to protect various parts of a network and must be configured to permit the connections required by Oracle VDI.

Clients must be able to connect to any host in an Oracle VDI Center.

The following table lists the ports you might need to open to permit these connections.

All hosts in an Oracle VDI Center need to be able to make connections to any of the configured user directories.

The following table lists the ports you might need to open to permit these connections.

Ports Required for Active Directory Type Directories

Each Oracle VDI host must be able to make connections to Active Directory on the following ports:

Port 53 for DNS lookups on Active Directory

Ports 88 and 464 for Kerberos authentication to a Key Distribution Center (KDC)

Port 389 for the secure LDAP connection to a domain controller

Port 3268 for the secure LDAP connection to a global catalog server

Oracle VDI performs several DNS lookups to discover LDAP information. For these lookups to work, it is essential that your DNS is configured correctly to enable the required information to be returned from Active Directory.

Ports 88 and 464 are the standard ports used for Kerberos authentication to a Key Distribution Center (KDC). These ports are configurable. Connections to these ports can use either the TCP or UDP protocol depending on the packet size and your Kerberos configuration. Port 464 is only required for password change operations.

Ports Required for LDAP Type Directories

The standard ports used for connections to LDAP directories are port 389 for standard connections (simple authentication) and port 636 for secure connections (secure authentication). These ports are configurable.

In order to run desktops, all hosts in an Oracle VDI Center must be able to connect to any of the configured desktop provider hosts, and their associated storage hosts.

The ports used for connections depends on the desktop provider type and whether the storage is managed by Oracle VDI.

The following table lists the ports you might need to open to permit these connections.

Ports 22, 443, 3389, 18083, and 49152-65534 are configurable.

On VirtualBox hosts, the HTTPS port is configured when you install VirtualBox. The VRDP ports are only required if the VRDP protocol is used to connect to desktops. See Choosing Between VRDP and MS-RDP for details. The range of ports used is configurable, see Configuring the VRDP Port Range for details.

A network might contain firewalls between the hosts in an Oracle VDI Center, for example if you have multiple offices each containing an Oracle VDI host. The Oracle VDI hosts must be able to connect to any other member of the Oracle VDI Center.

The following table lists the ports you might need to open to permit these connections.

On Oracle VDI hosts, port 3303 is also used for the connection between the vda client command and the Oracle VDI host. This port is bound to localhost and is configurable.

# data[].attributes.attachment_link.description
Firewalls can be used to protect various parts of a network and must be configured to permit the connections required by Oracle VDI. Clients must be able to connect to any host in an Oracle VDI Center. The following table lists the ports you might need to open to permit these connections.

# data[].attributes.body
(PPTP) - Port 1723 TCP

(L2TP) - Ports 1701 TCP, 500 UDP and 4500 UDP

(IPSec) - Ports 500 UDP and 4500 UDP

(SSTP) - Port 443 TCP

OpenVPN - Ports 1194 UDP and 443 TCP

Referência: https://nordvpn.com/pt-br/blog/what-are-vpn-ports/

# data[].attributes.body
TCP: 443, 80

Fonte: https://docs.microsoft.com/pt-br/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worldwide

# data[].attributes.body
TCP: 587, 993 e 995

fonte: https://support.microsoft.com/pt-br/office/configura%C3%A7%C3%B5es-pop-imap-e-smtp-8361e398-8af4-4e97-b147-6c6c4ac95353

# data[].attributes.attachment_link.readable_text
Você pode usar Outlook para ler e enviar emails do Yahoo, Gmail, Hotmail e outras contas de email. Se você quiser adicionar manualmente outra conta de email Outlook, talvez seja necessário usar a configuração avançada. Consulte Adicionar uma conta de email Outlook.

Você precisará das configurações de servidor de entrada do provedor de email (POP ou IMAP) e configurações de servidor de saída (SMTP). Aqui está uma lista dessas configurações para vários provedores de email. Se você não vir o seu listado aqui, peça ao provedor de email para dar a você.

Consulte também

POP, IMAP e SMTP para Outlook.com

Adicione suas outras contas de email a Outlook.com

Conexão contas de email Outlook na Web (Microsoft 365)

Recursos de suporte

Também é possível obter suporte dos outros Outlook.com usuários no nosso Fórum da comunidade, ou obter ajuda selecionando contatar o suporte abaixo:

Observação: Será necessário entrar primeiro para obter suporte. Se você não conseguir entrar, vá para Suporte de conta.

# data[].attributes.attachment_link.description
Você pode usar Outlook para ler e enviar emails do Yahoo, Gmail, Hotmail e outras contas de email. Se você quiser adicionar manualmente outra conta de email Outlook, talvez seja necessário usar a configuração avançada. Consulte Adicionar uma conta de email Outlook.

# data[].attributes.body
TCP: 443, 1000-10000, 50000-65000, 16000-26000;
UDP: 3478-3481, 50000-60000

Fonte: https://support.skype.com/pt-br/faq/FA148/quais-portas-precisam-ser-abertas-para-usar-skype-na-area-de-trabalho

# data[].attributes.attachment_link.title
Quais portas precisam ser abertas para usar Skype na área de trabalho? | Suporte do Skype

# data[].attributes.body
TCP: |433, 3478-3479, 5060, 5062, 5222, 6250, 12000-65000
UDP:| 3478-3479, 5060, 5062, 6250, 12000-65000

Referência: https://portforward.com/epic-games-launcher/

# data[].attributes.attachment_link.readable_text
The ports that need to be forwarded for Epic Games Launcher are listed here:

Epic Games Launcher - PC

TCP: 433, 3478-3479, 5060, 5062, 5222, 6250, 12000-65000

UDP: 3478-3479, 5060, 5062, 6250, 12000-65000

Setting Up a Port Forward for Epic Games Launcher

You might need to forward some ports in your router when you use Epic Games Launcher. A port forward allows incoming connection requests from the internet to go straight to Epic Games Launcher.

Routers are not designed to allow incoming network requests. By forwarding ports you can work around this limitation.

Before Forwarding a Port

Before forwarding a port make sure that you know these things:

Your router's internal IP address.

Your computer's internal IP address.

A list of TCP and UDP ports that need to be forwarded.

Locate Your Router's IP Address

The easiest way to locate your router's IP address is to run our free Router Detector utility. The software is part of our Network Utilities suite of tools and it is completely free to use.

If you do not want to run the software, you can follow our Find Your Router IP Address guide.

How To Forward Ports for Epic Games Launcher

We have Network Utilities software that can forward ports for you. Since Network Utilities allows you to both forward and un-forward ports easily you can keep your network security maximized, and then forward ports only when you need them.

Port forwarding can also be set up step-by-step by hand. The step-by-step process for forwarding a port is:

Log in to your router.

Find the port forwarding section in your router.

Type your computer's IP address into the correct box in your router.

Put the TCP and UDP ports that you are forwarding for Epic Games Launcher in the correct boxes in your router.

Frequently you have to reboot your router for the changes to take effect.

You can choose your router from our list to see exactly how to forward ports for Epic Games Launcher:

List of Routers - Customized for Epic Games Launcher

That is the process required to forward ports in your router for Epic Games Launcher.

# data[].attributes.attachment_link.keywords[]
port forward epic games launcher epic games epic games

# data[].attributes.attachment_link.title
How to Create a Port Forward in Your Router for Epic Games Launcher

# data[].attributes.attachment_link.description
The ports that need to be forwarded for Epic Games Launcher are listed here: TCP: 433, 3478-3479, 5060, 5062, 5222, 6250, 12000-65000 UDP: 3478-3479, 5060, 5062, 6250, 12000-65000 You might need to forward some ports in your router when you use Epic Games Launcher.

# data[].attributes.body
FIFA 21 – PC

TCP: | 8080, 9988, 9946, 10000-20000, 3569, 42124
UDP: | 9000-9999, 3659

FIFA 21 – PlayStation 4

TCP: | 3659, 3478-3480, 10000-10099, 1935,42127
UDP: | 3659, 3478-3479, 3074, 6000

FIFA 21 – PlayStation 5

TCP: | 3478-3480, 10000-10099, 3659, 1935, 42127
UDP: | 3659, 3478-3479, 3074, 6000

FIFA 21 – Steam

TCP: | 3569, 9946, 10000-20000, 9988, 27015-27030, 27036-27037, 8080, 42124
UDP: | 4380, 27000-27031, 9000-9999, 3659, 27036

FIFA 21 – Xbox One

TCP: | 3074, 3659
UDP: | 88, 3074, 3659, 3544, 500, 4500

FIFA 21 – Xbox Series X

TCP: | 3659, 3074
UDP: | 88, 3074, 500, 3544, 4500, 3659

FIFA 21 – Switch

TCP: | 6667, 28910, 29901, 29900, 12400, 29920
UDP: | 1-65535

Referência: https://www.portforwardinghub.com/games/fifa-21-port-forwarding/

# data[].attributes.body
TCP: 80, 443 (conexão)

443, 8801, 8802 (Clientes)

Referência: https://support.zoom.us/hc/en-us/articles/202342006-Network-Firewall-Settings-for-Meeting-Connector

# data[].attributes.body
TCP: 6463

Referência: https://www.speedguide.net/port.php?port=6463

# data[].attributes.body
TCP:  443, 3478
Referência: https://support.google.com/a/answer/1279090?hl=en#zippy=%2Cstep-set-up-outbound-ports-for-media-traffic

# data[].attributes.attachment_link.readable_text
The following recommendations apply to typical office environments. A wireless engineer should evaluate more complex environments, such as manufacturing floors, areas with high levels of radio frequency (RF) noise, or sparsely covered spaces.
Carefully review the following considerations during the design, deployment, and operation of wireless networks used by Meet.

2.4 GHz versus 5 GHz RF bands

We recommended that your network force clients onto the 5 GHz RF band, if available.

We recommend to not deploy and operate Meet over the 2.4-GHz band of a wireless network as it's typically heavily used. The 2.4-GHz band is also less reliable because it has 3 non-overlapping channels, typically high noise levels from nearby interfering networks, and extra interference from other devices.

Design and deployment considerations

For the wireless network, think about capacity rather than coverage.

Manage cell size-Control cell size by the transmit power of the access point (AP). Deploy smaller cells where more devices are expected, such as meeting rooms and auditoriums, to increase capacity. Use bigger cells to provide general coverage on the office floor.

Disable low rates to improve RF usage efficiency and force a client's handover to the closest AP while roaming between APs.

If a wireless network's SSID is available on both bands (2.4 GHz and 5 GHz), the network should force clients onto the 5-GHz band.

To allow advanced features, such as seamless roaming between APs and proper RF management, a wireless network should be centrally managed and operated-not a collection of standalone APs.

Finally, perform a post-deployment wireless survey to confirm wireless coverage in the spaces where Meet is typically used.

WMM best practices

To support reliable Meet communication over wireless networks, you should implement Wireless Multimedia Extensions (WMM).

Meet traffic needs to be classified by one of the following ways:

The wireless controller or AP based on the Meet-specific protocols and ports.

The Differentiated Services Code Point (DSCP) field value set by other network equipment. Use DSCP if you have sufficient trust in the network.

While full WMM support (including clients) is required to provide bidirectional QoS, you can configure it at the network level (on the controller or AP) to give significant benefits. Meet traffic should be assigned to the audio or video queue on the wireless AP or controller and be preferred over other classes of traffic.

# data[].attributes.attachment_link.title
Prepare your network for Meet video calls

# data[].attributes.attachment_link.description
The following recommendations apply to typical office environments. A wireless engineer should evaluate more complex environments, such as manufacturing floors, areas with high levels of radio frequency (RF) noise, or sparsely covered spaces. Carefully review the following considerations during the design, deployment, and operation of wireless networks used by Meet.

# data[].attributes.body
TCP: 5522, 443
Referência: https://developers.facebook.com/docs/whatsapp/guides/network-requirements/

# data[].attributes.attachment_link.readable_text
This document provides information for setting up your network and debugging potential problems.

The WhatsApp Business API client has certain network requirements for connecting to the WhatsApp servers. If your business cannot do the below, we unfortunately cannot support your WhatsApp integration.

We understand that different businesses have different network configurations and security concerns Contact Direct Support if this document is not sufficient for your setup because of any special connectivity or security requirements you may have.

The WhatsApp Business API client requires a long-lived TCP connection. Occasional requests will be made so the connection does not stay idle. However, you will have to ensure that your firewall, router, security, etc. do not terminate the long-lived TCP connections.

Ports

There are two ports used for outgoing traffic:

They are not listening or used for incoming traffic. Your business's firewall can still protect from incoming traffic as normal.

The default port for the WhatsApp Business API client is 5222. If that port is not available, the application will fallback to port 443. Port 443 needs to be opened for HTTPS at the minimum for application registration and restarts. You can leave port 5222 closed and have port 443 open, but you cannot open port 5222 and not port 443.

It is recommended that you open both ports and allow all outgoing traffic.

Protocols

The WhatsApp Business API client uses two types of protocols:

The WhatsApp proprietary chat protocol, called chatd, is used to send the encrypted messages and information to and from the WhatsApp servers. Because it is proprietary, we ask that the port you open be on an allow list for all outgoing traffic. Some firewalls and proxies terminate non-SSL connections, which will interfere with the application's ability to connect to WhatsApp servers.

WhatsApp uses HTTPS during registration and it is necessary for restarts. We do not recommend blocking HTTPS after registration because you never know when you will have to re-register or restart your application.

IP Addresses

WhatsApp uses a wide range of IP addresses for its servers. You can try to allow all of the IP addresses. However, it is best to just allow all outgoing traffic and connections from the above ports.

List of the WhatsApp server IP addresses and ranges (.zip file)
(updated July 3, 2021, applicable beginning August 30, 2021)

This list might change often. It is therefore recommended you allow all outgoing traffic from port 5222 or 443, to avoid having to update this allow list in your network each time it changes.

Hostnames

You can add the WhatsApp servers to your allow list by hostname rather than IP address.

The WhatsApp server hostnames that the WhatsApp Business API client requires connectivity to are:

.*.cdn.whatsapp.net

g.whatsapp.net

graph.facebook.com

graph.whatsapp.com

media-.*.cdn.whatsapp.net

media..*.fna.whatsapp.net

mmg.whatsapp.net

pps.whatsapp.net

static.whatsapp.net

v.whatsapp.net

Docker Container Images

You will also need to allow access to our repository in JFrog where we host the Docker container images in order to download them.

You must use hostnames in your allow list for JFrog as IP addresses cannot be provided.

The necessary JFrog hostnames are:

docker.whatsapp.biz

dl.bintray.com

akamai.bintray.com

Firewalls

Depending on your firewall and how it functions, adding the hostnames to an allow list may not work and you will need to add all the IP addresses to an allow list instead.

Examples of firewall behavior that will not work with just the hostnames on an allow list are:

Firewalls that run a DNS query (against the DNS configured in your data center) and use the resulting IPs in the allow list;

Firewalls that look for outbound DNS queries from machines in the data center and use IP addresses that are seen in the response to the allow list;

Firewalls that look for hostnames in the HTTP/HTTPS handshake.

In the event that your firewall exhibits one of these behaviors please proceed to use the IP addresses in an allow list.

Proxies

Configure network proxies by setting the following environmental variables to the proxy you are using, then pass them to the Coreapp:

Testing with WADebug

The WADebug tool can help quickly check whether the Coreapp container has access to all the required WhatsApp servers. With WADebug installed, simply run:

  wadebug partial check_network

FAQ

# data[].attributes.attachment_link.title
Set Up and Debug Your Network - WhatsApp Business Platform - Documentation - Facebook for Developers

# data[].attributes.attachment_link.description
This document provides information for setting up your network and debugging potential problems. The WhatsApp Business API client has certain network requirements for connecting to the WhatsApp servers. If your business cannot do the below, we unfortunately cannot support your WhatsApp integration.

# data[].attributes.body
TCP/IP: 3306
Ref:
https://dev.mysql.com/doc/workbench/en/wb-mysql-connections-methods-standard.html

# data[].attributes.attachment_link.readable_text
This connection method enables MySQL Workbench to connect to MySQL Server using TCP/IP. In addition to naming your new connection in the field provided, you can select from the following tabs to specify connection values: Parameters, SSL, and Advanced.

The skip_networking MySQL system variable affects the TCP/IP connection method. If disabled, use named pipes or shared memory (on Windows) or Unix socket files (on Unix).

Parameters Tab

The parameters for standard TCP/IP connections are:

Hostname: The host name or IP address of the MySQL server.

The host name "localhost" might resolve to "127.0.0.1" or "::1" on your host, so note this when checking permissions. For example, if a web application's user only has access to "127.0.0.1" on a host, and a defined connection uses "localhost" that resolves to "::1", this connection may lack the proper permissions to the aforementioned web application. Ping "localhost" on each host to determine where it resolves to.

Port: The TCP/IP port on which the MySQL server is listening (the default is 3306).

Username: User name to use for the connection.

Password: Optional password for the account used. If you enter no password here, you are prompted to enter the password when MySQL Workbench attempts to establish the connection. MySQL Workbench can store the password in a vault (see Section 5.3.9, "The Password Storage Vault").

Default Schema: When the connection to the server is established, this option sets the schema that becomes the default schema for use in other parts of MySQL Workbench. For simplicity, you can leave the default schema value blank during the initial setup and set the default value later, if needed.

SSL Tab

SSL parameters are:

Use SSL: SSL encryption is configurable, enabling you to adjust your connection to the conditions determined by the server. The values are:

No - establishes an unencrypted connection.

If available (default) - establishes an encrypted connection if the server supports encrypted connections, falling back to an unencrypted connection if an encrypted connection cannot be established.

Require - causes the connection attempt to fail if an encrypted connection cannot be established.

Require and Verify CA - requires an encrypted connection and also performs verification against the server CA certificate.

Require and Verify Identity - performs verification against the server CA certificate and against the server host name in its certificate.

SSL Key File: Path to the Key file for SSL.

SSL CERT File: Path the Certificate file for SSL.

SSL CA File: Path to the Certification Authority file for SSL.

SSL Cipher: Optional list of permissible ciphers to use for SSL encryption.

Actions in this tab:

Advanced Tab

The Advanced tab includes these check boxes:

Use compression protocol: If checked, the communication between the application and the MySQL server will be compressed, which may increase transfer rates. This corresponds to starting a MySQL command-line client with the --compress option. This option is unchecked by default.

Use ANSI quotes to quote identifiers: Treat as an identifier quote character (like the quote character) and not as a string quote character. You can still use to quote identifiers with this mode enabled. With this option enabled, you cannot use double quotation marks to quote literal strings, because it is interpreted as an identifier. Note: If this option is checked, it overrides the server setting. This option is unchecked by default.

Enable Cleartext Authentication Plugin: Send the user password as text that is not encrypted. Required for some authentication methods. This option is unchecked by default.

Use the old authentication protocol: This option disables the Connector/C++ secure_auth option. This option is unchecked by default. Doing so means you can connect to MySQL Server with MySQL users that utilize the old mysql_old_password authentication plugin, which is not recommended. mysql_old_password support was removed in MySQL Server 5.7.

This option was removed in MySQL Workbench 6.3.6, and did not function in MySQL Workbench 6.3.5. For information about upgrading passwords from the old authentication protocol, see Section 5.3.10, "Updating Old Authentication Protocol Passwords".

Also, MySQL Server 5.7 does not support the old authentication protocol, because secure_auth cannot be disabled. Using the old mysql_old_password has not been recommended since MySQL 4.1.

It also includes these options:

Timeout: Maximum time to wait before the connection is aborted. The connection times out in 60 seconds by default.

SQL_MODE: Override the default SQL_MODE used by the server.

Others: Other options for Connector/C++ as option=value pairs, one per line.

# data[].attributes.attachment_link.title
MySQL :: MySQL Workbench Manual :: 5.3.1 Standard TCP/IP Connection Method

# data[].attributes.body
TCP port: 9418
https://bigbrassband.com/git-integration-for-jira/documentation/git-url-ports.html

# data[].attributes.attachment_link.description
If your Jira and Git servers are running through a firewall, configure the firewall to allow access using the URL schemes for git repositories. For authentication issues, make sure to check first the correct port for its connection.

# data[].attributes.body
TCP port: 443

Ref: https://www.godaddy.com/garage/whats-an-ssl-port-a-technical-guide-for-https/

# data[].attributes.attachment_link.readable_text
Secure Sockets Layer (SSL) is the technology responsible for data authentication and encryption for internet connections. It encrypts data being sent over the internet between two systems (commonly between a server and a client) so that it remains private. And with the growing importance of online privacy, an SSL port is something you should get familiar with.

Because data can be sent with or without the use of SSL, one way to indicate a secure connection is by the port number. By default, HTTPS connections use TCP port 443. HTTP, the unsecure protocol, uses port 80.

Commonly used TCP ports

For those responsible for configuring and managing web hosting, it's useful to know the numbers for common services, such as an SSL port. Use the tables below to quickly look up port numbers and their basic functions.

Web

Email

You can see which ports GoDaddy uses for email - in addition to finding SSL port information - in the GoDaddy Help Center.

cPanel

You can see which ports GoDaddy uses for cPanel in the GoDaddy Help Center.

How does HTTPS and SSL work?

HTTP is not a separate protocol from HTTPS. Rather, HTTPS works by establishing a secure HTTP connection using SSL. Hence, the protocol stacks for HTTP and HTTPS look similar:

The only difference is that HTTPS runs over SSL. To create this secure internet connection, an SSL certificate is installed on a web server. The SSL certificate authenticates an organization's identity to activate the HTTPS protocol so that data can be passed securely from a web server to a web browser.

Distinguishing between certificates and protocols

The HTTPS protocol and an SSL certificate are two different - but critical - factors in creating a secure internet connection.

The HTTPS protocol provides the channel by which data is encrypted and transferred securely.

SSL certificates are simply used to authenticate critical information when an internet user attempts to send information over a secure connection.

Therefore, the secure connection is determined by your server configuration and not by the certificate itself.

What is the difference between SSL and TLS?

Transport Layer Security (TLS) is an update to the SSL protocol. The original SSL protocol was developed by Netscape back in 1995 and released to the public as SSL 2.0. Since that time, updates have been made to ensure stronger, more secure encryption.

In 1999, TLS 1.0 was released as an update to SSL 3.0. Since then, TLS has been the primary technology used to secure data over internet connections and SSL. However, because the term SSL is more widely-known, the name carries on despite the technology depreciating.

Why should I worry about my SSL port?

Seemingly a small nuance, your SSL port is important for a number of reasons. For starters, HTTP is falling out of favor. In fact, more than 70 percent of web pages are loaded via HTTPS in Google Chrome in the United States, according to Google's HTTPS Transparency Report. Besides the reason that "everyone else is doing it," there are a ton of advantages to using HTTPS as opposed to HTTP.

Limit exposure to criminal activity by using SSL

HTTPS offers an additional layer of protection against digital eavesdropping, whereby criminals monitor network activity to steal valuable information like login credentials. Because HTTPS is encrypted, it helps to thwart this type of criminal activity.

HTTPS is required for PCI compliance

If you collect credit card information on your website, then you are required by the Payment Card Industry to use HTTPS.

HTTPS is capable of loading web pages faster than HTTP

Not only does HTTPS make for a more secure browsing experience, it can also positively impact the load times of your site content. If you need proof, see for yourself.

Create a more trustworthy web browsing experience

Most major web browsers indicate whether or not a site is secure in the address bar with a padlock icon or the word "secure."

Web browsers, like Chrome, are moving towards alerting users when they've accessed a site that is not using HTTPS.

SSL can boost your SEO

HTTPS is preferred by major search engines and is generally considered beneficial for SEO. It is crucial that you implement HTTPS correctly and take a few extra steps to ensure you reap the SEO benefits. Follow this HTTPS migration checklist for SEO to make sure you get it right.

How do I get SSL?

SSL certificates can be purchased from a Certificate Authority (CA), like GoDaddy. After you purchase the certificate, follow the instructions from your hosting provider to install the SSL certificate.

Start taking back your day.

We built The Hub by GoDaddy Pro to save you time. Lots of time. Our members report saving an average three hours each month for every client website they maintain. Are you ready to take back that kind of time?

# data[].attributes.attachment_link.title
What is an SSL port? A technical guide for HTTPS

# data[].attributes.attachment_link.description
Secure Sockets Layer (SSL) is the technology responsible for data authentication and encryption for internet connections. It encrypts data being sent over the internet between two systems (commonly between a server and a client) so that it remains private. And with the growing importance of online privacy, an SSL port is something you should get familiar with.

# data[].attributes.body
TCP port: 80

Ref: https://bigbrassband.com/git-integration-for-jira/documentation/git-url-ports.html

# data[].attributes.attachment_link.description
If your Jira and Git servers are running through a firewall, configure the firewall to allow access using the URL schemes for git repositories. For authentication issues, make sure to check first the correct port for its connection.

# data[].attributes.body
TCP: 4070

UDP: 57621
Fonte: https://www.netify.ai/resources/protocols/spotify-synchronization-protocol

# data[].attributes.body
TCP: 5938, 443, 80

UDP: 5938
Fonte: https://community.teamviewer.com/English/kb/articles/4139-ports-used-by-teamviewer

# data[].attributes.body
TCP:  22, 33001

UDP: 33001
Fonte: https://partnerhelp.netflixstudios.com/hc/en-us/articles/115000257627-What-are-Netflix-s-IP-Addresses-and-Port-Ranges-

# data[].attributes.body
Cauê Silveira
Darlei Feix
Ghilherme Rocha
Henrique Vilela
Matheus Ribeiro

# data[].attributes.body
TCP: 20, 21

Referência: https://www.pearsonitcertification.com/articles/article.aspx?p=1868080