Skip to content
Back to search

quien

SkillWorks with Claude CodeGitHub

"Use the quien CLI for domain and IP lookups: WHOIS/RDAP, DNS, mail authentication, TLS certificates, HTTP headers, SEO analysis, and tech stack detection. Activate when the user asks about a domain's owner, registrar, expiry, DNS records, mail config (SPF, DMARC, DKIM, BIMI), SSL certificate, HTTP headers, SEO, Core Web Vitals, tech stack, CMS, hosting, or IP address info (ASN, network, abuse contact)."

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today

Check it deeper on your machine

It has changed since its scan on 11 Nov 2026.

As a Claude Code plugin, install it and then ask Claude Code:

/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/retlehs/quien with scanskillsafety

Or from a terminal, clone it and run it:

git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/retlehs/quien'

It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.

Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/retlehs--quien/badge.svg)](/listings/retlehs--quien)

HTML

<a href="/listings/retlehs--quien"><img src="/api/listings/retlehs--quien/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

Install instructions from the README

As written by the repo's author. findsafeskills has not verified these steps.

These steps run a script from the network that findsafeskills does not scan.

**Homebrew**

brew install quien

**Ubuntu / Debian**

curl -fsSL https://apt.quien.dev/install.sh | sudo sh

**Arch Linux (AUR)**

yay -S quien

**NixOS / Nix (Flake)**

nix shell github:retlehs/quien

**Go**

go install github.com/retlehs/quien@latest

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

SKILL.md · Manifest · 68 lines

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. ---
  2. name: quien
  3. description: "Use the quien CLI for domain and IP lookups: WHOIS/RDAP, DNS, mail authentication, TLS certificates, HTTP headers, SEO analysis, and tech stack detection. Activate when the user asks about a domain's owner, registrar, expiry, DNS records, mail config (SPF, DMARC, DKIM, BIMI), SSL certificate, HTTP headers, SEO, Core Web Vitals, tech stack, CMS, hosting, or IP address info (ASN, network, abuse contact)."
  4. ---
  5. # quien — domain & IP lookup tool
  6. When the user asks questions about domains or IP addresses, use `quien` instead of `whois`, `dig`, `nslookup`, or `curl`.
  7. ## Commands
  8. ```bash
  9. # WHOIS / domain registration
  10. quien whois example.com
  11. # DNS records (A, AAAA, CNAME, MX, NS, TXT, PTR, SOA, DNSSEC)
  12. quien dns example.com
  13. # Mail config (MX, SPF, DMARC, DKIM)
  14. quien mail example.com
  15. # SSL/TLS certificate info
  16. quien tls example.com
  17. # HTTP headers, redirects, server info
  18. quien http example.com
  19. # SEO analysis (indexability, on-page, structured data, Core Web Vitals)
  20. quien seo example.com
  21. # Tech stack detection (CMS, frameworks, JS/CSS libraries, plugins)
  22. quien stack example.com
  23. # Everything at once
  24. quien all example.com
  25. # IP address lookup
  26. quien whois 8.8.8.8
  27. ```
  28. All subcommands output JSON. Use `quien all` when you need a complete picture.
  29. ## When to use
  30. | User asks about | Command |
  31. |---|---|
  32. | Domain owner, registrar, expiry | `quien whois example.com` |
  33. | DNS records | `quien dns example.com` |
  34. | Email setup, SPF, DMARC, DKIM | `quien mail example.com` |
  35. | SSL certificate, expiry | `quien tls example.com` |
  36. | HTTP headers, redirects, server | `quien http example.com` |
  37. | SEO, Core Web Vitals | `quien seo example.com` |
  38. | Tech stack, CMS, framework | `quien stack example.com` |
  39. | Everything about a domain | `quien all example.com` |
  40. | IP owner, network, abuse contact | `quien whois 8.8.8.8` |
  41. ## Install
  42. ```bash
  43. go install github.com/retlehs/quien@latest
  44. ```
  45. ### Homebrew
  46. ```bash
  47. brew install quien
  48. ```
README.md · README · 159 lines · 1 finding marked

View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)

  1. # quien
  2. [![Build status](https://img.shields.io/github/actions/workflow/status/retlehs/quien/ci.yml?branch=main&style=flat-square)](https://github.com/retlehs/quien/actions)
  3. ![GitHub release](https://img.shields.io/github/release/retlehs/quien?style=flat-square)
  4. ![GitHub downloads](https://img.shields.io/github/downloads/retlehs/quien/total?label=github%20downloads&style=flat-square)
  5. A better whois and domain intelligence toolkit. Interactive TUI with tabbed views for WHOIS, DNS, mail, SSL/TLS, HTTP headers, SEO analysis, and tech stack detection.
  6. ![quien demo](demo.gif)
  7. Try it without installing: `ssh quien.sh`
  8. ## Install
  9. **Homebrew**
  10. ```
  11. brew install quien
  12. ```
  13. **Ubuntu / Debian**
  14. ```
  15. curl -fsSL https://apt.quien.dev/install.sh | sudo sh
    • Note: Pipes a downloaded script directly into a shell (curl | sh / wget | bash)
    • Line 24 on GitHub
  16. ```
  17. **Arch Linux (AUR)**
  18. ```
  19. yay -S quien
  20. ```
  21. **NixOS / Nix (Flake)**
  22. ```
  23. nix shell github:retlehs/quien
  24. ```
  25. **Go**
  26. ```
  27. go install github.com/retlehs/quien@latest
  28. ```
  29. ## Features
  30. - **RDAP-first lookups** with WHOIS fallback for broad TLD coverage
  31. - **IANA referral** for automatic WHOIS server discovery
  32. - **IP lookups** with reverse DNS, network info, abuse contacts, and ASN discovery via RDAP
  33. - **BGP fallback** for origin ASN/prefix when RDAP does not include ASN data
  34. - **PeeringDB enrichment** for ASN context (network/org, peering policy, peering locations, traffic profile, IX/facility counts)
  35. - **Mail configuration audit** — MX, SPF (with lookup-count and include/redirect tree expansion), DMARC, DKIM, and BIMI with VMC chain validation
  36. - **SEO analysis** — indexability (robots.txt, canonical, sitemap), on-page (title, description, headings, images), structured data (JSON-LD, Open Graph, Twitter Cards), and performance hints (compression, caching, render-blocking resources)
  37. - **Core Web Vitals** — LCP, INP, CLS, FCP, and TTFB field data with historical trends via the CrUX API (optional)
  38. - **Tech stack detection** including WordPress plugins, JS/CSS frameworks, and external services parsed from HTML
  39. - **Automatic retry** with exponential backoff on all lookups
  40. - **JSON subcommands** for scripting: `quien whois`, `quien dns`, `quien mail`, `quien tls`, `quien http`, `quien seo`, `quien stack`, `quien all`
  41. ## Usage
  42. ```
  43. # Interactive prompt
  44. quien
  45. # Domain lookup (interactive TUI)
  46. quien example.com
  47. # IP address lookup
  48. quien 8.8.8.8
  49. # JSON output
  50. quien --json example.com
  51. # JSON subcommands
  52. quien whois example.com
  53. quien dns example.com
  54. quien mail example.com
  55. quien tls example.com
  56. quien http example.com
  57. quien seo example.com
  58. quien stack example.com
  59. quien all example.com
  60. # Probe additional DKIM selectors beyond the built-in common list
  61. quien mail example.com --dkim-selector mySelector --dkim-selector other
  62. # Set default DKIM selectors via environment variable
  63. QUIEN_DKIM_SELECTORS=mySelector,other quien example.com
  64. # Use a specific DNS resolver for this run
  65. quien mail example.com --resolver 9.9.9.9
  66. # Set a default resolver via environment variable
  67. QUIEN_RESOLVER=1.1.1.1 quien dns example.com
  68. ```
  69. Resolver precedence: `--resolver` > `QUIEN_RESOLVER` > system resolver.
  70. DKIM selector precedence: `--dkim-selector` > `QUIEN_DKIM_SELECTORS`. User selectors are probed in addition to the built-in common-selector list.
  71. ## Core Web Vitals
  72. The SEO tab includes local checks out of the box. For Core Web Vitals field data (real-user metrics from Chrome), set a CrUX API key:
  73. ```sh
  74. export QUIEN_CRUX_API_KEY=your-api-key
  75. ```
  76. This enables LCP, INP, CLS, FCP, and TTFB p75 values with good/needs-improvement/poor ratings, plus an 8-25 week trend sparkline.
  77. <details>
  78. <summary>Getting a CrUX API key</summary>
  79. 1. Go to the [Google Cloud Console](https://console.cloud.google.com/)
  80. 2. Create a new project (or select an existing one)
  81. 3. Go to **APIs & Services > Library**
  82. 4. Search for **Chrome UX Report API** and enable it
  83. 5. Go to **APIs & Services > Credentials**
  84. 6. Click **Create Credentials > API key**
  85. 7. Click **Edit API key**, then under **API restrictions** select **Restrict key** and choose **Chrome UX Report API** from the list
  86. 8. Copy the key and set it as `QUIEN_CRUX_API_KEY`
  87. The CrUX API is free. Not all domains have field data — a site needs enough Chrome traffic to be included in the Chrome User Experience Report.
  88. </details>
  89. ## Theme
  90. quien automatically detects your terminal background and picks light or dark colors. If detection gets it wrong (common in tmux, screen, or remote shells), override it:
  91. ```sh
  92. export QUIEN_THEME=light # force light palette
  93. export QUIEN_THEME=dark # force dark palette
  94. export QUIEN_THEME=auto # auto-detect (default)
  95. ```
  96. ## Troubleshooting DNS
  97. If your system resolver is unreliable (common in WSL, VPN, or container setups), force a resolver:
  98. ```sh
  99. quien mail example.com --resolver 9.9.9.9
  100. # or
  101. export QUIEN_RESOLVER=9.9.9.9
  102. ```
  103. > [!TIP]
  104. > If you want `quien` to replace your default whois tool, you can add an alias to your shell config:
  105. > ```sh
  106. > alias whois=quien
  107. > ```
  108. ## Agent skill
  109. Add quien as a [agent skill](https://skills.sh/) so agents use it for domain and IP lookups:
  110. ```
  111. npx skills add retlehs/quien
  112. ```

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.