Skip to main content
IP Intelligence provides you with additional information about any IP address you see in ngrok. It includes Autonomous System information, Geolocation data, as well as information fetched from 3rd parties that list IP address for blocklists or allowlists. See the full list of IP Categories available here. These variables can be used in Traffic Policy expressions, or they can be used to enrich your traffic via dynamic injection into headers or responses.

Client IP Intelligence

The following variables are available under the conn.client_ip namespace:

conn.client_ip.categories

The list of categories that classify the conn.client_ip. Check out our full list of categories.

conn.client_ip.is_on_blocklist

true when the conn.client_ip appears on one of the curated IP reputation blocklists ngrok trusts. These are blocklists with low false-positive rates, suitable for blocking traffic on the critical path. This is a convenience shortcut equivalent to checking conn.client_ip.categories for any blocklist category.

conn.client_ip.is_tor_node

true when the conn.client_ip is a known Tor exit node. This is a convenience shortcut equivalent to checking 'proxy.anonymous.tor' in conn.client_ip.categories.

Client IP Autonomous System

The following variables are available under the conn.client_ip namespace:

conn.client_ip.as.number

The Autonomous System Number of the conn.client_ip.

conn.client_ip.as.organization

The Autonomous System Organization name of the conn.client_ip.

Client IP Geo Location

This is the location where the IP address is located, which may be different from where the IP address is registered. For more details, see the MaxMind documentation.

conn.client_ip.geo.location.city

The name of the city, in EN, where the conn.client_ip is likely to originate.

conn.client_ip.geo.location.continent

The name of the continent, in EN, where the conn.client_ip is likely to originate.

conn.client_ip.geo.location.country

The name of the country, in EN, where the conn.client_ip is likely to originate.

conn.client_ip.geo.location.country_code

The two-letter ISO country code where the conn.client_ip is likely to originate.

conn.client_ip.geo.location.is_eu

Determines if the conn.client_ip is in the EU. Helpful for GDPR compliance.

conn.client_ip.geo.location.latitude

The approximate latitude where the conn.client_ip is likely to originate.

conn.client_ip.geo.location.longitude

The approximate longitude where the conn.client_ip is likely to originate.

conn.client_ip.geo.location.metro_code

The metro code where the conn.client_ip is likely to originate.

conn.client_ip.geo.location.postal_code

The postal code where the conn.client_ip is likely to originate.

conn.client_ip.geo.location.radius

The radius in kilometers around the latitude and longitude where the conn.client_ip is likely to originate.

conn.client_ip.geo.location.subdivision

The name of the subdivision, in EN, where the conn.client_ip is likely to originate.

conn.client_ip.geo.location.timezone

The name of the timezone where the conn.client_ip is likely to originate.

Client IP Registered Geo Location

This is the location where the IP address is registered, which may be different from where the IP address is located. For more details, see the MaxMind documentation.

conn.client_ip.geo.registered_location.city

The name of the city, in EN, where the conn.client_ip is registered.

conn.client_ip.geo.registered_location.continent

The name of the continent, in EN, where the conn.client_ip is registered.

conn.client_ip.geo.registered_location.country

The name of the country, in EN, where the conn.client_ip is registered.

conn.client_ip.geo.registered_location.country_code

The two-letter ISO country code where the conn.client_ip is registered.

conn.client_ip.geo.registered_location.is_eu

Determines if the conn.client_ip is in the EU. Helpful for GDPR compliance.

conn.client_ip.geo.registered_location.subdivision

The name of the subdivision, in EN, where the conn.client_ip is registered.

conn.client_ip.geo.registered_location.metro_code

The metro code where the conn.client_ip is registered.

conn.client_ip.geo.registered_location.timezone

The name of the timezone where the conn.client_ip is registered.

Server IP Intelligence

The following variables are available under the conn.server_ip namespace:

conn.server_ip.categories

The list of categories that classify the conn.server_ip. Check out our full list of categories.

conn.server_ip.is_on_blocklist

true when the conn.server_ip appears on one of the curated IP reputation blocklists ngrok trusts. These are blocklists with low false-positive rates, suitable for blocking traffic on the critical path. This is a convenience shortcut equivalent to checking conn.server_ip.categories for any blocklist category.

conn.server_ip.is_tor_node

true when the conn.server_ip is a known Tor exit node. This is a convenience shortcut equivalent to checking 'proxy.anonymous.tor' in conn.server_ip.categories.

Server IP Autonomous System

conn.server_ip.as.number

The Autonomous System Number of the conn.server_ip.

conn.server_ip.as.organization

The Autonomous System Organization name of the conn.server_ip.

Server IP Location Geo

This is the location where the server IP address is located, which may be different from where the IP address is registered. For more details, see the MaxMind documentation.

conn.server_ip.geo.location.city

The name of the city, in EN, where the conn.server_ip is likely to originate.

conn.server_ip.geo.location.continent

The name of the continent, in EN, where the conn.server_ip is likely to originate.

conn.server_ip.geo.location.country

The name of the country, in EN, where the conn.server_ip is likely to originate.

conn.server_ip.geo.location.country_code

The two-letter ISO country code where the conn.server_ip is likely to originate.

conn.server_ip.geo.location.is_eu

Determines if the conn.server_ip location is in the EU. Helpful for GDPR compliance.

conn.server_ip.geo.location.latitude

The approximate latitude where the conn.server_ip is likely to originate.

conn.server_ip.geo.location.longitude

The approximate longitude where the conn.server_ip is likely to originate.

conn.server_ip.geo.location.metro_code

The metro code where the conn.server_ip is likely to originate.

conn.server_ip.geo.location.postal_code

The postal code where the conn.server_ip is likely to originate.

conn.server_ip.geo.location.radius

The radius in kilometers around the latitude and longitude where the conn.server_ip is likely to originate.

conn.server_ip.geo.location.subdivision

The name of the subdivision, in EN, where the conn.server_ip is likely to originate.

conn.server_ip.geo.location.timezone

The name of the timezone where the conn.server_ip is likely to originate.

Server IP Registered Location Geo

This is the location where the server IP address is registered, which may be different from where the IP address is located. For more details, see the MaxMind documentation.

conn.server_ip.geo.registered_location.city

The name of the city, in EN, where the conn.server_ip is registered.

conn.server_ip.geo.registered_location.continent

The name of the continent, in EN, where the conn.server_ip is registered.

conn.server_ip.geo.registered_location.country

The name of the country, in EN, where the conn.server_ip is registered.

conn.server_ip.geo.registered_location.country_code

The two-letter ISO country code where the conn.server_ip is registered.

conn.server_ip.geo.registered_location.is_eu

Determines if the conn.server_ip is in the EU. Helpful for GDPR compliance.

conn.server_ip.geo.registered_location.subdivision

The name of the subdivision, in EN, where the conn.server_ip is registered.

conn.server_ip.geo.registered_location.metro_code

The metro code where the conn.server_ip is registered.

conn.server_ip.geo.registered_location.timezone

The name of the timezone where the conn.server_ip is registered.

IP Categories

The following categories are available to use with the IP Intelligence .categories list. The categories are hierarchal and can be matched at any level needed. For example, an IP with the category of com.cloudflare.ipv4 also has the categories com and com.cloudflare. This can be helpful if you want to allow all IPs from Cloudflare using com.cloudflare which would have both ipv4 and ipv6 lists. Here’s an example of how to block Tor exit node IPs from accessing your endpoint.
Or you can block all anonymous proxies which would include Tor as well as any other lists with the proxy.anonymous category.

Blocklists

Proxies / VPNs

Public lists

Organizations

Ahrefs

Algolia

Amazon Web Services (AWS)

Anthropic

Apple

Atlassian

Babbar

BetterStack

Bing (Microsoft)

Brevo

Bunny CDN

Censys

Cloudflare

Common Crawl (CCBot)

Criteo

DigitalOcean

Datadog

Delinea

DuckDuckGo

Fastly

Firehol

Github

GitLab

Google

IBM

Linode (Akamai)

Meta (Facebook)

Microsoft Azure

Microsoft Office

Okta

OpenAI (ChatGPT)

Oracle

Pagerduty

Perplexity AI

Pingdom

Plaid

RingCentral

RSS API

Salesforce

Semrush

Stripe

Svix

Telegram

Teleport

Telnyx

UptimeRobot

Vultr

WebPageTest

X (Twitter)

Yandex

Zendesk

Zoom

Zscaler