Hi! Here is a link https://www.dynatrace.com/support/help/deploy-dyn...
Please check the last section
Is that what you need ?
Your Dynatrace Managed clusters must be able to communicate with Mission Control (URL:
https://mcsvc.dynatrace.com1 and IP addresses:
188.8.131.52) via HTTPS (
for license validation, health monitoring, and automatic updates.
Communication between Dynatrace Managed clusters and Mission Control is
based on TLS v1.2.
To enable health monitoring, your Dynatrace Managed Server must also have access to
*.live.dynatrace.com (IP addresses
184.108.40.206) via HTTPS (
Roberta, Radoslaws response is for those running a Managed onpremise instance of Dynatrace. If you are using a SaaS tenant of Dynatrace, it depends on which data center your tenant is located. So if you have further questions, please be sure to clarify whether you're asking about a Managed instance or a SaaS instance.
To enable health monitoring, your Dynatrace Managed Server must also have access to *.live.dynatrace.com (IP addresses 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, and 188.8.131.52) via HTTPS (port 443).
Why not list those domain and IPs in the official documentation?
For a SaaS instance, the IP address varies depending on your instance location. To find your personal IP addresses, select the Deploy Dynatrace -> Start Installation -> select your platform, and at the bottom of the page will be a list of your IPs.
IP addresses are automatically identified from the HTTP headers of web requests and the Dynatrace Real User Monitoring signal. However, when load balancers, CDNs, or proxies are used, the remote IP of the HTTP(S) request might be different from the original IP address from your end users' devices. For such cases, Dynatrace watches the HTTP headers most frequently used for identifying the originating IP address of a client connecting to a web server through an HTTP proxy, a CDN or a load balancer. To view which headers Dynatrace watches by default, go to Global Settings > Web & mobile monitoring -> IP determination. These headers are processed in a specific order.