Is Dokobit e-signing and e-identification safe?
Dokobit e-signing lets allowlisted Dokobit partner pages request certificate metadata and signatures through its local signing host.
The extension injects a content script into all pages and frames, but its background script only permits messages from Dokobit and hardcoded partner origins. On those allowed pages, the page API can request certificate details or signing operations through the local lt.isign.chromesigning native host; other origins are rejected before native messaging.
Who publishes itDokobit - no other listings under this identity, 1 shared hostname
Dokobit - no other listings under this identity, 1 shared hostname
What this publisher told the store about itself, and the other listings that told it the same thing.
Shared hosts - 1 hostname
Hostnames hardcoded in this extension that few other listings call. That can mean one operator behind both, and it can equally mean a small shared vendor, so it is context rather than a conclusion. Hosts that many listings call are left out: they are services, not connections.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
What it can do
Permissions this extension asks for, as declared in version 1.1.70. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.
Talk to a program installed on your computer, outside the browser's sandbox
nativeMessaging
Store data in your browser
storage