FAQ

FAQ

Q: Are the credentials real? No. Every value is generated from weighted synthetic databases. No data is sourced from actual breaches. SSNs are format-random, credit cards are Luhn-valid but not real, addresses are pattern-random.

Q: Is this legal? The tool generates synthetic data. Using it against systems you do not own or are not authorized to test may be illegal. Authorized testing only.

Q: Why are short passwords like 123456 in the output? Because that's reality. Breach statistics show the top passwords dominate real distributions. If you need policy-compliant candidates, use --min-length (e.g. --min-length 8).

Q: Why does the output have country-specific domains now? v2 claimed country domains in the README but never used them. v3.0 implements per-country weighted domain pools (mail.ru for RU, bol.com.br for BR, web.de for DE, yahoo.co.jp for JP, gmail-heavy everywhere).

Q: Can I make output reproducible? Yes — --seed 42 (or any integer) produces identical output for the same arguments.

Q: Zero dependencies? Really? Yes. Python 3.6+ standard library only. random.choices does the weighted sampling.

Q: How do I generate a hashcat wordlist? python3 credforge.py -n 200000 -f 6 -o wordlist.txt --min-length 6 — one password per line, no separators.

Q: The interactive menu and CLI — same features? Yes. Same engine. CLI mode is scriptable; interactive mode is a guided version of the same flags.

Q: How many lines can it generate? No hard limit. 1M lines take a few seconds (pure Python, zero I/O until the final write).