International Sanctions Compliance & Iran Regional Defense
Global digital publishing software must adhere strictly to statutory export controls, international trade embargoes, and financial sanctions. Version 5.3.1 expanded Open Publisher's application-layer geographic defense engine to enforce full access restrictions on connections originating from the Islamic Republic of Iran (IR) alongside the Russian Federation (RU). This release establishes automated multi-tier geographic interception in strict compliance with United States OFAC regulations, European Union Council directives, and UK statutory sanctions.
Connections originating from sanctioned territories are intercepted before application startup with bilingual compliance notices.
Statutory Obligations & Compliance Context
Client-side web software distributed globally must operate in full conformity with regulatory frameworks:
International Trade Controls: Under OFAC, EU, and UK sanctions, software platforms are legally prohibited from exporting or facilitating technical services to sanctioned state entities and jurisdictions.
Infrastructure Protection: Automated scraping, unauthorized proxy rotation, and abusive batch workloads originating from restricted IP ranges are halted before consuming server or client resources.
Distinction Between State & People: While enforcing legal compliance, the restriction screen expresses clear solidarity with universal human rights, civil liberties, and fundamental freedoms.
Multi-Tiered Interception Architecture
The defense system in extensions/geo-defense.js executes at the very top of the document head:
Cloudflare Edge CDN Trace: Queries /cdn-cgi/trace during early bootstrap. If the authoritative country code evaluates to loc=IR or loc=RU, the application terminates execution immediately before any stylesheets, fonts, or templates load.
Redundant Public Geolocation: If edge trace data is unreachable, the engine falls back asynchronously to secondary geolocation services (https://api.country.is/).
Timezone & Persian Locale Heuristics: Audits host telemetry against Iranian timezones (Asia/Tehran, Iran) and Persian language preferences (fa, fa-IR, pes), intercepting connections that leak host environment data through local proxy tunnels.
Session & Local Storage Persistence: Sets persistent flags (op_ir_blocked = '1') so subsequent page reloads engage the restriction screen instantaneously without redundant network lookups.
Bilingual Sanctions Notice Card
When engaged, the entire document DOM is replaced with a standalone compliance screen featuring the Iranian tricolor flag (Green, White, Red), bilingual English and Persian legal text detailing statutory compliance, and a dedicated solidarity footer.
Note: Enterprise administrators can verify compliance rules or simulate regional restrictions using developer audit tools in the system console.