Serve WordPress cleanly over .onion with URL rewriting, Onion-Location, and privacy hardening.

Adam Szokol

Onion Service by Adam Szokol

A focused plugin designed to enable Onion Service & Mapping support for your WordPress site.

Ivijan-Stefan Stipic

INFINITUM FORM

Onionify is an independent plugin that enables WordPress websites to operate seamlessly through onion services (.onion).
This plugin is not affiliated with or endorsed by the Tor Project.
Onionify adds safe and standards-compliant integration for onion access – rewriting runtime URLs when requests arrive via .onion, preventing canonical redirects that might expose onion visitors to the clearnet, optionally adding the official Onion-Location HTTP header, and applying additional privacy-hardening measures (CSP, COEP, oEmbed and resource hints control) specifically for onion traffic.
The plugin follows WordPress.org guidelines and is designed for secure public distribution:
<ul>
<li>No modifications to WordPress core.</li>
<li>Uses WordPress filters and actions only.</li>
<li>Fully compatible with multisite environments (per-site mappings and network defaults).</li>
<li>Optional WP-CLI integration for advanced administration.</li>
</ul>
<h3>⚠ IMPORTANT WARNING</h3>
⚠ Warning: This plugin does not provide hosting-level anonymity or concealment of infrastructure. Onionify helps WordPress handle requests that arrive via onion service addresses, but it does not change or hide server configuration, hosting provider information, or other infrastructure-level metadata. If you require infrastructure-level protections or specialized operational procedures, consult authoritative technical documentation and qualified operational security professionals. Do not rely on this plugin for legal compliance or for anonymizing hosting details.
<h3>Features</h3>
<ul>
<li>Detects .onion requests and safely rewrites generated WordPress URLs to the configured onion host at runtime.</li>
<li>Does not modify database <code>home</code> or <code>siteurl</code> values – all rewrites occur at runtime only.</li>
<li>Multisite support: per-site onion mapping (via Network Admin) and configurable Network Defaults.</li>
<li>Optionally sends the Onion-Location header from the clearnet site to help browsers recognize the onion mirror.</li>
<li>Optional privacy enhancements for onion visitors (CSP, COEP, X-Frame-Options, disable oEmbed, and tighten resource hints).</li>
<li>Optional verification feature using a public list of known Tor exit addresses (opt-in only).</li>
<li>Includes WP-CLI commands to list, map, and manage onion host configurations.</li>
<li>Provides filter hooks for extensibility (including <code>onion_is_onion_request</code> and <code>onion_verify_exit_list</code>).</li>
<li>Carefully validated, defensive code compatible with PHP 7.4 – 8.x.</li>
</ul>
<h3>Quick usage (WP-CLI)</h3>
<ul>
<li><code>wp tor-onion list</code> – show mapping table (multisite) or single-site status.</li>
<li><code>wp tor-onion map <blog_id|0> <example.onion></code> – map blog_id (or 0 for single-site) to an onion host.</li>
<li><code>wp tor-onion set --hardening=on|off --oembed=on|off --csp=strict|relaxed|off</code> – quick toggles.</li>
</ul>
<h3>Settings explained (concise + clear)</h3>
<ul>
<li>.onion domain – Host only, no protocol. Example: <code>abcd1234xyz.onion</code>. Leave empty to use Network Default (multisite).</li>
<li>Send Onion-Location from clearnet – When enabled, the plugin adds an <code>Onion-Location: http://<your-onion><path></code> header to requests on the clearnet site. This is useful to advertise your onion mirror to Tor Browser or other clients.</li>
<li>Enable onion hardening – When enabled, headers and filters designed to reduce external resource loading (and privacy leakage) are applied to requests only when served via .onion.</li>
<li>Disable oEmbed/embeds on .onion – Blocks automatic fetching of oEmbed content (YouTube, Twitter, etc.) and discovery links to avoid loading third-party resources for onion visitors.</li>
<li>CSP mode – <code>Strict</code>, <code>Relaxed</code>, <code>Off</code>, <code>Custom</code>.
<ul>
<li>Strict – safest. No inline scripts. Best for privacy; may break themes/plugins that rely on inline JS.</li>
<li>Relaxed – allows inline scripts/styles (<code>'unsafe-inline'</code>), useful for older themes.</li>
<li>Off – plugin does not send a CSP header.</li>
<li>Custom – plugin will send exactly the policy you place into the Custom CSP text box. Only use if you understand CSP syntax.</li>
</ul>
</li>
</ul>
<h3>Custom CSP – clear guidance</h3>
<ul>
<li>The Custom CSP field is used only when <code>CSP mode</code> is set to Custom.</li>
<li>Enter the policy exactly as you want it sent. Examples below – copy/paste if needed:</li>
</ul>
1) Minimal secure WordPress (no external CDN): 
 <code>default-src 'self'; 
script-src 'self'; 
style-src 'self' 'unsafe-inline'; 
img-src 'self' data:; 
font-src 'self' data:; 
connect-src 'self'; 
frame-src 'self'; 
frame-ancestors 'self'; 
base-uri 'self'; 
form-action 'self';</code>
2) Relaxed (allows inline JS): 
 <code>default-src 'self'; 
script-src 'self' 'unsafe-inline'; 
style-src 'self' 'unsafe-inline'; 
img-src 'self' data:; 
font-src 'self' data:; 
connect-src 'self'; 
frame-src 'self';</code>
3) If you must use an external CDN – add only the exact host(s): 
 <code>img-src 'self' https://cdn.example.com data:; 
font-src 'self' https://cdn.example.com data:;</code>
Tips & cautions: 
– Start with Strict; if things break (admin bar, theme JS), switch to Relaxed. 
– Use Custom only if you know CSP; incorrect CSP can break admin, media, or login. 
– Avoid including public CDNs in onion mode where possible – best privacy practice is to host assets locally.
<h3>Multisite behavior</h3>
<ul>
<li>Per-site mapping: Network Admin → Onionify allows mapping each blog_id → onion host.</li>
<li>Network Defaults: Network Admin → Onionify → Network Defaults lets you set default values (default onion host, default CSP mode, default hardening toggles) that sites inherit unless they override locally.</li>
<li>Precedence: Per-site explicit setting → Network Default → Plugin internal default.</li>
</ul>
<h3>Filters & constants (developer)</h3>
<ul>
<li><code>apply_filters('onion_is_onion_request', bool $is_tor, array $server)</code> 
Allows other plugins/themes to override detection. <code>$server</code> is a copy of <code>$_SERVER</code>.</li>
<li><code>apply_filters('onion_verify_exit_list', bool $default)</code> 
Controls whether the plugin will verify IPs against the Tor exit list. Disabled by default.</li>
<li><code>define('TOS_VERIFY_TOR_EXIT', true);</code> – alternative to enable exit-list verification in <code>wp-config.php</code>.</li>
<li><code>onion_support_*</code> option names used by the plugin: see Settings page. The plugin cleans up these options on uninstall.</li>
</ul>
If you do not want automatic cleanup, do not use the admin “Delete” action; deactivate only.
<h3>Privacy, security, and limitations (be explicit)</h3>
<ul>
<li>This plugin only adjusts WordPress behavior (URL outputs, selected headers, CSP, and resource hint handling) based on how visitors access the site (clearnet vs .onion).</li>
<li>It does not anonymize or conceal server infrastructure details. Information such as hosting provider IP addresses, DNS records for clearnet domains, or other infrastructure-level metadata remains unchanged. Onionify is not designed or intended to provide anonymity or infrastructure concealment.</li>
<li>Enabling the optional exit-address verification feature performs external HTTP requests to a trusted public source (only when explicitly opted in). If your hosting environment restricts outbound HTTP requests, use the WP-CLI interface or <code>wp-config.php</code> configuration after verifying your allowed hosts.</li>
<li>The plugin operates with a privacy-first design: external requests are disabled by default, and its default configuration aims to reduce unnecessary third-party requests for onion visitors.</li>
</ul>
<h3>External services</h3>
This plugin can optionally fetch the official Tor exit relay list to verify requests against Tor exits.
Service: Tor Project – Exit addresses list 
Endpoint: https://check.torproject.org/exit-addresses
What it is used for: When exit verification is enabled, the plugin downloads the public list of Tor exit relays to check inbound requests.
What data is sent and when: The plugin performs a normal HTTP GET request from the server to the Tor Project endpoint. No user PII is sent; the request includes a generic User-Agent header and, as with any HTTP request, the server’s IP address is visible to the Tor Project. This request happens at most once per 24 hours due to caching and only if exit verification is enabled by the site owner.
How to enable/disable: Exit verification is opt-in. It is disabled by default. It can be enabled via the plugin settings or by adding define(‘TOS_VERIFY_TOR_EXIT’, true) in wp-config.php. If your environment blocks external HTTP requests (WP_HTTP_BLOCK_EXTERNAL), the plugin will respect that unless the host is whitelisted in WP_ACCESSIBLE_HOSTS.
Provider policies: See the <a href="https://www.torproject.org/about/privacy_policy/" rel="nofollow ugc">Tor Project privacy policy</a> and terms on their official website.
<h3>Support</h3>
Use the WordPress.org support forum for the plugin. For commercial help or customizations contact https://infinitumform.com/.

Alternatives to Onionify

Top alternatives