Fake Token Generator

Tokens produced here are structurally shaped like Discord bot tokens - three base64 segments joined by full stops - but the signature segment is random rather than derived from Discord's key. They authenticate nothing and will be rejected immediately by the API.

The use case is testing: validating a regex, checking that a redaction filter catches token-shaped strings, or populating a fixture without pasting a real credential into a test file. Anything where the shape matters and the validity does not.

If a site offers to generate working Discord tokens, it is either lying or phishing. Only Discord can issue a valid token, and the only way to obtain one is the Developer Portal for your own application.

Test data ends up in places production credentials should not: committed to repositories, pasted into issues, included in bug reports and shipped in example configs. A structurally valid but functionally dead token removes the risk entirely.

It also makes leak detection testable. You can commit a fake token deliberately to confirm your secret scanner fires, which is not something you want to try with a real one.

If you are building a token checker, decoder or any tool that parses tokens, you need sample data that matches the real format without exposing actual credentials. Fake tokens are the safe way to test edge cases and validate your parsing logic.

A fake token follows the same three-part structure as a real one, so your regex and split logic behave identically. The middle section even decodes to a JSON payload with a plausible user ID, which is handy for testing a decoder end to end.