Detect Misskey

PluginView evaluates public page signals in these classes when identifying Misskey. Individual fingerprint rule bodies are proprietary and are not published.

• Meta tags
• HTML markup

Illustrative indicators derived from public catalog metadata for Misskey. A live scan may match additional proprietary rules beyond these examples.

• application-name: Misskey
• <!-- Thank you for using Misskey! @syuilo -->

Establishes

One or more public signals on the scanned page matched a known Misskey signature (2 rules) at the time of the scan.

Does not establish

A sitewide install of Misskey, an active vendor contract, exclusive use, or that Misskey is still in place today.

1. 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Misskey signals.
2. 2. PluginView reads only public responses (meta tags, html markup) and scores them against the Misskey signature set (2 rules).
3. 3. Review the confidence score and text explanation for Misskey on the results page.

Can PluginView detect Misskey without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Misskey — typically meta tags, html markup. It does not bypass authentication or paywalls.

What category is Misskey?

Misskey is classified under Message boards in the PluginView directory.

How many fingerprint rules cover Misskey?

This reference currently tracks 2 fingerprint rules across meta tags, html markup. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Misskey?

Illustrative public indicators for Misskey include application-name: Misskey; <!-- Thank you for using Misskey! @syuilo -->. A live scan may match additional proprietary rules beyond these examples.