API Security Scanner
Scan an API endpoint online with no agent to install: CORS policy, rate-limit headers, GraphQL introspection, and exposed OpenAPI documents that describe every route to an attacker.
Critical2High5Medium24Low25Info8
Critical2 checks
- JWT HS256 signed with weak or hard-coded secretHS256 trusts a shared secret. If the secret is short, default, or checked into source, attackers can sign forged tokens offline.
- SOAP/XML parser has external entities enabled (XXE)XML parsers with DOCTYPE / external entity processing enabled allow attackers to read local files, hit SSRF endpoints, and exfiltrate via DTD.
High5 checks
- Bearer token in URL query stringAuthorization: Bearer is fine, but a Bearer token in a URL query string can leak via logs.
- OpenAPI security scheme is weak or missingAn OpenAPI document with no securitySchemes, or one that lists only apiKey in header, signals that the API does not enforce real authentication.
- SOAPAction header injection / SSRFThe SOAPAction header value contains shell/URL metacharacters. If that value is passed verbatim to a downstream HTTP call without validation, attackers can pivot the request to internal services.
- GraphQL introspection exposes a mutation-heavy schemaThe GraphQL introspection response doesn't just confirm introspection is enabled, it resolves a "Mutation" root type with five or more distinct mutation fields, meaning the entire write surface of the API, not only its read schema, is enumerable by any caller.
- OIDC discovery advertises the "none" signing algorithmThe authorization-server metadata lists "none" among its supported ID token signing algorithms. That means the server will issue, and by implication accept, unsigned ID tokens.
Medium24 checks
- GraphQL endpoint has no rate-limit headersGraphQL POST endpoints need rate-limiting because one query can touch many resolvers.
- JSONP callback parameter acceptedJSONP allows arbitrary JS to be loaded in the victim's origin. Prefer CORS.
- GraphQL introspection enabled in production__schema / __type queries dump the entire schema, including internal fields, admin-only mutations, and deprecation hints that aid targeted attacks.
- GraphQL batch (array) queries acceptedAccepting an array of queries lets a single HTTP request fan out to N independent operations, multiplying rate-limit cost and bypassing per-request throttles.
- GraphQL error response leaks stack traceStack traces in error.extensions.stacktrace expose file paths, framework versions, and SQL fragments to any unauthenticated caller.
- OpenAPI schema declares defaults for sensitive fieldsDefaults such as isAdmin: false, role: user, or apiKey: REPLACE_ME teach attackers the shape of state and embed credentials in client SDKs.
- Rate-limit keyed only on client IP, no auth requiredPer-IP throttling is fine for anonymous traffic, but auth-less endpoints behind a shared NAT or proxy can be exhausted by one noisy neighbour.
- Rate-limit headers present but only enforced on some pathsReturning X-RateLimit-* headers without enforcing the cap is theatre. Callers see budgets they cannot exceed in the response but can hammer the server anyway.
- WSDL publicly accessibleAuto-published WSDL files enumerate every operation, parameter type, and binding - a blueprint for crafting SOAP-level attacks.
- API endpoint has no rate limitingThe API endpoint does not enforce rate limiting, allowing unlimited requests from a single client.
- HTTP TRACE method enabledHTTP TRACE method is enabled on the server. TRACE reflects the full request including headers, enabling Cross-Site Tracing (XST) attacks.
- JWT header declares a jku or x5u key-location claimA JSON Web Token found in the response body or a Set-Cookie header decodes to a header segment containing a jku (JWK Set URL) or x5u (X.509 URL) claim that points to an external URL, meaning whichever server verifies this token may fetch the verification key from a location named inside the token itself.
- OAuth authorization code request missing PKCEA request made to an OAuth/OIDC authorize endpoint during the scan uses response_type=code with a client_id but no code_challenge parameter, meaning the authorization code flow is running without Proof Key for Code Exchange (PKCE).
- OAuth implicit grant (response_type=token) in useA request made to an OAuth/OIDC authorize endpoint during the scan uses response_type=token (with no code value present), the deprecated implicit grant that returns the access token directly in the redirect URL fragment instead of through a back-channel exchange.
- API error response leaks a stack trace or internal file pathA JSON API error response includes a "stack" field containing a real stack trace, or a "message" field referencing an internal filesystem path, exposing implementation details to any caller who triggers the error.
- GraphQL IDE served in productionThis endpoint serves an interactive GraphQL IDE: a schema browser and a query editor for this API. GraphiQL, GraphQL Playground, Apollo Sandbox, Voyager and the Hasura console are all development tools, and every one of them is meant to be switched off outside development.
- OpenAPI document publishes a cleartext base URLThe served API description publishes a public base URL over plain http rather than https. That is either an OpenAPI 3 servers entry, or a Swagger 2.0 schemes list containing http and not https.
- OpenAPI document declares the OAuth2 implicit flowThe served API description declares an OAuth2 security scheme using the implicit grant. That flow returns the access token directly in the redirect URL fragment instead of through a back-channel exchange.
- Postman collection export publicly servedA Postman collection export is served from this URL, identified by its own _postman_id field. Collections carry every request path, body and header the author saved.
- Insomnia workspace export publicly servedAn Insomnia workspace export is served from this URL, identified by the fields Insomnia writes. The export holds every saved request in the workspace, plus the environment values those requests interpolate.
- OAuth authorization request uses a cleartext redirect_uriThe scanned URL is an OAuth or OpenID Connect authorization request with a cleartext redirect_uri. The callback is a plain http URL on a host that is not loopback.
- OIDC authorization request returns an ID token with no nonceThe scanned URL is an authorization request whose response_type includes id_token, but it carries no nonce parameter. OpenID Connect Core section 3.2.2.1 requires a nonce for every flow that returns an ID token from the authorization endpoint.
- Problem document exposes a stack trace or exception classAn RFC 9457 problem document exposes a stack trace or the internal exception class behind it. The trace member carries real stack frames, or the exception member names the class that threw.
- Outdated Swagger UI bundle loadedThe page loads a Swagger UI bundle older than 4.1.3, read from the version embedded in the asset path or package specifier.
Low25 checks
- TRACE method referenced in API response bodyA response body explicitly lists TRACE as a supported method (e.g. in a route config or API documentation payload the server exposes), which is unusual enough to be worth checking even though it doesn't confirm the verb is actually enabled.
- GraphQL introspection field suggestionsField suggestions on error responses let attackers enumerate the schema.
- OpenAPI server URL leaks internal hostswagger.json often contains the internal / staging host in the 'servers' array.
- CORS preflight result not cachedMissing Access-Control-Max-Age forces browsers to send preflight OPTIONS on every cross-origin request.
- OPTIONS response exposes full method allowlistA verbose OPTIONS response (Allow: GET, POST, PUT, PATCH, DELETE) leaks the entire verb surface to attackers, simplifying endpoint enumeration.
- CORS preflight cache exceeds 24 hoursAccess-Control-Max-Age above 86400 pins browsers to a stale allowlist. New disallowed headers or origins take up to Max-Age seconds to take effect.
- WebSocket endpoint reachable, Origin handling unconfirmedA WebSocket-shaped endpoint was reachable and its response body doesn't reference Origin handling. This is a static content heuristic, not a live handshake test with a foreign Origin header, so it flags something to verify manually rather than a confirmed missing check.
- REST endpoint response exposes privileged fieldsA response body contains privileged field names (role, isAdmin) that, if the same names are also accepted as unvalidated input, would let clients escalate privileges. Detected from response content only; this does not confirm the fields are writable.
- XML-RPC endpoint referencedA page references an XML-RPC endpoint (e.g. xmlrpc.php). In WordPress and similar CMSes this legacy endpoint enables brute-force amplification attacks and remote method invocation when it's actually reachable and un-hardened.
- API reports itself deprecated without a Deprecation/Sunset headerA JSON API response explicitly reports itself as deprecated, a deprecated: true field, or a status/message field saying so, but the HTTP response carries neither the standard Deprecation nor Sunset header.
- GraphQL schema served as raw SDLThe response is a GraphQL schema document in Schema Definition Language form, served as plain text. That is the schema itself, not an HTML page that happens to show one.
- OpenAPI document declares no security for write operationsThe served OpenAPI document describes write operations but declares no security scheme anywhere. There is no securitySchemes block, no securityDefinitions, and no security requirement on any POST, PUT, PATCH or DELETE operation.
- AsyncAPI document publicly servedAn AsyncAPI document is served from this URL, describing the event-driven half of the system. It covers brokers, channels and topics, and the payload schema of every message that flows through them.
- WADL document publicly servedA WADL (Web Application Description Language) document is served from this URL. Jersey, Apache CXF and other JAX-RS stacks generate one automatically and expose it unless it is explicitly disabled.
- RAML API definition publicly servedA RAML API definition is served from this URL, identified by the #%RAML version marker. RAML files must begin with that marker, so this matches the document itself rather than a mention of it.
- OData $metadata document publicly servedAn OData $metadata document, describing the service's entity model, is served from this URL. OData services such as SAP Gateway, Microsoft Dynamics and ASP.NET Core OData publish one automatically.
- OIDC discovery advertises implicit-grant response typesThe authorization-server metadata advertises a response type that returns a token from the authorization endpoint. The advertised value is "token" or "id_token token", neither of which comes with a code.
- OIDC discovery omits code_challenge_methods_supportedThe authorization-server metadata advertises the authorization-code response type without PKCE support. code_challenge_methods_supported is the field a client reads to discover PKCE is available, and it is absent.
- JWT with a lifetime measured in monthsA JWT reachable from this response stays valid for more than 90 days after it was issued. The decoded payload's exp claim is more than 90 days after its iat or nbf.
- Retry-After header is not a valid delay or dateThe response carries a Retry-After header whose value is neither seconds nor an HTTP-date. Those are the only two forms RFC 9110 defines, and a client that cannot parse the header ignores it.
- Sunset date has passed but the endpoint still answersThe response carries an RFC 8594 Sunset header whose date has already passed. The resource is still being served after the retirement date it announced.
- JSON body served as HTML or with no Content-TypeThe response body is JSON-shaped but is not labelled as JSON by its Content-Type header. It is either declared as text/html, or served with no Content-Type at all.
- Response header points at an internal hostA Location, Content-Location or Link response header contains a URL on an internal hostname. That means a loopback or RFC1918 address, or a private-use suffix such as .internal, .local or .corp.
- WWW-Authenticate realm leaks internal detailThe WWW-Authenticate challenge carries a realm string that describes internal infrastructure. The value contains a filesystem path, an IP address, or an internal hostname suffix.
- Access-Control-Allow-Origin carries more than one originThe Access-Control-Allow-Origin header holds two or more origins rather than one. The header is defined to carry exactly one origin, or the single token *.
Info8 checks
- REST endpoint allows DELETEREST endpoint exposes DELETE without authentication.
- PUT method listed in Allow headerPUT changes server state. This is a passive observation that the endpoint's Allow header advertises PUT support (normal for any REST API with a PUT route, including properly authenticated ones); it does not confirm the endpoint accepts unauthenticated writes.
- PATCH method listed in Allow headerPATCH partially mutates a resource. This is a passive observation that the endpoint's Allow header advertises PATCH support (normal for any REST API with a PATCH route, including properly authenticated ones); it does not confirm the endpoint accepts unauthenticated writes.
- OPTIONS response exposes state-changing HTTP methodsThe OPTIONS response Allow header lists a state-changing method (TRACE, DELETE, or PUT), one of the higher-risk verbs to have reachable if the corresponding handler isn't properly authenticated. This is distinct from the separate 'full method allowlist' finding, which flags on verb count rather than which specific verbs are present.
- SOAP endpoint detectedA SOAP/XML web service endpoint was detected. SOAP services have a unique attack surface including XXE, SSRF via SOAPAction, and schema enumeration via WSDL.
- API described with Swagger 2.0The API description served here declares swagger: 2.0. That format was superseded by OpenAPI 3.0 in 2017 and by 3.1 in 2021.
- OpenAPI document advertises deprecated operationsThe served API description marks one or more operations or parameters as deprecated. They are still published as callable, so the contract advertises a route the team has already written off.
- Access-Control-Allow-Credentials sent with no allowed originThe response sets Access-Control-Allow-Credentials: true with no Access-Control-Allow-Origin. There is no origin the credentialed cross-origin request could be allowed for.
About the API checks
- What does the API category check?
- Scan an API endpoint online with no agent to install: CORS policy, rate-limit headers, GraphQL introspection, and exposed OpenAPI documents that describe every route to an attacker. CORS policy, rate-limit headers, GraphQL introspection, OpenAPI.
- How many api checks are there?
- VulnRadar runs 64 checks in this category, ranging across critical, high, medium, low, info severity.
- Do I need to install anything to run the api checks?
- No. Paste a URL in the browser or call the REST API, and the scan itself runs from our servers against that URL. There is no agent and no appliance to deploy alongside your application. A browser extension exists if you want to scan the page you are looking at, but nothing has to be installed to use this.
Run the api checks on your site
VulnRadar runs all 64 of these against a URL in seconds, with the evidence and fix for every finding. No agent to install, just paste a URL.