Like dig, but for the web. Comprehensive website intelligence and metadata extraction for Raycast.
Digger surfaces contextual information about any website without needing to open developer tools. Enter a URL and instantly see metadata, SEO signals, security info, DNS records, and more.
- Page title, description, and language
- Character encoding detection
- Bot protection/WAF detection (Cloudflare, Akamai, AWS WAF, etc.)
- Open Graph tags for social sharing
- Twitter Card metadata
- JSON-LD structured data
- All meta tags at a glance
- Robots meta directives
- Canonical URL
- Sitemap detection and viewer
- robots.txt and llms.txt detection
- Content-Signal directives (from robots.txt)
- Payment Required (x402) detection — HTTP 402 status code and payment protocol headers
- Alternate/hreflang links
- Stylesheets and scripts
- Favicon, Apple Touch Icons, and Open Graph images
- SVGs on demand — inline, sprite symbols, and image, favicon and in-page CSS references — with Copy as SVG, Copy as PNG (macOS), and Export as SVG
- Font detection (Google Fonts, Adobe Fonts, Bunny Fonts, Fontshare, Fonts.com, Font Awesome, custom)
- Theme color
- View all response headers
- Security headers audit (CSP, HSTS, X-Frame-Options, etc.)
- Server identification
- HTTP status code
- HTTP 402 status code and payment protocol headers
- A, AAAA, MX, TXT, NS, and CNAME records
- TLS certificate chain information
- Certificate expiration dates
- Total snapshot count
- First and last capture dates
- Quick link to Internet Archive
- Integration with Wayback Machine extension
- RSS, Atom, and JSON feed detection
- JSON-LD structured data viewer
- Host metadata discovery (RFC 6415 XRD/JRD)
Configure these in Raycast preferences (⌘ ,):
| Option | Description |
|---|---|
| Auto Load from Clipboard | Automatically analyze URLs copied to clipboard |
| Auto Load from Selected Text | Analyze highlighted URLs in any app |
| Browser Extension Support | Analyze the current browser tab (requires Raycast Browser Extension) |
| macOS | Windows | Action |
|---|---|---|
↑ / ↓ |
↑ / ↓ |
Navigate between sections |
⌘ R |
Ctrl R |
Refresh data |
⌘ ⇧ C |
Ctrl ⇧ C |
Copy URL |
⌘ ⇧ J |
Ctrl ⇧ J |
Copy as JSON |
⌘ ⇧ M |
Ctrl ⇧ M |
Copy as Markdown |
⌘ O |
Ctrl O |
Open in browser |
⌘ ⇧ W |
Ctrl ⇧ W |
Open in Wayback Machine |
⌘ ⇧ G |
Ctrl ⇧ G |
View on Google |
In the HTTP Headers list, ⌘ ⇧ C copies a header's value and ⌘ ⌥ C copies its
name. Press ⌘ K on any section to see every action available there.
Digger is useful for:
- SEO audits — Check meta tags, canonical URLs, and structured data
- Competitive analysis — See what technologies competitors use
- Debugging — Inspect headers, redirects, and DNS records
- Security research — View certificate chains and security headers
- Content discovery — Find RSS feeds, sitemaps, and API endpoints
Digger fetches websites directly from your machine. No data is sent to third-party servers except:
- Wayback Machine API — To retrieve archive history
- DNS lookups — Standard system DNS resolution
Debug Logging (off by default, in preferences) writes detailed diagnostics to the
Raycast console. Those logs stay on your machine — nothing is uploaded — and credentials
are masked automatically: values under names like token, key, or api_key, and
Bearer tokens, are replaced with *** wherever they appear, including inside logged
objects. Masking is pattern-based, so a sensitive value under an unremarkable parameter
name — ?sid=, ?u=, a document id — can still appear in full.
Strict Redaction (also in preferences, off by default) closes that gap: every URL query
string and fragment is masked to ?*** / #***, including values no pattern can recognize.
It applies to lines written after you enable it — it cannot clean up console output that
already exists — so turn it on first, reproduce the problem, then share the new lines. It is off by default because the query string
is frequently the thing you are trying to diagnose.
Some websites use Cloudflare, Akamai, or similar services that may block or challenge automated requests. Digger will indicate when this happens.
- Large websites may take longer to analyze
- Wayback Machine API can be slow or rate-limited during peak times
Contributions are welcome! Please:
- Fork the repository
- Create a feature branch
- Submit a pull request
For bugs or feature requests, open an issue.
Built by Chris Messina and his robot helpers.
Uses:
- Cheerio for HTML parsing
- Wayback Machine API for archive data
MIT License — see LICENSE for details.
