Restricted Site Access

Purpose: Restricting public access to a WordPress site for use as an extranet, intranet, or staging environment while providing controlled access methods.

Inferred · not functionally tested

Audience: WordPress administrators managing private or semi-private sites

Inferred · not functionally tested

Functions: Unknown

Interfaces: API: unknown · MCP: unknown · CLI: unknown · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: free · license: GPL-2.0 · platforms: WEB · deployment: browser, self_hosted

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: wordpress.org · wordpress.org. These links do not verify the individual claims.

In the Website firewall, bot & spam protection space, Restricted Site Access takes a focused approach. Inferred · not functionally tested: It focuses on restricting public access to a WordPress site for use as an extranet, intranet, or staging environment while providing controlled access methods. Inferred · not functionally tested: Restricted Site Access is a consumer product aimed at wordPress administrators managing private or semi-private sites. Basis unknown · not verified: Restricted Site Access is free to use. Basis unknown · not verified: It ships for the web, and it can be self-hosted.

10up builds and maintains Restricted Site Access, and it first shipped in 2009. Development happens publicly on GitHub with 247 stars and 69 commits in the last 90 days. Inferred · not functionally tested: Among its 4 catalogued features are IP Restriction, Login Redirect, and Custom Messages. The interface is available in English, Gujarati, and Dutch.

Summary written by a language model from the project’s public pages.