OP 01 July, 2023 - 12:38 AM
INSTALL
pip3 install -r requirements.txt
python main.py
USAGE
Enter token. Accept: input text, any file (accept unparsed logs), folder (recursive scan files with tokens).
This program parses token with complex algorithms (check QUESTIONS for more info).
Then your tokens, check for validation using parallel request with highest speed.
In the output you get text files with tokens and json_data file which contain all tokens data .
QUESTIONS
Q: Could there be bugs in the code?
A: Absolutely not. All methods used in the checker have been tested 1000 times by me, and the results have been verified with other checkers, including synchronous ones.
Q: Why is the sum of valid + unverified + invalid tokens less than the sum of parsed tokens?
A: The checker records all id tokens. If the new token contains an id from the list of verified ones, it is removed. Don't worry if one token becomes invalid another token with the same id too.
Q: Why do I have 1000 tokens in the file, but the parser found only 580?
A: The code uses an advanced token parser. The fact is that ordinary parsers check only the token pattern, but it also needs to check headers. (More info: https://jwt.io/introduction) In short, there are tokens that were created by some kind of token generator. They contain a header. If you decrypt it (base64), then for natural discord tokens it represents json value, while for generated ones it will be different. Check it out for yourself: https://jwt.io/#debugger-io.
OUTPUT
Standart output with valid, invalid, etc txt files.
Json output:
{
"tokensInfo": {
"valid": [],
"nitro": [],
"payment": [],
"phone": [],
"unverified": [],
"invalid": [],
"parsedTokens": []
},
"tokensData": {
"TOKEN": {
"status": "valid || unverified || invalid",
"me": {},
"payment_sources": {}
}
}
}
Download:
pip3 install -r requirements.txt
python main.py
USAGE
Enter token. Accept: input text, any file (accept unparsed logs), folder (recursive scan files with tokens).
This program parses token with complex algorithms (check QUESTIONS for more info).
Then your tokens, check for validation using parallel request with highest speed.
In the output you get text files with tokens and json_data file which contain all tokens data .
QUESTIONS
Q: Could there be bugs in the code?
A: Absolutely not. All methods used in the checker have been tested 1000 times by me, and the results have been verified with other checkers, including synchronous ones.
Q: Why is the sum of valid + unverified + invalid tokens less than the sum of parsed tokens?
A: The checker records all id tokens. If the new token contains an id from the list of verified ones, it is removed. Don't worry if one token becomes invalid another token with the same id too.
Q: Why do I have 1000 tokens in the file, but the parser found only 580?
A: The code uses an advanced token parser. The fact is that ordinary parsers check only the token pattern, but it also needs to check headers. (More info: https://jwt.io/introduction) In short, there are tokens that were created by some kind of token generator. They contain a header. If you decrypt it (base64), then for natural discord tokens it represents json value, while for generated ones it will be different. Check it out for yourself: https://jwt.io/#debugger-io.
OUTPUT
Standart output with valid, invalid, etc txt files.
Json output:
{
"tokensInfo": {
"valid": [],
"nitro": [],
"payment": [],
"phone": [],
"unverified": [],
"invalid": [],
"parsedTokens": []
},
"tokensData": {
"TOKEN": {
"status": "valid || unverified || invalid",
"me": {},
"payment_sources": {}
}
}
}
Download:
