---
url: 'https://docs.smoxy.eu/developer-guide/geoip-headers.md'
---
# GeoIP Headers

When smoxy forwards a request to your origin server, it automatically adds HTTP headers carrying geolocation and network metadata derived from the client's IP address. Use these headers to personalize content, switch languages, enforce regional compliance, or feed your analytics - without performing any IP lookups in your backend.

***

### Available Headers

| Header           | Description                                           | Example            |
| ---------------- | ----------------------------------------------------- | ------------------ |
| `s-country`      | ISO 3166-1 alpha-2 country code                       | `DE`, `US`         |
| `s-city`         | Approximate city                                      | `Berlin`           |
| `s-subdivisions` | ISO 3166-2 region/subdivision code                    | `DE-BY`            |
| `s-latitude`     | Approximate latitude                                  | `52.5200`          |
| `s-longitude`    | Approximate longitude                                 | `13.4050`          |
| `s-iseu`         | Whether the client is in the EU (`1` = yes, `0` = no) | `1`                |
| `s-asn`          | Autonomous System Number of the client's network      | `13335`            |
| `s-asorg`        | Organization name for the ASN                         | `Cloudflare, Inc.` |

All headers are added automatically to every request - no configuration needed.

***

### Use Cases

#### Language switching

Use `s-country` to serve content in the visitor's language, or redirect to a localized storefront.

#### Regional compliance

Use `s-iseu` to apply GDPR-specific cookie consent banners only for EU visitors.

#### Geo-targeted content

Use `s-country` or `s-subdivisions` to show region-specific pricing, promotions, or shipping options.

#### Analytics

Log `s-country` and `s-city` to understand where your traffic comes from without relying on client-side analytics.

#### Access control

Combine GeoIP headers with [Access Rules](/rules/access-rules) or [Conditional Rules](/rules/conditional-rules) to restrict or modify behavior by region.