Report a Mastodon Post About Me: Who Can Remove It
How to report a Mastodon post about you across servers: who can delete it, what forwarding does, and what to do if the server ignores you or is gone.
To report a Mastodon post about you, open the menu on the post, choose Report, attach the post as evidence, explain the problem in the note, and switch on the option that forwards the report to the poster's server. That server, named in the second half of the poster's full handle, is the only one that can delete the post or suspend the account. Every other server can hide the post from its own users and nothing more.
This is what makes Mastodon different from a platform with a single help center. A post is written on one server, called an instance, and delivered as a copy to every server that has a reason to show it. There is no central desk and no company that can remove all copies. Each server is run by its own administrator under its own rules, and the Fediverse is the wider group of servers, running Mastodon or other software, that exchange posts through an open protocol called ActivityPub.
So the work is a sequence: find the server that holds the original, report there first, decide what your own server should do, and know what to try when nobody answers. Where a point depends on one server's rules, this guide says so, because a rule on one instance is not a rule of the network.
- Find the poster's home server first: it holds the original and is the only server that can delete the post or suspend the account.
- Report from the post itself, attach it, write the reason in the note, and use the forward option so the home server's moderators receive the report.
- Your own server and other servers can limit, hide or block what they carry, but they cannot reach into another server and delete.
- If the home server ignores you or has disappeared, the surviving copies are handled one server at a time, and search results are handled separately.
Three numbers from the documentation set the limits you are working within.
From the Mastodon documentation for the reports API and for moderation, and the Mastodon Server Covenant, all read for this guide. The notice period applies only to servers that commit to the covenant.
A Mastodon post lives on one server and is copied to others
The original of a Mastodon post sits on the poster's home server, and another server holds a copy only if someone there follows the poster, replies, boosts, or searches for the post. Mastodon's user documentation says there is no global shared state between servers, so no server shows every public post. Your server shows what it knows about: posts from accounts its users follow, plus posts it learned about by other means, such as a search for a post's address.
Related readRemove a Tumblr Post About Me: Reblogs and ReportsYou find the home server in the poster's full handle: the username, then the domain of the server after it. A post on a large server's timeline may have been written on a small server you have never heard of, so open the profile and read the domain before anything else.
A scenario shows why this matters. A stranger on a small server posts your employer's name and your street, and a friend on a large server boosts it by mistake. You hold an account on a third server. Three administrators now carry the post, and only the stranger's can end the original.
Deletion by the poster is the best outcome, and it is not instant
If the poster deletes the post, the home server removes it and sends a Delete notice to the servers that had a copy. The Mastodon help center warns that content cached by other servers may not be deleted immediately. A community guide, Fedi.Tips, says most other servers delete the post too, that some may be delayed by a queue of tasks, and that in a small number of cases, for example when the other server is not working properly, the deletion does not happen there.
Which server can remove what
The home server can delete the post and suspend the account. Any other server can only change what its own users and database show. The table sets out the four situations you will meet.
| Server | What its moderators can do | What they cannot do | Depends on |
|---|---|---|---|
| Poster's home server | Delete the post, suspend or limit the account | Delete copies elsewhere; it can only send the deletion request | Its rules and how active its moderators are |
| Your own server | Hide the post and the poster from its users, limit or suspend the remote account locally, block the domain | Delete the original or suspend the account anywhere else | Whether its moderators agree to act |
| Any server showing a copy | Hide its own copy, limit the remote account | Touch the original or another server's copy | Whether you can reach them |
| A dead home server | Nothing: no one is there to act | Be asked to delete | Whether other servers still carry the post |
Mastodon's ActivityPub documentation lists Delete as removing a status from the database, and Delete on a profile as removing the account and all its statuses: those actions belong to the server that owns the data. Hachyderm, a large Mastodon instance, publishes a moderation series written for Mastodon 4.2.10 that says its "Delete posts" action on a remote user only makes the posts not visible to that instance, and that neither remote users nor their moderators are notified of moderation actions. Behavior may differ in other versions.
Related readRemove a Blogspot Post About Me: Blogger and WordPress.comMastodon's documentation describes the tools, not the outcomes: it sets no response time for reports and does not say what a moderator does with a report from another server. Anything beyond that is the practice of a given instance.
How to report a Mastodon post about you, step by step
You report from the post or the account, in the web interface or an app, and the report goes to your own server's moderators unless you ask for it to be forwarded. Mastodon's user documentation describes four moves: open the menu on the post or account and choose Report, add a note about why, optionally attach specific posts, and forward the report to the remote server's moderators if the conduct breaks that server's rules.
- Save the evidence firstKeep the post's address and a screenshot showing the full handle and date, in case the poster deletes it after your report.
- Open the report formUse the menu on the post, or on the profile if the problem is the account.
- Choose the reasonThe API names four categories: spam, illegal content, a violation of the server's listed rules, and other. If the server lists numbered rules, pick the one the post breaks.
- Attach posts and write the noteAdd every post that is part of the problem. In the note, say what the post says, why it breaks a rule or a law, and what you want done. The default limit is 1,000 characters.
- Switch on forwardingFor a poster on another server, forwarding sends the report to the moderators of the poster's home server. The reports API documentation shows the default is off, so it happens only if you choose it.
- Record the submissionNote the date and the wording. Do not file the same report again every day.
Labels differ between versions and apps. The community guide notes that the official apps lacked the forward option when it was written, so if your app has no forward switch, open the post in a browser and file it there.
Reporting without an account on any server
You cannot use the Report button without an account, but you can reach the people who run a server. A server publishes its rules and a contact on its About page. The API behind that page carries a contact account, an email address for inquiries, and a numbered rules list, and a server may leave the contact empty.
Mastodon GmbH, which runs mastodon.social and mastodon.online, publishes in its help center a point of contact for users of those two servers and a separate page for authorities. That is how those two servers work. A small server may have one administrator and one address, or none. When you write, give the address of the post, the full handle, the rule or law it breaks, and the action you ask for.
Related readRemove a Medium Post About Me: What WorksWhat to put in the report so the right person can act
A useful report names the rule, describes the post, says who is affected and asks for one action. The reason is practical: Hachyderm's 4.2.10 series says remote reports are always categorized as "Other" in its queue, whatever category the reporter chose. If the category is lost on the way, the note is what the receiving moderator reads, so write it as if the category will not arrive.
Read the poster's server's rules, not only your own. The community standards of mastodon.social and mastodon.online, for example, list doxxing and privacy violations, harassment, impersonation, non-consensual intimate imagery, misinformation and intellectual property violations. That is those two servers, not a network list. The page we read does not name defamation, and a small server may have no written rules beyond a line or two.
Posts that publish your address, phone number or workplace, impersonate you, or harass you are covered by the rules of most active servers, so report them as a violation. A critical post that is accurate and lawful is rarely a violation anywhere. If private images are involved, the route changes, and our page on leaked and intimate content removal covers it.
| What the post does | Category to choose | What the note must say | Usual result, in our experience |
|---|---|---|---|
| Publishes your address or workplace | Rule violation (privacy, doxxing) | The rule number, the exact detail exposed, no consent | Often actioned where such a rule exists |
| Impersonates you | Rule violation (impersonation) | Proof of identity and the account address | Suspension is a frequent outcome |
| Harasses you | Rule violation (harassment) | Each post, dates, the pattern | Depends on the server's tolerance |
| Makes a false factual claim | Other, or illegal content if a law applies | The claim, why it is false, the evidence | Uncertain: many servers will not judge truth |
| Criticizes you accurately | Usually none | Nothing to report | Likely closed without action |
What forwarding does, and who sees your report
Forwarding sends your report to the poster's home server, and it comes from your server, not from you. Mastodon's ActivityPub documentation says that for reports to remote servers, Mastodon sends the report from the instance actor, with the reported user, any attached posts, and the comment. The community guide adds that administrators on the receiving server see only the report's content, not who sent it, while your own administrator can see that your account filed it.
Related readRemove a Substack Post About You: Rules and RoutesHachyderm's 4.2.10 series describes the receiving side, and other versions or servers may differ. Remote reports identify the reporting server, not the individual reporter, and moderators cannot forward a report from their queue onward. If a report contains followers-only posts, they cannot recreate it and would need to contact the remote team through another channel. So a forwarded report that rests on followers-only posts may stall: state the content in the note as well.
One consequence is our reading of the sources, not a documented policy. If your account is on a small server with few users, the domain on the forwarded report may point to you. If staying unnamed matters, report from an account on a large general-purpose server, or write to the home server's contact directly.
The community guide says not to forward when the author's whole server is the problem: that report goes to your own administrator, who can block the server.
Server rules and network norms are not the same thing
Every Mastodon server sets its own rules, and nothing above the servers can overrule a decision. The community guide says each server is totally independent and sets its own rules for acceptable behavior. What exists above the servers is voluntary and weaker than a rule.
One example is the Mastodon Server Covenant, which lists four commitments for servers linked from the project's server picker: active moderation against racism, sexism, homophobia and transphobia, daily backups, at least one other person with emergency access, and at least three months of warning before shutting down. None of the four mentions reports about personal information or false statements, so it says little about how a listed server treats your case.
Related readReport a Threads Post About Me: What Meta RemovesHow one large operator handles reports
Mastodon GmbH's help page on moderation decisions and appeals describes mastodon.social and mastodon.online only. Reports go to a human team, and the page says there is no automated handling. Account holders learn what they were reported for and what action was taken, but not who reported. Reporters can ask for an outcome: the team can confirm it reviewed the report and whether the content breached the rules, but it does not share the specific action. The page does not explain how those servers treat reports about content that lives elsewhere. Treat it as one well-documented example, not the standard to expect.
The timeline, and what to do at each stage
No Mastodon source sets a deadline for reports. In our experience an active server reads a report within days and a quiet one may take weeks, so treat the ranges as experience, not a promise.
| Stage | When, usually | What you do | If nothing happens |
|---|---|---|---|
| Evidence saved | Day 0 | Screenshots, post address, full handle, domain | Nothing to wait for |
| Report to the home server | Day 0 to 1 | Report with forwarding, or email the contact | Note the date |
| Local protection | Day 0 to 1 | Block and mute on your account, ask your own server to limit | Still useful for your own view |
| One follow-up | After about a week | Short message with the date and rule number | Try a second contact route |
| Escalation | After about two to three weeks | Report the copies where you see them, then the legal route | Take advice |
Blocking and muting change what you see, not what exists. Mastodon's user documentation says a block hides the user from your view and forces them to unfollow you, and blocking a server stops you seeing its posts. Use them while a report is open, and do not reply, quote or boost the post to object: that gives it more reach.
What to do when the server ignores you
Silence has several causes: a volunteer who is away, a report closed because the post breaks no rule, or an abandoned server. Climb this ladder and stop at the first step that works.
- Check the server is aliveOpen the poster's server in a browser. If the site loads, its About page lists a contact and recent posts show activity, the problem is a slow reader, not a dead server.
- Send one follow-up on a second channelUse the contact account or email from the About page and cite the earlier report with its date and the rule number.
- Ask your own server to act locallyYour administrator can limit or suspend the remote account, or block the domain. That does not touch the original. A limit hides the account from your server's other users except its followers there, and a suspension or domain block removes it from view entirely.
- Report the copiesIf the post appears on servers other than yours, report it where you see it. Those administrators control that copy and can hide it even if the home server will not.
- Take the legal routeFor unlawful content, a letter from your counsel to the server's operator is the next step. The route and its wording belong to your lawyer, and the law that applies depends on where the operator and you are located.
A refusal is not always neglect: an accurate, lawful post about you, even an unwelcome one, sits outside most written rules. Repeating the same report does not change that. Report once with the facts, follow up once, then change route.
Related readReport a Snapchat Account or Story About YouAn abandoned or deleted server leaves copies behind
If the home server has disappeared, there is no one to ask, and the post survives only where other servers copied it. The hosting company Masto.host explains that when a server is simply deleted, its domain stops responding, so remote servers see what looks like a server that is temporarily down, and posts and profile data from its users can continue to exist on remote servers. Mastodon's tootctl documentation describes the opposite path: a self-destruct command that broadcasts account Delete activities to all known servers. In version 4.3.0 and later, the command prints instructions for switching the server into self-destruct mode, which is what sends the notices. A server that vanished never ran it.
A dead home server shifts your effort to two jobs. The first is finding the live copies. Use a search engine for distinctive words from the post and note every address that shows it. Do not paste a post's address into your own server's search box: Mastodon's user documentation says a search for a remote post's address makes your server fetch it.
The second is search results. A Mastodon post page that is still online can appear in results for your name, and that is handled with the search engines' removal tools and, where the content is lawful, with suppression. Indexing is the poster's setting, not yours: Mastodon's preferences documentation says its opt-out adds a noindex flag to public profile and status pages, without saying whether that covers old posts.
The next step: report to the home server and track it
In one sitting: save the post and the full handle, read the poster's server rules, file one report with forwarding on, and set your own blocks. Give it about a week, then send one follow-up. After that, report the copies you can find and decide on a legal route with your counsel. Reputation Partners handles the case file for people who would rather hand over the tracking, the follow-ups and the search side.
Related readReport WhatsApp group defamation: what worksIf a Mastodon post about you is already spreading or showing in search results, we can map the servers that carry it and the routes that apply to each. Start with the removal page.
Questions people ask
Can I report a Mastodon post if I do not have an account?
Not the Report button, which needs an account on some server. You can still contact the administrator of the poster's server through the contact details on its About page, or open an account on a general-purpose server and use its form. Either way, name the post, the full handle and the rule it breaks.
Does the poster find out I reported them?
On the servers run by Mastodon GmbH, the account holder is told what they were reported for and what action followed, but not who reported them. Other servers set their own practice, and a forwarded report reaches the poster's server from your server, not under your name.
What if the poster's server runs different software?
Mastodon is one program of many that speak ActivityPub. The W3C vocabulary defines Flag as reporting content as inappropriate and Delete as an actor having deleted an object, but each program decides what happens next. Expect a different form and a different contact, and read that software's own help before filing.
Can I get a post removed if it is true?
Sometimes. A true statement can break a server's rules if it publishes private details such as your address, and it can breach privacy law in some places. If it is true, lawful and of public interest, expect a refusal. The law depends on where you and the operator are, so ask your counsel.
How long should I wait before following up?
No Mastodon source sets a deadline for reports. In our experience about a week is a reasonable wait on an active server, and two to three weeks before changing route. If the About page says the team is volunteer-run or reduced, allow for that before you follow up.
