How do I use the MiseGuard Chrome extension?

Install it

Add it from the Chrome Web Store with Add to Chrome on MiseGuard → Chrome extension (Microsoft Edge installs Chrome extensions too). Until the listing is published the card shows Beta with Ask for early access.

Pair it with your account

1. Click the MiseGuard icon in the toolbar and press Show a pairing code. The extension shows a code of eight letters and digits and opens the approval page in a new tab.
2. Sign in if you are not (with your two-step code), check the code on the page matches the one in the extension, untick anything you do not want it to do, and press Approve.
3. The extension signs in by itself within a few seconds.

Approve only a code your own extension is showing right now: never one someone sent you. The page warns you when the code was started from another network. Someone viewing your account for support cannot approve a code for you.

What it shows

• The badge: how many of your sites need attention (down, or with an open issue). Empty when all is well.
• All sites: sites up and down, those needing attention, attacks blocked and malware found, the mail and form figures of the period, and one row per site with its issues and its uptime over 24 hours.
• One site: up or down now and uptime over 24 hours, 7 days and 30 days; every open issue (down, certificate or domain running out, firewall off, malware, vulnerabilities, updates waiting, a failed backup, messages in the quarantine, e-mail and DNS, privacy and CDN problems) with a link to fix it; the certificate's and the domain's days left, the firewall, the last backup, updates waiting and the forms; the recent malware, privacy and domain scans and the latest form checks; and the mail figures: messages scanned, infected, deleted, quarantined, removed (their keep date passed) and leads delivered.
• Protection: for one site, each protection switch (the form filter, the firewall and its parts, the malware scan, backups, monitoring, the CDN and the domain and privacy checks) with its state, read-only; Change in the hub opens MiseGuard → Protection for the site.
• The period: today, 7 days or 30 days, the same figures as the MiseGuard Overview and app.
• Agencies: the site switcher lists your sites by client group, and, if you allowed it, your client workspaces' sites.

A figure MiseGuard does not have yet reads Not measured yet, never 0. An area outside your package is simply not shown.

Notifications

Every few minutes (five by default) the extension looks for your new alerts: a site down, malware found or a backup failed. Each one shows once as a browser notification; a click opens it in MiseGuard. Acknowledge in the pop-up marks it read, in your notification bell too. Switch notifications off in the extension's Options.

This tab

On any website the pop-up shows its public facts: the certificate and when it expires, the security headers, the platform and its version, when the domain expires, and its SPF, DKIM and DMARC records. They are read by our server from the public website and DNS, never by the extension; only the website's name (for example www.example.com) is sent, never the page. When the website is one of yours, the pop-up shows its MiseGuard status instead. There is a limit of checks a minute and a day.

What it can do

Check now (checks the site's uptime, certificate and domain again; needs a role that manages the site), Open in MiseGuard and Acknowledge. It cannot change your firewall, restore a backup, delete anything or change a setting.

Remove it

Remove it in Chrome, sign out in its Options, or press Remove under MiseGuard → Chrome extension → Connected extensions (workspace owners and admins see everyone's). It stops at once. Signing out everywhere or changing your password removes it too. Unused for 30 days, or 90 days after pairing, it asks you to pair again.

Privacy

• What it reads: the address of the tab in front, only when you click its icon, and only to send the website's name. It has no access to the pages you visit.
• What it sends: only to your MiseGuard server, over https: the pairing (a code you approve, never your password), the website's name for the tab check, and requests for your own figures and alerts.
• What it keeps in the browser: your settings and the pairing's renewal token in this browser profile (never synced); the short-lived access token and the last figures in memory only; the ids of alerts already shown.
• What the server keeps: the public facts of a website you checked only in a short cache (six hours by default), never with your name; your pairings (name, scopes, when used) until they end; each pairing and removal in your workspace's audit log.
• What it never does: collect your browsing history or the content of pages, run code from anywhere else, or sell anything about you.