zentinelproxy.io valid
Zentinel
A security-first reverse proxy built on Pingora: explicit configuration, bounded resources, and WAF and auth in isolated agents.
- Authority
- 45 reach 0 · trust 5 · quality 25 · freshness 15
- Tier
- listed
- llms.txt
- https://zentinelproxy.io/llms.txt
- llms-full.txt
- https://zentinelproxy.io/llms-full.txt
- Sections
- 5
- Links
- 42
- Size
- 12685 bytes
- Country
- — Publisher location unknown; CDN address excluded
- Country evidence
- No published address evidence collected yet
- For agents
- Documentation: developer or product docs worth reading, nothing to call
- First seen
- 2026-10-27T12:29:48.891Z
- Last checked
- 2026-10-27T12:29:50.481Z
- Badge
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-27T12:29:49.001Z. Cached copy · Source on zentinelproxy.io
# Zentinel
> A security-first reverse proxy built on Pingora: explicit configuration, bounded resources, and WAF and auth in isolated agents.
## What Zentinel is
Zentinel is a security-first reverse proxy built to guard the free web. It is written in Rust on Cloudflare's [Pingora](https://github.com/cloudflare/pingora), through a fork published on crates.io as `zentinel-pingora-*`.
- **Configuration:** KDL, in one file or several joined with `include`. Validated with `zentinel test`; `zentinel lint` reports settings that are being ignored. Reloaded on `SIGHUP`, or on file change with `auto-reload`, and validated before an atomic swap.
- **Routing and upstreams:** routes match on host and path; load balancing includes round robin, least connections, consistent hashing, Maglev and power of two choices; active health checks over HTTP, TCP and gRPC; retries and circuit breakers.
- **TLS:** termination with per-SNI certificates, client certificates (mTLS) and ACME issuance. HTTP/1.1 and HTTP/2 downstream and upstream; HTTP/3 is not implemented.
- **Traffic handling:** response caching, rate limiting, GeoIP filtering (MaxMind and IP2Location databases), response compression with gzip, Brotli or zstd negotiated from `Accept-Encoding`, and static file serving.
- **Agents:** WAF, authentication and other policy run in agents, separate processes the proxy talks to over Unix domain sockets or gRPC (optionally with TLS) using agent protocol v2. Each agent has its own timeout and a `failure-mode` of open or closed, so a slow or crashed agent does not take the proxy down. The [agent registry](https://registry.zentinelproxy.io/) lists agents for WAF and ModSecurity rules, bot management, IP reputation, authentication and SPIFFE identity, GraphQL, gRPC and SOAP inspection, and scripting in Lua, JavaScript or WebAssembly. SDKs for writing agents exist for Rust, Go, Python, TypeScript, Kotlin, Elixir and Haskell.
- **Observability:** Prometheus metrics and structured access, error and audit logs. OpenTelemetry tracing and Redis or memcached-backed distributed rate limiting are build features (`opentelemetry`, `distributed-rate-limit`), not in the default build.
- **Licence:** Apache 2.0.
Current release: 26.10_8 (GitHub release tag; the crate on crates.io is `zentinel-proxy`).
## Site
- [Benchmarks](https://zentinelproxy.io/benchmarks/): Performance, soak testing, and chaos engineering results for Zentinel reverse proxy
- [Compare](https://zentinelproxy.io/compare/): How Zentinel differs from nginx, HAProxy, Envoy, Caddy and Traefik — on design, not on benchmarks.
- [Contributing](https://zentinelproxy.io/contributing/): How to contribute to Zentinel: where to start, what belongs in the core, and where to ask questions.
- [Control Plane](https://zentinelproxy.io/control-plane/): Fleet management for Zentinel reverse proxies. Declarative configuration distribution with safe rollouts, real-time monitoring, and audit logging.
- [Config Converter](https://zenti
…Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| formal.ai | Formal | documentation AI and machine learning Cybersecurity +1 | US | 51 | ✓ | ||
| traefik.io | Traefik Labs: Unified Control Plane for APIs, Models, and Agents | documentation AI and machine learning Developer tools +2 | — | 58 | ✓ | ||
| bitninja.com | BitNinja | documentation Cybersecurity | FR | 55 | ✓ | ||
| agentfield.ai | AgentField | documentation AI agents and MCP Developer tools | US | 53 | ✓ | ✓ | |
| zeropath.com | ZeroPath | interface Cybersecurity | US | 57 | ✓ | ✓ | |
| ngrok.com | ngrok | interface AI and machine learning Infrastructure +1 | DE | 68 | ✓ | ✓ | |
| zenity.io | zenity.io | documentation AI and machine learning Cybersecurity | US | 57 | ✓ | ✓ | |
| superwise.ai | SUPERWISE® | documentation AI and machine learning Cybersecurity | US | 55 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=zentinelproxy.io · GET /v1/domain/zentinelproxy.io · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage zentinelproxy.io, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for zentinelproxy.io:
1. POST https://agentwebmap.com/v1/sites/zentinelproxy.io/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://zentinelproxy.io/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/zentinelproxy.io/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/zentinelproxy.io).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.