Skip to content

Accuracy Implementations

Jump to bottom
OSINTial edited this page Apr 13, 2025 · 2 revisions

cupidcr4wl implements multiple data points to ensure robustness and accuracy of its results.

HTTP Response Code

For cupidcr4wl to display an "Account found" or "Possible account found" result, it first analyzes the HTTP GET response to ensure the response code is 200. An HTTP response code of 200 OK indicates that a request was successful. If the HTTP GET request receives a response code other than 200 it will display "No account found".

Check_text

After an HTTP GET response code of 200 is ensured, cupidcr4wl will then utilize check_text. check_text are a list of HTML code snippets that have been parsed from pages that display a valid account. They are utilized to maintain robustness of the accuracy of results that cupidcr4wl returns. If an HTTP GET response of 200 + a match of check_text is found, the result will be "Account found". The HTML code snippets can be found in the Page Source code.

Not_found_text

Inversely, not_found_text are HTML code snippets parsed from invalid account pages (code snippets that are displayed on pages when an invalid username or phone number is requested). not_found_text are the third stage of the accuracy process. Before getting to this stage, cupidcr4wl will have completed the analysis of the HTTP GET response and check_text. If an HTTP GET response of 200 + a match of not_found_text, the result will be "No account found". Again, the HTML code snippets can be found in the Page Source code.

Both check_text and not_found_text found

If the situation arises where both check_text and not_found_text are matched, cupidcr4wl will display the reult of "Account found". This is done because cupidcr4wl analyzes check_text before not_found_text. This was intentionally implemented as it is more preferred to receive a possible false positive as compared to a false negative and risk missing an important piece of intel.

Neither check_text or not_found_text found

If a response code of 200 is received, but neither check_text nor not_found_text are matched, cupidcr4wl will display the result "Possible accout found". Due to changes in HTML code by web developers of the platforms that cupidcr4wl searches, HTML snippets used in check_text and not_found_text may become innacurate over time. As an HTTP GET response of 200 indicates that the request was successful, it means that the user will not be displayed a false negative, thus missing a relevant piece of intel.

To simplify:

  • HTTP GET response code other than 200 = No account found.
  • HTTP GET response code of 200 + check_text match = Account found.
  • HTTP GET response code of 200 + no check_text match, but not_found_text match = No account found.
  • HTTP GET response code of 200 + no check_text match AND no not_found_text match = Possible account found.
  • HTTP GET response code of 200 + check_text match AND not_found text match = Account found.

ISP content blocking

It should be noted that if your ISP, VPN, or proxy provider is blocking certain adult platforms in your region it will cause cupidcr4wl to return false positives. To prevent this ensure that you are using a VPN or proxy location in a region that is not blocking content.

Clone this wiki locally