Detect MyFonts

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

• Response headers
• DOM selectors

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

• content-security-policy: .myfonts.net
• link

Establishes

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

Does not establish

A sitewide install of MyFonts, an active vendor contract, exclusive use, or that MyFonts 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 MyFonts signals.
2. 2. PluginView reads only public responses (response headers, dom selectors) and scores them against the MyFonts signature set (2 rules).
3. 3. Review the confidence score and text explanation for MyFonts on the results page.

Can PluginView detect MyFonts without logging in?

Yes. PluginView only reads publicly accessible responses when checking for MyFonts — typically response headers, dom selectors. It does not bypass authentication or paywalls.

What category is MyFonts?

MyFonts is classified under Font scripts in the PluginView directory.

How many fingerprint rules cover MyFonts?

This reference currently tracks 2 fingerprint rules across response headers, dom selectors. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses MyFonts?

Illustrative public indicators for MyFonts include content-security-policy: .myfonts.net; link. A live scan may match additional proprietary rules beyond these examples.