Python Django
The official Django middleware for the InternetData API.
New to InternetData? Make your first lookup
Getting Started
pip install internetdata-djangoRequires Python 3.11 or newer and Django 4.2 or newer.
Without an API key a lookup is on Unlimited, the free plan: the country, the network and the company behind the address, Tor, relay, anycast, carrier and satellite space and the service flags, with no daily or monthly cap. Every lookup your app makes comes from your server's one address, though, so a busy site will see bursts refused. A paid plan answers every field, VPN, the proxy flags, hosting, CDN and the city among them; create a key in the console. A free account tries every field.
Add it to MIDDLEWARE and configure it with an INTERNETDATA dict:
# settings.py
MIDDLEWARE = [
# ...
"internetdata_django.InternetDataMiddleware",
]
INTERNETDATA = {"api_key": os.environ.get("INTERNETDATA_API_KEY")}def index(request):
result = request.internetdata.result
country = result.location.country_name if result else "somewhere"
return HttpResponse(f"Hello, visitor from {country}")By default nothing is blocked. Every request gets a request.internetdata and your own code decides what it means: a currency to show, a sign-up to review, a page to keep from some countries.
A request your skip claims gets no answer, so it carries no request.internetdata. Wherever skip can apply, read the answer as lookup(request), imported from internetdata_django, which is None for such a request.
Blocking
Pass a block_condition and a matching request is answered with 403 and never reaches your views.
INTERNETDATA = {
"api_key": os.environ.get("INTERNETDATA_API_KEY"),
"block_condition": {"location": {"country": ["CU", "IR", "KP"]}},
}A condition is written in the shape of a result, keyed by the same names the API uses, and only the members you name are considered, so it can refuse on anything in the answer. The country works on every plan, and so do the first two of these:
{"asn": {"type": "hosting"}} # the network's type
[{"is_anycast": True}, {"is_satellite": True}] # anycast and satellite space
[{"is_hosting": True}, {"is_cdn": True}] # traffic from servers, not people
[{"is_vpn": True}, {"is_tor": True}, {"is_resproxy": True}] # anonymity: a list is OR
{"is_vpn": True, "vpn": {"provider": "nordvpn"}} # one provider
{"resproxy": {"hits": {"gte": 5}}} # a numeric thresholdValues are matched by equality, strings without regard to case. A list means any-of. A dict of gte/gt/lte/lt compares numbers, and every bound you give must hold, so two of them are a range. Members set to False or None are ignored, so a condition states the signals you act on; one that constrains nothing would match every request, and is refused when the middleware is built rather than silently blocking all your traffic.
Replace the refusal with on_blocked, which takes the request and the answer and returns a response:
INTERNETDATA = {
"api_key": os.environ.get("INTERNETDATA_API_KEY"),
"block_condition": {"location": {"country": ["CU", "IR", "KP"]}},
"on_blocked": lambda request, found: render(request, "unavailable.html", status=451),
}Blocking one view
block_condition applies to every view. To refuse a visitor on some views only, decorate them, sync or async:
from internetdata_django import block_if
@block_if({"location": {"country": ["CU", "IR", "KP"]}})
def checkout(request): ...block_if takes the same condition, on_blocked, fail_closed and on_missing_field. It judges the answer the middleware already attached, so a visitor is looked up once however many views check them, and it warns once for a member your plan doesn't include. A request skip claimed reaches the view. The middleware still has to be installed: without it, a decorated view raises ImproperlyConfigured instead of letting everyone through.
Where the client address comes from
This is the setting that decides whether any of the above works, and it is the one thing only you can get right.
By default the middleware uses REMOTE_ADDR, which is the socket peer. Django deliberately does not read X-Forwarded-For for you, because trusting a header without knowing your topology is unsafe. So if your app sits behind nginx, a load balancer, or a CDN, every visitor arrives wearing your proxy's address, and that is the address that gets looked up: every visitor gets your proxy's country and network, and if it is a hosting address, a hosting rule blocks everyone. nginx on the same machine is 127.0.0.1 and a load balancer usually has a private address, which the middleware answers locally without a lookup, as an address with no country, and logs a warning.
For an edge that writes the address into its own header, name the header:
from internetdata_django import header_ip_selector
INTERNETDATA = {
"api_key": os.environ.get("INTERNETDATA_API_KEY"),
"ip_selector": header_ip_selector("CF-Connecting-IP"), # or True-Client-IP, or your own
}xff_ip_selector() reads X-Forwarded-For directly. Be aware that the left-most entry is whatever the caller sent, because proxies append to that header, so it's only trustworthy when an edge you control overwrites it. If you know how many proxies sit in front, count from the right instead: xff_ip_selector(1) is the address your nearest proxy saw.
Anything else, pass your own callable. It receives the request and returns an address.
If the address resolves to a private one, the middleware says so once through the internetdata logger. That is expected on localhost and is the signal to fix your configuration anywhere else.
When a lookup fails
The request is let through, and the reason is recorded on the answer's error. Our outage should not become yours, so a network failure, a rate limit or a rejected key all fail open. Pass "fail_closed": True to block instead. Private addresses are answered locally and never fail, so this will not lock you out in development.
Cost and latency
Answers are cached for an hour, so a returning visitor costs nothing, and private addresses never leave the process. A cache miss is one request to our API, bounded at 2.5 seconds by default and not retried: on a request path, failing open quickly beats holding a visitor while we try again. Both are adjustable with timeout and retries, and the cache through an InternetData client you build yourself and pass as client.
Skip what you do not care about, or must never refuse:
"skip": lambda request: request.path.startswith("/webhooks/"),A webhook comes from its sender's servers, an address a hosting rule would refuse. Static files need no skip: runserver, WhiteNoise and a web server in front each answer them before this middleware runs.
Beyond a few million distinct visitors a day, stop calling the API per request: look addresses up locally in our databases instead.
Absent is not false
Unlimited, with a key or without one, leaves out is_vpn, is_hosting, is_cdn and the four proxy flags, the detail behind them, and the paid members inside location, asn, company and abuse, such as location.city. A field your plan does not include is None, which means "not in your plan" rather than "checked, and no".
request.internetdata.result.flagged("is_vpn") # False rather than None on a plan without itA block_condition naming a member your plan does not serve, location.city on Unlimited included, can never match, so the middleware warns once instead of failing silently. Pass "on_missing_field": "raise" to make it an error.