Lor.sh (Mastodon Instance) favicon

Lor.sh (Mastodon Instance)

Social & Identity
lor.sh•Engine Active
REST API
Interactive Reconnaissance

Scan any handle on Lor.sh (Mastodon Instance)

Enter a handle to probe Lor.sh (Mastodon Instance)'s public registry in real time with passive reconnaissance.

@
Try sample targets:

Reconnaissance Specifications

Handle Pattern & Endpoint

UserScope checks account registration on Lor.sh (Mastodon Instance) by passively querying the official public structure:

https://lor.sh/@{username}
Zero Query Logging & Privacy

All searches against Lor.sh (Mastodon Instance) are performed using passive unauthenticated requests. No search query logs, handles, or IP histories are recorded.

100% Client-Side Privacy Guaranteed

How to Check Username Availability & Presence on Lor.sh (Mastodon Instance)

Step-by-step guidance for security researchers, brand protection teams, and OSINT investigators:

1

Enter Exact Handle

Provide the username or handle without extra spaces or symbols. For Lor.sh (Mastodon Instance), usernames resolve directly via lor.sh.

2

Passive Probe Execution

UserScope leverages high-efficiency REST API queries to verify whether the target identity returns a valid public response code.

3

Cross-Network Footprint

Scan Lor.sh (Mastodon Instance) individually or probe all 650+ networks simultaneously to correlate alias re-use across the global OSINT surface.

Interpreting Lor.sh (Mastodon Instance) Scan Telemetry

Understand the meaning of each verification status returned by the UserScope engine:

FOUND / CLAIMED

An active account or public profile was verified on Lor.sh (Mastodon Instance). You can click through directly to inspect public repository activity, biography details, or profile timestamps.

AVAILABLE / UNCLAIMED (404)

The handle does not currently exist on Lor.sh (Mastodon Instance). It may be available for registration, or previously purged from the platform's namespace.

PROTECTED / RATE LIMITED

The platform's anti-scraping or rate limit mechanisms triggered a verification block. Re-probe using direct browser verification via the link provided above.

Frequently Asked Questions about Lor.sh (Mastodon Instance) Reconnaissance

Common questions regarding handle verification, privacy, and footprint detection on Lor.sh (Mastodon Instance):

How does UserScope check if a username exists on Lor.sh (Mastodon Instance)?

UserScope inspects public endpoints on Lor.sh (Mastodon Instance) (lor.sh) using passive query patterns (REST API). It verifies whether the username returns an active profile or an unregistered 404 response without making unauthorized modifications or alerting the account owner.

Can Lor.sh (Mastodon Instance) account holders see that I performed a username search?

No. All verification queries through UserScope are passive, unauthenticated, and zero-log. UserScope does not require login credentials or store your search history, ensuring 100% operational privacy.

What format should I use when looking up handles on Lor.sh (Mastodon Instance)?

Provide the raw alphanumeric handle without URL prefixes or '@' symbols. The standard profile URL pattern for Lor.sh (Mastodon Instance) resolves to https://lor.sh/@{username}.

Why is checking Lor.sh (Mastodon Instance) valuable during OSINT investigations?

As part of the Social & Identity ecosystem, usernames on Lor.sh (Mastodon Instance) frequently correlate across other public registries. Correlating identical handles across multiple platforms helps identify digital footprints, verify online presence, or protect personal brand identity.

Related Social & Identity Ecosystems

View all platforms