Detect TerMed

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

• Script sources
• Inline scripts

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

• api.termed.de

Establishes

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

Does not establish

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

Can PluginView detect TerMed without logging in?

Yes. PluginView only reads publicly accessible responses when checking for TerMed — typically script sources, inline scripts. It does not bypass authentication or paywalls.

What category is TerMed?

TerMed is classified under Appointment scheduling in the PluginView directory.

How many fingerprint rules cover TerMed?

This reference currently tracks 2 fingerprint rules across script sources, inline scripts. Individual rule bodies are proprietary and are not published.

What public signals suggest a site uses TerMed?

Illustrative public indicators for TerMed include api.termed.de. A live scan may match additional proprietary rules beyond these examples.