Usage Options

cupidcr4wl currently implements four command line argument options,

To see all cupidcr4wl command line arguments:

    python3 cc.py -h or python3 cc.py --help

usage: cc.py [-h] [-u USERNAME] [--export-results] [--debug] [--sites] [--export-sites]

A tool for checking if a username exists across various platforms.

options:
  -h, --help        show this help message and exit
                    
  -u USERNAME       Enter a username or multiple usernames (separated by commas) to search.
                    
  --export-results  Search results will be exported to a text file named 'cc_results.txt' in
                    the current working directory.
                    
  --debug           Debug mode shows all results, HTTP response codes, check_text/not_found_text
                    matches, timeouts, and errors for each site checked.
                    
  --sites           Prints all sites that cupidcr4wl will search.
                    
  --export-sites    Exports the list of sites that cupidcr4wl will search to a text file
                    named 'cc_sitelist.txt' in the current working directory.

2. To perform a search of a username:

    python3 cc.py -u username

Due to how different platforms structure their usernames it is recommended to run your target username in multiple different variations. E.g., janedoe,'jane doe',jane-doe,jdoe.

3. To perform a search of multiple usernames separate them by commas (with no spaces):

    python3 cc.py -u username1,username2,username3

4. To export a copy of the search results to a text named 'cc_results.txt' in the current working directory:

    python3 cc.py -u username --export-results

5. To view a list of all sites that cupidcr4wl will search:

    python3 cc.py --sites

6. To export the list of all sites that cupidcr4wl will search to a text file named "cc_sitelist.txt" in the current working directory:

    python3 cc.py --export-sites

7. To run cupidcr4wl in debug mode to test for false positives/negatives:

    python3 cc.py -u username --debug

When using the --debug argument, a few things will happen.

1. All results will be displayed:

     - Account found results

     - Possible account found results

     - No account found

     - Errors

     - Timeouts

2. HTTP response codes

3. Results of matched check_text or not_found_text

This allows a user to check for accuracy by dissecting the exact reason cupidcr4wl categorized the account result the way it did (found, not found, possibly found).

By default, cupidcr4wl will only display "Account found" and "Possible account found" results. If no account was found, a request resulted in a timeout, or a response code other than 200 was received it will not be displayed. The --debug argument allows the user to see all aforementioned information. This is done intentionally to reduce the "spaminess" of the results.