pickfit

BrowseDeveloper CLIs

dog

dog is a command-line DNS client for looking up DNS records.

Use it

Before you install: known vulnerabilities

pickfit found 16 known high or critical vulnerabilities in the packages a fresh install brings (OSV.dev, 4 Nov 2026). Weigh this before you install it.

  • crates:failure 0.1.8 Type confusion if __private_get_type_id__ is overriden (GHSA-jq66-xh47-j9f3, critical, no fix yet)
  • crates:openssl-src 111.15.0+1.1.1k SM2 Decryption Buffer Overflow (GHSA-5ww6-px42-wc85, critical, fixed in 111.16.0)
See 8 more

6 more findings not listed here.

Linux x86_64

These steps ran from a folder named work in the home folder, which already existed. Make it and run them from there:

mkdir -p "$HOME/work" && cd "$HOME/work"
  1. git clone dog source and cargo build --release with --no-default-features --features=with_idna; copy binary to ~/.local/bin

    cd "$HOME"/work && rm -rf dog && git clone --depth 1 https://github.com/ogham/dog.git && cd dog && cargo build --release --no-default-features --features=with_idna && mkdir -p ~/.local/bin && cp target/release/dog ~/.local/bin/
Verified in pickfit: the commands exactly as its sandbox ran them

For the record only: they name the sandbox's home, /home/sbx.

cd /home/sbx/work && rm -rf dog && git clone --depth 1 https://github.com/ogham/dog.git && cd dog && cargo build --release --no-default-features --features=with_idna && mkdir -p ~/.local/bin && cp target/release/dog ~/.local/bin/
dog --version
cat > /home/sbx/work/stub.py <<'EOF'
import socket, struct
s = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
s.bind(("127.0.0.1", 5353))
while True:
    data, addr = s.recvfrom(512)
    txid = data[:2]
    i = 12
    while data[i] != 0:
        i += data[i] + 1
    i += 1
    qtype, qclass = struct.unpack('!HH', data[i:i+4])
    q = data[12:i+4]
    an = 1 if qtype == 1 else 0
    resp = txid + struct.pack('!HHHHH', 0x8180, 1, an, 0, 0) + q
    if an:
        resp += b'\xc0\x0c' + struct.pack('!HHIH', 1, 1, 300, 4) + socket.inet_aton("93.184.216.34")
    s.sendto(resp, addr)
EOF
python3 /home/sbx/work/stub.py
dog example.net @127.0.0.1:5353 --color=always

Check that it works

dog --version

The output should contain “command-line DNS client”.

First thing to try

cat > "$HOME"/work/stub.py <<'EOF'
import socket, struct
s = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
s.bind(("127.0.0.1", 5353))
while True:
    data, addr = s.recvfrom(512)
    txid = data[:2]
    i = 12
    while data[i] != 0:
        i += data[i] + 1
    i += 1
    qtype, qclass = struct.unpack('!HH', data[i:i+4])
    q = data[12:i+4]
    an = 1 if qtype == 1 else 0
    resp = txid + struct.pack('!HHHHH', 0x8180, 1, an, 0, 0) + q
    if an:
        resp += b'\xc0\x0c' + struct.pack('!HHIH', 1, 1, 300, 4) + socket.inet_aton("93.184.216.34")
    s.sendto(resp, addr)
EOF
python3 "$HOME"/work/stub.py
dog example.net @127.0.0.1:5353 --color=always

What it does

  • Emit DNS results as JSON
    Tested
  • Display DNS results with colourful output
    Not shown working
  • Query using DNS-over-TLS and DNS-over-HTTPS
    Not tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Starts
  3. 1 of 3 features work
  4. Works offline

macOS and Windows: the project says it runs there; pickfit hasn’t tried it.

Good for

  • query a domain using default settings
  • look up MX records for a domain
  • query using a specific nameserver

An alternative to dig.

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

Its main function works

  • Replayed from scratch
  • Works offline
  • Checked on 16 Nov 2026
  • Version v0.2.0-pre [-tls, -https] [721440b]

Differences the test machine hit

  • README: To build, download the source code and run: cargo build
    In the test: Default features (with_tls, with_https) need OpenSSL development headers (libssl-dev / openssl-devel). Without them the build fails in openssl-sys. Here no root was available, so the build used --no-default-features --features=with_idna, which the README documents under Feature toggles.
  • README: dog example.net (default settings query)
    In the test: Not run as a smoke test: it uses the system resolver and needs network, and smoke tests run with network off. Checks used a local stub DNS server on 127.0.0.1:5353 via the @ADDR:PORT nameserver syntax, which worked.
  • README: Build with cargo build; the release binary is target/release/dog
    In the test: Installed by copying target/release/dog to ~/.local/bin. The build also prints many unexpected_cfgs warnings; they are harmless.

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.