If the target Site is a hosting site and the combo is the login/password of a premium account, the received Cookie is a premium account. Received Cookie: this column shows the Cookie received by the target Site for each Hit. This column is refreshed each time you check a combo with the History checker. Captured keys: this column shows the keywords captured on the answer page for each Hit. for a given site in the history it uses the settings loaded from the site snapshot, so you don't have to configure anything in the history options, since all the checker settings will be acquired from a saved snapshot, unless you don't have a snapshot for the site.in this case you have to create one by starting a bruteforcer session with the right settings for the site you have to create a snapshot for. History Checker Engine Now the History Checker engine uses the main bruteforcer engine to check history hits, i.e. The Keyword Wizard will be launched: from here you can configure special matching functions.
Finally you can access advanced key matcher features by right clicking on a key phrases box and selecting 'Add (Advanced)' from the popup menu. Moreover the global keys category has been changed to Retry Keys (a default list is included). If no keys are found, the AfterFingerPrinting Engine is activated. If a retry key is found, the combo is retested with another proxy.
If a failure key is found, the combo is marked as bad. If a ban key is found, the current proxy is banned and the combo is tested with another proxy. Success key is found, the combo is marked as hit. It searches in order for Success, Ban, Failure and finally Retry keys. Keys and then for source keys (the source keys are checked only if the request method is different from HEAD of course). The keywords checker engine looks out first for header General ChangesKeyword Engine The keywords phrases for Header and Source are now extended to four categories: Success Keys, Failure Keys, Ban Keys and Retry Keys.