Detect Thefork
Thefork is a restaurant booking, managing system.
Detection looks at dom selectors across 2 fingerprint rules among the site's public responses.
01
Websites using Thefork
Loading website list…
02
Signal classes
PluginView evaluates public page signals in these classes when identifying Thefork. Individual fingerprint rule bodies are proprietary and are not published.
- DOM selectors
03
Example public indicators for Thefork
Illustrative indicators derived from public catalog metadata for Thefork. A live scan may match additional proprietary rules beyond these examples.
- iframe
04
What a detection means
- Establishes
- One or more public signals on the scanned page matched a known Thefork signature (2 rules) at the time of the scan.
- Does not establish
- A sitewide install of Thefork, an active vendor contract, exclusive use, or that Thefork is still in place today.
05
How to check a site for Thefork
- 1. Enter the website URL in the scan form — homepage, pricing, checkout, or login pages usually expose the strongest Thefork signals.
- 2. PluginView reads only public responses (dom selectors) and scores them against the Thefork signature set (2 rules).
- 3. Review the confidence score and text explanation for Thefork on the results page.
06
FAQ: detecting Thefork
- Can PluginView detect Thefork without logging in?
- Yes. PluginView only reads publicly accessible responses when checking for Thefork — typically dom selectors. It does not bypass authentication or paywalls.
- What category is Thefork?
- Thefork is classified under Reservations & delivery in the PluginView directory.
- How many fingerprint rules cover Thefork?
- This reference currently tracks 2 fingerprint rules across dom selectors. Individual rule bodies are proprietary and are not published.
- What public signals suggest a site uses Thefork?
- Illustrative public indicators for Thefork include iframe. A live scan may match additional proprietary rules beyond these examples.
