| title | intro | redirect_from | versions | topics | shortTitle | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
About GitHub's IP addresses |
{% data variables.product.github %} serves applications from multiple IP address ranges, which are available using the API. |
|
|
|
GitHub's IP addresses |
You can retrieve a list of the IP addresses for {% data variables.product.prodname_dotcom_the_website %} from the meta API endpoint. For more information, see AUTOTITLE.
{% ifversion ghec %}
If you access {% data variables.product.github %} on a subdomain of {% data variables.enterprise.data_residency_site %}, the meta endpoint does not return IP ranges for your subdomain. See AUTOTITLE.
{% endif %}
Note
The list of {% data variables.product.prodname_dotcom %} IP addresses returned by the Meta API is not intended to be an exhaustive list. For example, IP addresses for some {% data variables.product.prodname_dotcom %} services might not be listed, such as LFS or {% data variables.product.prodname_registry %}.
These IP addresses are used by {% data variables.product.prodname_dotcom %} to serve our content, deliver webhooks, and perform hosted {% data variables.product.prodname_actions %} builds.
These ranges are in CIDR notation. You can use an online conversion tool to convert from CIDR notation to IP address ranges, for example: CIDR to IPv4 conversion site.
We make changes to our IP addresses from time to time. We do not recommend allowing by IP address, however if you use these IP ranges we strongly encourage regular monitoring of our API.
For applications to function, you must allow TCP ports 22, 80, and 443 via our IP ranges for github.com.