Security
OAuth Redirect URI Validator
Check a redirect URI against the OAuth 2.0 Security Best Current Practice - HTTPS except loopback, exact-match, no wildcards or fragments.
Redirect URI
Uses HTTPS (or is a loopback address, which is exempt).
No wildcard in the URI.
No fragment component.
Based on the OAuth 2.0 Security Best Current Practice - exact-match, HTTPS (except loopback), no wildcards or fragments.
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?