Mastodon Search Cannot Find Remote User: Fix

You type a remote user’s full handle into the Mastodon search box, but the profile does not appear in the results. This happens because Mastodon’s search engine indexes local content by default and relies on federation events to discover remote accounts. Without a prior interaction or a complete federated handshake, the search box returns nothing. This article explains why remote users stay invisible and provides three reliable methods to locate and follow them.

Why Mastodon Search Fails to Find Remote Users

Mastodon’s search engine does not crawl the entire fediverse. It indexes only content that has already federated to your instance. When you type a remote handle into the search box, the instance first checks its local database. If no post, boost, or follow has ever reached your instance from that remote account, the database returns zero results. The search box then attempts a live federation lookup. This lookup can fail if the remote instance is slow, down, or configured to block federation requests from unknown instances. The result is a blank search with no error message, leaving you unsure whether the account exists or the search is broken.

Full Handle Syntax Requirement

Mastodon requires the complete handle format @username@domain.tld for remote searches. If you type only the username or the username with the @ symbol but omit the domain, the search will never leave your local database. The instance cannot guess which remote server hosts the account. Always paste or type the full handle, including both @ symbols and the full domain name.

Federation Delay and Instance Blocking

Even with the correct handle, the live lookup can time out. Federated instances communicate over ActivityPub, and the request must travel from your instance to the remote instance and back. Network latency, server load, or a temporary outage on either side causes the lookup to fail silently. Some instances also moderate incoming federation requests by rejecting lookups from instances they do not trust. In these cases, the search box will never find the remote user, and you must use alternative methods.

Steps to Find and Follow a Remote User on Mastodon

Method 1: Full Handle Paste into the Search Box

1. Copy the complete remote handle
   Obtain the exact handle from the user’s profile on their instance. The format must be @username@domain.tld. For example, @mastodonmigration@mastodon.social.
2. Open your Mastodon instance search box
   Click the magnifying glass icon in the left sidebar or press Ctrl + / to focus the search box.
3. Paste the full handle and press Enter
   Paste the handle exactly as copied. Press Enter. Wait up to 10 seconds. If the remote instance responds, the profile appears in the search results. Click the profile to open it and then click Follow.
4. If the profile does not appear, refresh the search
   Clear the search box, paste the handle again, and press Enter. A second attempt sometimes succeeds when the first lookup timed out.

Method 2: Use the Instance Public Directory

1. Navigate to your instance public directory
   Open a browser and go to https://yourinstance.tld/directory. Replace yourinstance.tld with your actual instance domain.
2. Search for the remote user by display name or username
   Type the user’s display name or username into the directory search field. The directory shows users who have opted into discovery, including remote users who have interacted with your instance.
3. Click the user profile and follow
   Once you find the user, click their name to open the profile page. Click Follow to add them to your home feed.

Method 3: Use a Third-Party Search Tool

1. Open Fedi.Directory
   Go to https://fedi.directory in your web browser. This site indexes Mastodon users by category and interest.
2. Search for the user by name or category
   Use the search bar or browse categories. When you find the user, click their profile link to open their Mastodon profile page on their home instance.
3. Copy the handle from the profile URL
   The profile URL contains the full handle. Copy it and paste it into your instance search box as described in Method 1.

If Mastodon Still Cannot Find the Remote User

Remote User Has Not Interacted with Any Federated Account

Some remote users have never posted, boosted, or followed anyone outside their home instance. Your instance cannot discover them through federation because no ActivityPub message has ever arrived. In this case, you must ask the user to interact with a public post from your instance or ask someone already following them to boost a post. After that interaction, the search box will find them.

Remote Instance Blocks Your Instance

The remote instance may have a domain block that prevents federation requests from your instance. You cannot override this block. The only workaround is to create an account on an instance that the remote instance allows, or contact the remote instance admin to request an exception.

Search Box Returns Only Local Results

Some Mastodon instances disable remote search entirely in their server configuration. If the search box never returns remote users even after correct handle pasting, your instance admin may have set SEARCH_DISABLED or WHITELIST_MODE to true. Contact your instance admin to confirm. If remote search is disabled, you must use the public directory or third-party tools.

Mastodon Search vs Third-Party Tools for Remote User Discovery

Item	Mastodon Search	Third-Party Tools
Requires federation handshake	Yes	No
Indexes all remote users	No, only those who federated	Depends on the tool’s database
Works with blocked instances	No	Yes, if the tool has the profile
Speed of result	Instant for local, up to 10s for remote	Varies by tool
Requires exact handle format	Yes	Sometimes only a name is needed

You can now locate and follow any remote Mastodon user by pasting the full handle, checking the public directory, or using Fedi.Directory. If the search still fails, ask the user to interact with a federated post or check whether your instance blocks remote search. For persistent discovery issues, consider joining an instance with fewer federation restrictions.