@ali-m07 Thanks for the PR, great job, it works fine!

One suggestion: Facebook enforces strict username rules (allowed symbols, length, etc.). To make this validator more accurate, could you add a regex-based pre-check before calling status_validate()?

Suggested flow:

• If the username matches the Facebook pattern → call status_validate()
• If it doesn’t → return 2 with a clear message explaining what constraint failed

This avoids unnecessary requests and gives the user better feedback.
If you run into any issues with showing the validation error message, feel free to ask, and once updated, you can push the changes here and reopen the PR.

Hey @ali-m07, I ran into this while working on the project.

I tested the facebook.com/{username} approach and it no longer works — Facebook now returns HTTP 400 for all direct profile URL requests (existing, non-existing, invalid) regardless of headers, cookies, or user agent. This means status_validate(url, 404, 200) always returns an error.

I opened #263 with an alternative approach that uses the account recovery lookup endpoint (same one used by the existing email scanner module). It reliably differentiates existing from non-existing usernames and includes the regex pre-validation that @kaifcodec requested.