Security
Tenant isolation
Every workspace's data is protected by PostgreSQL Row Level Security keyed on membership. Server code additionally scopes every query to the active workspace, and privileged operations re-check authorization before using elevated credentials.
Role-based access
Owner, Admin and Member roles are enforced in the database (policies and column-level grants), not just hidden in the interface. Audit logs record security-relevant actions.
SSRF protection
Targets must be http(s) on ports 80/443/8080/8443. Hostnames are resolved by Aegis, and the connection is pinned to an address that has been checked against private, loopback, link-local, multicast, reserved and metadata ranges. Each redirect is re-validated and re-resolved; requests have timeouts, size limits, a redirect cap and a concurrency limit.
Ownership verification
Scans and subdomain discovery only run after the workspace proves control of the domain via DNS TXT or a file under /.well-known/.
Safe testing only
No brute force, credential testing, exploit payloads or destructive requests. Checks are read-only GET requests, one TLS handshake and public DNS lookups. Scans are rate-limited per workspace.
Honest results
Findings require observed evidence. Uncertain observations are labelled with lower confidence and softer language. The Aegis Security Score is an internal posture indicator — never presented as a certification.
Would Aegis scan this?
Type any address. This runs Aegis's real server-side target validation (static rules only — nothing is fetched) and shows exactly why a target would be accepted or blocked.