Detect Typekit

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

• Script sources
• JavaScript globals
• HTML markup

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

• use.typekit.com
• Typekit.config.js: .
• <link *href="use.typekit.netcom

Establishes

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

Does not establish

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

Can PluginView detect Typekit without logging in?

Yes. PluginView only reads publicly accessible responses when checking for Typekit — typically script sources, javascript globals, html markup. It does not bypass authentication or paywalls.

What category is Typekit?

Typekit is classified under Font scripts in the PluginView directory.

How many fingerprint rules cover Typekit?

This reference currently tracks 3 fingerprint rules across script sources, javascript globals, html markup. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses Typekit?

Illustrative public indicators for Typekit include use.typekit.com; Typekit.config.js: .; <link *href="use.typekit.netcom. A live scan may match additional proprietary rules beyond these examples.