All mabl test traffic originates through a fixed set of IP addresses. By adding mabl's static IP addresses to a firewall allowlist, permitlist, or whitelist, you can give mabl access to non-public testing and production environments for cloud runs.
Static IP addresses are an alternative to mabl Link. If you desire a more secure solution to testing private environments behind a corporate firewall, read more about mabl Link.
Finding the IP addresses
Unless you have configured your tests to run over mabl Link, all cloud test traffic, webhook calls, and URL validation traffic will originate from the IP addresses listed on the networking page in the app: Settings > Networking.
Example of static IP addresses used by mabl browsers
The IP addresses are listed in CIDR block format. If your firewall doesn't use CIDR format, just drop the /28
from the address and use that in your firewall configuration.
Mabl uses the standard port for HTTPS / TLS (443
).
If your application under test is hosted by select Google Cloud Platform services, such as the following, traffic will appear to originate from the 0.0.0.0
address, because the test traffic will transit the internal Google Could network directly to your application.
- Google App Engine
- Google Cloud Run
- Google Cloud Functions
Current static IP addresses
As of this article being updated, mabl's static egress IPs are:
- 3.146.47.160/27
- 34.132.2.128/28
- 34.31.138.224/27
Keep in mind the latest IPs can be found by visiting the mabl app, as shown above.
Retired static IP addresses
Previously used egress IPs that are now retired are:
- 104.198.166.162/32 (RETIRED)
- 35.184.236.163/32 (RETIRED)
- 207.254.16.90/32 (RETIRED)
Retired egress IPs remain in the control of mabl for security purposes, but are no longer used for production mabl test traffic.
Communicating IP Address Changes
If mabl adds or removes static IP addresses, the change will be communicated via:
- the Friends of mabl Slack team
- the Release Notes
- the networking page in the app: Settings > Networking
Limitations
- Executing mabl tests locally with the mabl CLI will originate from their local host
- Private static IP addresses are not yet available on a per workspace/customer basis
- As mabl grows, more origin IPs may be added. Advance notice will be provided via mabl status where you can subscribe for update notifications.