WebDriver
An open source tool anyone can run
How to detect WebDriver
WebDriver identifies itself through its own markers in the browser. Those can be faked, so it is detected by confirming them against other signals: where the traffic comes from, such as the IP address and hosting network, matches the operator; and scripted navigation with no human input.
- Detection method
- Self-declaredThe agent names itself in its user agent, and Verisoul confirms it with network, device or behavioral data. A user agent alone is never enough.
- Signals that identify it
- NetworkWhere the traffic comes from, such as the IP address and hosting network, matches the operator
- DeviceWebDriver automation flag and driver artifacts in the browser
- BehavioralScripted navigation with no human input
Every signal Verisoul checks for WebDriver
WebDriver identifies itself through its own markers in the browser. Those can be faked, so we only label a session WebDriver when the other signals check out too.
- Not used
Cryptographic
Not needed to identify it
- Used
Network
Where the traffic comes from, such as the IP address and hosting network, matches the operator
- Used
Device
WebDriver automation flag and driver artifacts in the browser
- Used
Behavioral
Scripted navigation with no human input
How often you'll see it
Common
Shows up regularly on most sites
More open source tools
Questions about WebDriver
How do you detect WebDriver?
WebDriver identifies itself through its own markers in the browser. Those can be faked, so it is detected by confirming them against other signals: where the traffic comes from, such as the IP address and hosting network, matches the operator; and scripted navigation with no human input.
What is WebDriver?
WebDriver is a browser controlled through the WebDriver protocol, the engine behind Selenium.
Does WebDriver identify itself?
Partly. WebDriver leaves its own markers in the browser, but those can be faked, so they are checked against other signals.
Can a bot pretend to be WebDriver?
A bot can copy WebDriver's user agent or markers, but the network, device and behavior signals will not match, so it is not labeled WebDriver.
How common is WebDriver?
Common. Shows up regularly on most sites.
What does the Verisoul API return for WebDriver?
Every session Verisoul identifies as WebDriver carries an agent block with id "webdriver", name, provider, type "headless_automation", detection_method "self_declared" and the detection_signals used (network, device, behavioral). Build rules on the id, type and detection method.