> For the complete documentation index, see [llms.txt](https://learn.mechanic.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.mechanic.dev/faq/what-ip-address-does-mechanic-use.md).

# What IP address does Mechanic use?

In general, Mechanic uses dynamically-assigned IP addresses, and does not support static or fixed IP addresses for outgoing or inbound requests.

## HTTP actions

The [HTTP action](/core/actions/http.md) supports HTTPS, HTTP, and SOCKS5 proxies, allowing you to set up your own proxy server with a static IP address, passing your Mechanic requests through it. Using this strategy, you can control the client IP addresses used for your outbound requests. This can be useful for API vendors that have IP address restrictions. Learn more: [Actions / HTTP / Using a proxy](/core/actions/http.md#using-a-proxy).

## Outbound email

Mechanic itself doesn't offer any guarantees about IP addresses used for outgoing mail. However, in practice, our email provider Postmark does offer such a list:\
​\
​<https://postmarkapp.com/support/article/800-ips-for-firewalls#outbound>\
​\
Mechanic doesn't offer any representation of Postmark's commitment to those addresses. While it's unlikely, the possibility exists that Mechanic would use another email provider (with different IPs) in the future.

{% hint style="info" %}
Mechanic works with Postmark to use DKIM message signing and Return-Path routes, both of which are strong signals for deliverability. The requisite DNS configuration for these features is part of validating any [custom email address](/platform/email/custom-email-domain.md) used in Mechanic.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://learn.mechanic.dev/faq/what-ip-address-does-mechanic-use.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.