Tools / API exposure checker

API exposure checker: Swagger, OpenAPI & GraphQL

Check whether your website or API publishes its full map to anyone: OpenAPI / Swagger specifications, Swagger UI, ReDoc and Scalar pages, and GraphQL with introspection switched on. If a specification is public, see what it reveals: endpoints, authentication, unauthenticated operations and internal server names.

Why exposed API documentation matters

API documentation is meant to help developers, but a public specification for an internal or partner API hands an attacker a complete map: every endpoint, parameter and authentication method, often including admin routes and staging servers. GraphQL introspection does the same for GraphQL APIs. Broken object-level authorization (BOLA), the most common API flaw in the OWASP API Security Top 10, is far easier to find with that map in hand.

What it checks

How to fix exposed API docs

Frequently asked questions

Is a public API specification always a problem?

No. A public API you want developers to use should have public docs. It becomes a risk when the API is internal, for partners only, or documents admin and debug endpoints.

Does this tool call my API endpoints?

No. It only reads documentation locations and sends one small GraphQL introspection query that asks for type names. It never calls the operations listed in your specification.

Does "no authentication declared" mean the endpoint is open?

Not necessarily. It means the specification does not declare security for that operation; the server may still enforce it. Treat it as a list to verify, ideally in an API security assessment.

What is GraphQL introspection?

A built-in GraphQL query that returns the whole schema: every type, field and mutation. Useful during development, but in production it lets anyone map your API in seconds.

Related checks