René's URL Explorer Experiment


Title: JWTForge — JWT Security Scanner & Attack Toolkit

Open Graph Title: JWTForge — JWT Security Scanner & Attack Toolkit

X Title: JWTForge — JWT Security Scanner & Attack Toolkit

Description: Free, fully client-side JWT security toolkit for pentesters: decode and verify tokens, scan for vulnerabilities, and forge attack tokens. Nothing ever leaves your browser.

Open Graph Description: Attacker-minded, fully client-side JWT toolkit. Decode, audit, and forge attack tokens with export artifacts. Nothing ever leaves your browser.

X Description: Attacker-minded, fully client-side JWT toolkit. Nothing ever leaves your browser.

Keywords:

Opengraph URL: https://jwtforge.com

direct link

Domain: jwtforge.com


Hey, it has json ld scripts:
{"@context":"https://schema.org","@type":"WebApplication","name":"JWTForge","alternateName":"JWTForge — JWT Security Toolkit","url":"https://jwtforge.com","description":"Privacy-first, fully client-side JWT security toolkit: decode and verify, audit for vulnerability signals, and generate attack tokens (alg:none, RS→HS confusion, kid/jwk injection, HS256 brute-force) with ready-to-run curl, Burp, nuclei and jwt_tool artifacts.","applicationCategory":"SecurityApplication","operatingSystem":"Any (web browser)","browserRequirements":"Requires JavaScript and the WebCrypto API.","offers":{"@type":"Offer","price":"0","priceCurrency":"USD"},"isAccessibleForFree":true,"inLanguage":"en","image":"https://jwtforge.com/og.png","featureList":["JWT decoder and signature verifier (HS/RS/PS/ES)","JWT vulnerability checker / security scanner","alg:none attack token generator","RS256 to HS256 algorithm-confusion generator","kid / jwk / jku injection generator","HS256 secret brute-force (in-browser Web Worker)","Claim tampering and re-signing","Export to curl, .http, Burp Intruder, nuclei and jwt_tool"]}
{"@context":"https://schema.org","@type":"WebSite","name":"JWTForge","url":"https://jwtforge.com","inLanguage":"en"}
{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"Does JWTForge send my token, secret, or keys to a server?","acceptedAnswer":{"@type":"Answer","text":"No. JWTForge is 100% client-side. Decoding, signature verification, key generation, signing, and the HS256 brute-force all run in your browser via the WebCrypto API. You can confirm it by opening your browser's DevTools Network tab — no request carries your data. The only optional outbound request is the JWKS-URL fetch on the Decode tab, which sends only the URL you type, never your token."}},{"@type":"Question","name":"What is a JWT security scanner and how is JWTForge different from a decoder?","acceptedAnswer":{"@type":"Answer","text":"A JWT security scanner looks beyond decoding to flag implementation weaknesses an attacker could exploit — things like the alg:none bypass, weak HMAC secrets, RS256-to-HS256 algorithm confusion, and kid/jku/jwk header injection. JWTForge's Audit tab surfaces those signals, and its Attack tab generates the forged tokens and ready-to-run artifacts you use to actually test them."}},{"@type":"Question","name":"How do I test a JWT for the alg:none vulnerability?","acceptedAnswer":{"@type":"Answer","text":"Open the Attack tab and use the alg:none generator. It strips the signature and produces none, None, nOnE and NONE header variants to defeat naive case-sensitive filters, then exports curl, .http, Burp, nuclei and jwt_tool artifacts. Send them to a system you are authorized to test; if the server accepts an unsigned token, authentication is bypassable."}},{"@type":"Question","name":"What is JWT algorithm confusion (RS256 to HS256)?","acceptedAnswer":{"@type":"Answer","text":"If a server picks the verification algorithm from the token header, an attacker can switch RS256 to HS256 and sign the token with the server's RSA public key — which is not secret — used as the HMAC key. JWTForge's algorithm-confusion generator re-signs your token this way so you can check whether the server trusts the header's algorithm."}},{"@type":"Question","name":"Can I brute-force a JWT secret in the browser?","acceptedAnswer":{"@type":"Answer","text":"Yes. The Attack tab includes an HS256/384/512 dictionary brute-forcer that runs in a Web Worker so the UI never blocks. It ships with a wordlist of common leaked secrets and accepts your own. If a weak secret is recovered, you can forge tokens the server will accept. It is entirely client-side — nothing is uploaded."}},{"@type":"Question","name":"Is JWTForge a jwt_tool alternative I can use online?","acceptedAnswer":{"@type":"Answer","text":"JWTForge covers much of the same JWT attack surface as jwt_tool — alg:none, algorithm confusion, kid/jwk/jku injection, claim tampering and secret brute-force — directly in the browser with no install. For each attack it also emits the equivalent jwt_tool command, so you can pivot to the CLI when you want to fire requests at a target yourself."}},{"@type":"Question","name":"Does the Audit tab confirm that my server is vulnerable?","acceptedAnswer":{"@type":"Answer","text":"No, and it never claims to. Whether a server accepts alg:none, mishandles algorithm selection, or uses a weak secret is a server-side property that cannot be observed from the token alone. Every Audit signal is a hypothesis to verify, paired with how to test it. The proof comes from running the matching Attack artifact against a system you are authorized to test."}}]}

theme-color#070912
color-schemedark
application-nameJWTForge
authordevploit
creatordevploit
googlebotindex, follow, max-video-preview:-1, max-image-preview:large, max-snippet:-1
categorytechnology
og:site_nameJWTForge
og:imagehttps://jwtforge.com/og.png
og:image:width1200
og:image:height630
og:image:altJWTForge
og:typewebsite
twitter:cardsummary_large_image
twitter:imagehttps://jwtforge.com/og.png

Links:

Skip to contenthttps://jwtforge.com#main
JWTForgehttps://jwtforge.com/
Decodehttps://jwtforge.com/decode
Audithttps://jwtforge.com/audit
Attackhttps://jwtforge.com/attack
Guideshttps://jwtforge.com/guides
Abouthttps://jwtforge.com/about
https://github.com/devploit/jwtforge
Start decoding →https://jwtforge.com/decode
Generate attack tokenshttps://jwtforge.com/attack
DecodeLive header / payload / signature breakdown, human-readable claims with expiry badges, and signature verification with your secret, public key, or a JWKS URL.Open Decode →https://jwtforge.com/decode
AuditHeuristic security signals — alg:none, weak algorithms, kid/jku/x5u injection surface, sensitive claims — each framed honestly as a hypothesis to verify, with how to test it.Open Audit →https://jwtforge.com/audit
AttackThe differentiator. Generate malicious token variants and ready-to-run curl, .http, Burp, nuclei and jwt_tool artifacts. Includes an in-browser HS256 brute-forcer.Open Attack →https://jwtforge.com/attack
How this works & privacy →https://jwtforge.com/about
All guides →https://jwtforge.com/guides
JWT Algorithm Confusion (RS256 → HS256)Force a server to verify an RS256 token as HS256 using its public key as the HMAC secret — and how to fix it.Read →https://jwtforge.com/guides/jwt-algorithm-confusion
The JWT alg:none AttackStrip the signature and set alg to none to bypass verification — variants, testing, and remediation.Read →https://jwtforge.com/guides/jwt-none-algorithm-attack
JWT kid Header Injection (path traversal, SQLi, command injection)Turn an unsanitized kid header into path traversal, SQLi, or command injection — including the /dev/null empty-key forgery.Read →https://jwtforge.com/guides/jwt-kid-injection
How this works & privacyhttps://jwtforge.com/about
@devploithttps://x.com/devploit
source on GitHubhttps://github.com/devploit/jwtforge

Viewport: width=device-width, initial-scale=1

Robots: index, follow


URLs of crawlers that visited me.