AEGIS v3.9.3 — CLEAN LINK CONTROL ================================== ADAPTIVE ACCESS UPDATE - Low-risk sessions use the normal loading flow and continue automatically. - Uncertain sessions use the neutral Continue confirmation step. - Explicit automation headers and confirmed abuse remain blocked. - Coarse browser telemetry is session-bound and is not used for persistent tracking. - All successful visitors resolve to the same configured destination. STABLE ADMIN-MANAGED PATHS - Only Admin may edit a user's canonical public path after account creation. - The previous path remains active by default for links already sent. - New token links immediately use the new canonical path. - Existing tokens work on retained legacy paths without regeneration. - Route collision checks, path history, automatic route refresh, and rollback-safe aliases added. MODERN LOADING GATES - Every adaptive gate now uses a softly blurred skeleton-page background. - Percentage flow styles include ring, bar, counter, floating pill, and corner status. - The gate appearance is stable per public path and token. - PASSIVE/MANUAL decisions, proof checks, telemetry, routing, and security settings are unchanged. PER-USER GATE BEHAVIOR - Users may select Adaptive, Loading Only, or Always Confirm from their dashboard. - Loading Only affects presentation only after the backend returns ALLOW. - Always Confirm may add a manual confirmation but cannot weaken a backend decision. - Backend CHALLENGE and DENY decisions, proof checks, telemetry enforcement, rate limits, cooldowns, and failure memory always take priority. - Admin can see each user's selected gate behavior. RECIPIENT EMAIL AUTOFILL - Accepts recipient email values from the query keys email, e, t, target, and a. - Only a valid email address up to 254 characters is accepted; arrays, unresolved merge tags, and other values are ignored. - The validated value is bound to the verification session and forwarded only after verification succeeds. - The destination receives the email under its existing supported key, or the canonical email key when none exists. - Recipient email values are not added to AEGIS visitor logs. LOG VIEW UPDATE - User visitor logs hide repetitive RATE_CONTROL block rows only. - User logs continue to show LANDING, CONFIRMED, and all other BLOCK reasons. - Admin logs retain every record, including RATE_CONTROL entries. - Admin log view now defaults to 500 records per page, supports up to 1,000, and provides complete Older/Newer pagination with server-side stage filters. GATE DESIGN UPDATE - Replaced the spinner-only page with a clear, neutral confirmation gate. - Added a responsive white-card layout and accessible link icon. - Continue stays disabled until the existing verification finishes. - Nonce, proof, session, IP/browser binding, and one-use release ticket are unchanged. PRIMARY FLOW - The primary public link is https://domain.com/email. - NEW: Admin assigns each user a unique public path during account creation. - NEW: One domain can serve multiple users with separate destinations through hostname + path routing. - The original website at https://domain.com/ remains untouched. - One hostname is assigned to one AEGIS user. - The user saves a Destination URL and Public Domain URL. - Folder paths are removed from the saved public URL. OPTIONAL ALIASES - Each Generate click creates one optional token link. - The selector controls token character length from 5 through 20. - Example: length 5 => /email/87HBA. - Example: length 10 => /email/8JVSAQ231WA. - Alias format: https://domain.com/email/XXXXXXXXXX - Aliases expire after 14 days and may be revoked from the dashboard. - Existing token_index records remain readable when they meet current validation. ADMIN IP ANALYTICS - One IP2Location API key is stored in Admin for the whole installation. - User dashboards do not expose the key. - City, ISP, ASN and network type enrich LANDING, BLOCK and CONFIRMED logs. - Successful lookups are cached for 24 hours; temporary failures for 15 minutes. - Location/ISP fields enrich logs. Normalized network-risk indicators feed the same balanced access policy for every visitor; no alternate destination exists. BALANCED NETWORK POLICY - Standard networks keep the normal five-second Continue flow. - DCH, VPN, proxy and datacenter indicators trigger proof-of-work. - Confirmed TOR, botnet and bogon indicators are denied. - Trusted VPN/RDP IPs and CIDRs are managed from Admin. - A successful POST creates a one-use release ticket that expires in 30 seconds and is bound to the same browser session and IP. - The destination remains server-side until the release ticket is accepted. - Logs include access_decision, proof_result and decision_reason. - Scanner/crawler-specific fields are not used for alternate treatment. ADAPTIVE ABUSE CONTROL - Admin presets: Normal, Balanced and Strict. - Configurable landings per IP per 10 minutes. - Configurable destination releases per IP per 10 minutes. - Configurable verification-failure threshold and penalty duration. - Configurable token requests per minute and token cooldown duration. - Configurable DCH and escalated proof difficulty. - Token surge cooldown affects only the token that surged. - Browser, IP, session, nonce and ticket continuity are enforced. UNIFORM FIRST-PARTY VERIFICATION - Every visitor receives the same landing page and validation rules. - The page waits five seconds, then reveals a Continue button. - Continue uses POST, a session cookie and a single-use nonce. - Nonces expire after ten minutes and cannot be reused. - Direct POST requests, invalid aliases and excessive requests are rejected. - The destination URL is resolved server-side only after verification. REMOVED FROM THE PUBLIC FLOW - Automatic no-click redirect. - Random/fixed landing rotation. - IP/ASN/VPN classification and scanner-specific destinations. - Legacy /u/USERNAME/ public gate folders. INSTALLATION - Open the admin dashboard and click Install Email Route. - AEGIS detects root, folder and nested-folder installations automatically. - The existing document-root .htaccess is backed up before changes. - A marked AEGIS block is inserted above CMS rules and refreshed without duplicates. - ROOT_BRIDGE_FOR_FOLDER_INSTALL.txt remains available only as a permission fallback. BACK UP users_data/ and config/ before replacing an existing installation.