Drupal is a registered trademark of Dries Buytaert
cms 2.1.3 Update released for Drupal core (2.1.3)! drupal 10.5.11 Update released for Drupal core (10.5.11)! drupal 11.3.11 Update released for Drupal core (11.3.11)! drupal 11.2.13 Update released for Drupal core (11.2.13)! drupal 10.6.10 Update released for Drupal core (10.6.10)! cms 2.1.2 Update released for Drupal core (2.1.2)! drupal 11.1.10 Update released for Drupal core (11.1.10)! drupal 10.5.10 Update released for Drupal core (10.5.10)! drupal 10.4.10 Update released for Drupal core (10.4.10)! drupal 11.2.12 Update released for Drupal core (11.2.12)! drupal 11.3.10 Update released for Drupal core (11.3.10)! drupal 10.6.9 Update released for Drupal core (10.6.9)! drupal 10.6.8 Update released for Drupal core (10.6.8)! drupal 11.3.9 Update released for Drupal core (11.3.9)! drupal 11.3.8 Update released for Drupal core (11.3.8)! drupal 11.3.7 Update released for Drupal core (11.3.7)! drupal 11.2.11 Update released for Drupal core (11.2.11)! drupal 10.6.7 Update released for Drupal core (10.6.7)! drupal 10.5.9 Update released for Drupal core (10.5.9)! cms 2.1.1 Update released for Drupal core (2.1.1)!

pagegeofence

67 sites Security covered
View on drupal.org

This module ensures that designated website pages cannot be accessed or viewed from specific geographic locations, using geolocation country code provided by a customizable request header. The header name can be configured in the module settings, enabling compatibility with diverse environments and setups.

Key Features
Page-level Geofencing:
Enable geofencing restrictions on an individual page or for a page and its sub-pages (sub-paths).

Configurable Request Header:
Admins can specify the exact header name (e.g., HTTP_CF_IPCOUNTRY, X-Country-Code, etc.) that contains the relevant geolocation data.

Granular Restriction:
Allow or deny access based on selected countries/regions derived from the configurable request header.

Logging of Changes:
Time-stamped logs for all restriction configuration changes, including enabling/disabling, scope, affected countries, restriction type, and legal reasoning.

Default Behavior:
No geofencing by default; restrictions must be explicitly configured per page.

Legal Compliance:
Requires justification for any restriction applied for documentation purposes.

Activity

Total releases
3
First release
Oct 2025
Latest release
5 months ago
Release cadence
21 days
Stability
0% stable

Release Timeline

Releases

Version Type Release date
1.0.0-alpha3 Pre-release Dec 8, 2025
1.0.0-alpha2 Pre-release Oct 31, 2025
1.0.0-alpha1 Pre-release Oct 27, 2025