Detection Methodology

1) Data source and scope

Each check is driven by platform-specific URL templates and matching rules in the maintained site dataset. The scanner focuses on publicly reachable profile surfaces and does not authenticate into private areas.

2) Detection pipeline

1. Validate username format and prepare the target request set.
2. Build site-specific URLs using platform rule templates.
3. Run concurrent HTTP checks with timeout controls.
4. Evaluate status code and content-match rules per platform.
5. Stream matched results in real time and expose source links.

3) Safe mode policy

By default, adult-category platforms are excluded from scan coverage on this website. This improves safety posture and keeps the tool aligned with general audience and ad policy expectations.

4) Known limitations and false signals

Platform behavior changes frequently. Some sites return generic responses, require JavaScript rendering, or rate limit requests. This can produce false positives or false negatives. Redirect behavior and anti-bot defenses may also affect availability checks.

5) Verification checklist

• Open profile URLs manually and inspect profile context.
• Cross-check at least 3 independent platform signals.
• Compare account creation clues and posting cadence.
• Document uncertainty levels in your case notes.
• Never assert identity from one username match alone.

6) Feedback and rule updates

Detection rules are periodically revised when platform behavior changes. If you observe an incorrect result, report it with username, platform, and expected behavior so the rule can be triaged and updated quickly.