Skip to content
Extend.Domains

Install

Two clicks, or one clone

Extend.Domains is on both stores, free, with no account and no trial. If you would rather not take a binary on trust, the whole thing is on GitHub and builds in about a minute — nothing is minified, so what you run is what you can read.

Add it to your browser

Add to Chrome Add to Firefox

What you are agreeing to: nothing

No sign-up, no email, no trial, no paid tier. The extension has no backend of its own and sends nothing anywhere — every request it makes is listed here.

A store install keeps itself up to date, so there is nothing to come back for.

Chrome 116 or newer — which also covers Edge, Brave and Arc — or Firefox 140 or newer (the current ESR).

The first minute

  1. 1

    Try it on this page

    Highlight example.com right here, right-click, and choose Look up “example.com”. The panel opens on the side with the registry record, DNS, and the rest.
  2. 2

    Pin it, and learn the shortcut

    Pin the toolbar icon so the panel is always one click away. Ctrl + Shift + L opens it too, or ⌘ + ⇧ + L on a Mac — both browsers let you rebind that on their own shortcuts page.
  3. 3

    Set it up how you like it

    Theme, registrar, which cards show and in what order, and every scoring weight — all of it is on the settings page.

One thing to do on Firefox

Host permissions are opt-in there

Under Manifest V3, Firefox withholds site access until you grant it. Without it the right-click lookup still works, but highlight-to-preview stays dormant and the site preview card shows a Grant access button instead of a page summary.

Grant it once at about:addons → Extend.Domains → Permissions → “Access your data for all websites”, or per-site from the puzzle-piece icon in the toolbar.

Build it from source

Optional — for reading the code, running your own changes, or just not wanting the store's copy. You need git, Node 22.6 or newer, and npm.

clone & build
git clone https://github.com/patriali/extend.domains.git
cd extend.domains
npm install
npm run build

That writes two builds from the one source tree: dist/chrome and dist/firefox. Each carries its own generated manifest, so the shared fields can never drift apart between the browsers.

Loading your build

Chrome

Chrome 116 or newer · also Edge, Brave, Arc

  1. 1.Open chrome://extensions
  2. 2.Turn on Developer mode (top right)
  3. 3.Load unpacked → pick the dist/chrome folder
  4. 4.Pin the toolbar icon so the panel is one click away

Chrome only accepts packed extensions that came from the Web Store, so unpacked is the way to run a build of your own.

Firefox

Firefox 140 or newer

  1. 1.Open about:debugging#/runtime/this-firefox
  2. 2.Load Temporary Add-on…
  3. 3.Pick dist/firefox/manifest.json

A temporary add-on is wiped when Firefox restarts — fine for testing a change, not for daily use. For that, install from the Add-ons listing above.

Updating

A store install updates itself; there is nothing to do. A build of your own does not, so pull and rebuild when you want the latest:

update
git pull
npm install
npm run build

Then reload the extension: the ↻ button on the card at chrome://extensions, or Reload at about:debugging.