Security
CORS Preflight Simulator
Method, Content-Type, and headers, checked against the actual Fetch spec's CORS-safelisted request rules - not an approximation.
Method
Triggers a preflight OPTIONS request
- Content-Type "application/json" isn't one of the three safelisted values (application/x-www-form-urlencoded, multipart/form-data, text/plain).
- Header not safelisted: authorization (e.g. Authorization always triggers a preflight).
This is one question. ArchSetu answers it for a whole repository.
Call graph, dead code, blast radius and a health score, in about a minute.
Related tools
All Security tools →CORS Config Generator/ExplainerOrigins, methods, headers to generated CORS headers.Security Risk ScannerPaste a real GitHub repo - hardcoded secrets, unsafe dynamic execution, string-built SQL, insecure transport, and weak cryptography. Sign in required.JWT InspectorDecode a JWT header and payload, check expiry - decode-only, signing key never needed.Bcrypt Cost Factor CalculatorA measured benchmark on your hardware plus a target hash time to the right bcrypt cost factor.AWS IAM Policy GeneratorService, access level, and a resource ARN to a valid, scoped IAM policy JSON.API Key Format IdentifierPaste a key prefix - which service it belongs to, based on documented prefix conventions.
Was this tool helpful?