drwho.me network and developer tools

me.drwhoPublished by drwho.meOfficial publisherv2.0.0Updated Oct 24, 2026

29 free tools: DNS, email auth (SPF, DKIM, DMARC), TLS, headers, WHOIS, dev utils.

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Free remote MCP server for domain, email-authentication and web checks plus small developer utilities, with no account or API key.

What you can do
  • Run graded domain checks: DNS, MX, DNSSEC, SPF, DMARC, DKIM, MTA-STS, TLS-RPT and a combined summary
  • Inspect TLS certificates, response headers, redirect chains and CORS preflight answers
  • Review a site's web surface: robots.txt, sitemap, page metadata, AI-crawler policy, llms.txt and security.txt
  • Look up WHOIS registration data, certificate-transparency subdomains, single DNS records and IP location and network
  • Parse user agents and run local utilities: base64 encode and decode, JWT decode, JSON formatting, URL encode and decode, UUID generation
When to use it
Useful when you want an assistant to audit how a domain is set up, check whether its email can be spoofed, debug redirects or headers, or do quick encoding and JSON tidying without leaving the chat.
Requirements
Remote streamable HTTP endpoint at drwho.me; no account, API key or headers needed. A Docker image is offered for running it locally over stdio. Fair use is 60 tool calls per hour per address, with tool listing unlimited.
Before you install
Every tool is described as read-only, but checks send the domain you name to third parties: Cloudflare DNS, ipinfo.io, crt.sh and certspotter, and the target site itself. jwt_decode does not verify signatures, so decoded claims must not be trusted. Results link to a paid graded report product.

Installation

In SourceWeft

  1. Open drwho.me network and developer tools in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/me.drwho%2Ftools/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "drwho-me-network-and-developer-tools": {
      "type": "http",
      "url": "https://drwho.me/mcp/mcp"
    }
  }
}

README

drwho.me

[drwhome MCP server]

Free tools for domains, mail and the web, and a free MCP server that gives the same tools to AI agents. No account, no API key.

  • Site: https://drwho.me
  • MCP endpoint: https://drwho.me/mcp/mcp (streamable HTTP)

DNS and most email checks run in your browser (17 of the 32 tools), so the domain never reaches drwho.me. SPF, DMARC, DKIM, TLS-RPT and the blacklist check go from your browser straight to Cloudflare's public DNS. Site checks, WHOIS and the certificate log run on the server, which does not store what you check. So do MTA-STS and the other tools that must read another site's response or open a socket.

drwho.me is built by Hikmah Technologies, the team behind Domain Posture. Each tool here checks one thing. Domain Posture runs every check at once, grades them and tells you what to fix first.

Use the MCP server

Claude Code:

claude mcp add --transport http drwho https://drwho.me/mcp/mcp

Most other clients take this shape (check your client's docs):

json
{ "mcpServers": { "drwho": { "url": "https://drwho.me/mcp/mcp" } } }

Fair use: 60 tool calls per hour per address. Listing the tools is never limited. On the website, server-side checks are limited to 60 an hour per address (30 an hour shared by requests with no address), and IP lookup to 30 an hour.

To run it yourself over stdio:

docker build -t drwho-mcp .docker run -i --rm drwho-mcp

Tools

ToolWhat it does
dossier_summaryNine DNS, email and TLS checks on a domain, one graded line each
dossier_dns, dossier_mx, dossier_dnssecDNS records, mail servers, DNSSEC
dossier_spf, dossier_dmarc, dossier_dkimEmail authentication
dossier_mta_sts, dossier_tlsrptInbound mail TLS policy and reporting
dossier_tls, dossier_headers, dossier_redirects, dossier_corsTLS certificate, response headers, redirect chain, CORS preflight
dossier_web_surface, dossier_ai_crawlers, dossier_llms_txt, dossier_security_txtrobots.txt, sitemap, page metadata, AI-crawler policy, llms.txt, security.txt
dossier_whois, dossier_ct_logRegistration data, subdomains in certificate logs
dns_lookup, ip_lookup, user_agent_parseOne DNS record type, IP location and network, user agent parsing
base64_encode, base64_decode, jwt_decode, json_format, url_encode, url_decode, uuid_generateDeveloper utilities, run locally

Every tool is read-only. A result for a domain also links to the full graded report on Domain Posture.

How it is built

TypeScript on Node 22. Hono renders the pages on the server as plain HTML. There is no client framework: two small custom elements (<dw-check>, <dw-live>) run the tools in the page. The check logic is the MIT-licensed @hikmahtech/dossier-checks package, shared by the browser, the server and the MCP server.

src/content/tools.ts   the tool list; pages, sitemap and navigation read itsrc/checks/            which checks run in the browser and which on the serversrc/reports/           turns a check result into a report: a verdict and rowssrc/lib/               pure logic for the developer tools (also used by MCP)src/client/            browser scripts, one bundle per tool kindsrc/views/             pages; tool views are found by file namesrc/mcp/               the MCP tools, the HTTP endpoint, the manifestssrc/server/            client address, rate limit, outbound network guard

docs/ADDING_A_TOOL.md explains how to add a tool.

Safety

The server fetches sites that visitors name, so it guards its own network. Before a check runs, the domain must resolve only to public addresses. On top of that, every outgoing connection is checked at the socket layer, whichever library opens it, so a redirect, a changed DNS answer or a WHOIS referral cannot reach a private address. See src/server/ssrf.ts.

The content security policy allows no inline or evaluated script.

Run it

pnpm installpnpm dev          # http://localhost:3000pnpm testpnpm lint

Configuration is in .env.example. Everything is optional: without IPINFO_TOKEN the two IP tools say they are not configured, and without GA_MEASUREMENT_ID no analytics loads. MCP tool calls are counted in a separate GA4 property set by GA_MCP_MEASUREMENT_ID and GA_MCP_API_SECRET; without both, none are sent. Each event carries the client's name and version and a caller id: a keyed hash of the caller's address whose key changes every UTC day, so GA can count distinct callers per day but never sees an address or the domain checked. Set MCP_CALLER_SALT to a long random value to keep ids stable across restarts within a day.

glama.json and server.json are generated from the code with pnpm manifests. A test fails if they are out of date.

Deploy

Dockerfile.web is the website and the hosted MCP endpoint. Dockerfile is the stdio MCP server. .paas/app.yaml is the manifest for koyracloud.

Unknown paths redirect to the same path on domainposture.com. drwho.me used to be that product's address, and links and signed documents issued then must keep working.

Licence

MIT

Source: README.md at commit 08c9c1e

Tools

29

dossier_summary

Domain summary (9 checks)

Run the nine DNS, email-authentication and TLS checks on a domain in parallel and return one graded line per check: DNS records, MX, SPF, DMARC, DKIM, DNSSEC, TLS-RPT, MTA-STS and the TLS certificate. Use it first when asked how a domain is set up or whether its email can be spoofed; then call the single dossier_* tool for any check you need the raw data for. Each line has the check id, its status, a severity (info, low, medium, high, critical) and a one-line reason, graded by the same rules as Domain Posture. It does not return raw records or fix instructions, and it leaves out the nine web and discovery checks; the full 18-check graded report is linked in the result. Returns JSON {domain, checks:[{id, status, severity, reason}], worst}. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.

Parametersdomainrequired

dossier_dns

DNS records

Fetch a domain's A, AAAA, NS, SOA, CAA and TXT records in one call. Use as the first step of a DNS review; prefer dns_lookup for a single record type or for MX, CNAME and SRV. Sends six Cloudflare DNS-over-HTTPS queries in parallel, 5 s timeout each. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.

Parametersdomainrequired

dossier_mx

MX lookup

List a domain's MX (mail exchanger) records sorted by priority. Use to see where a domain's inbound mail goes, or before checking SPF and DMARC. Queries Cloudflare DNS-over-HTTPS, 5 s timeout. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.

Parametersdomainrequired

dossier_spf

SPF checker

Find and parse a domain's SPF record into its mechanisms. Use to check which servers may send mail for a domain, or to debug delivery failures; pair with dossier_dmarc and dossier_dkim for the whole email-authentication picture. Reads TXT records over Cloudflare DNS-over-HTTPS. Reports records that contain v=spf1 but do not start with it (for example behind a hidden byte-order mark) as lookalikes that receivers discard, and treats more than one SPF record as an error, as RFC 7208 requires. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.

Parametersdomainrequired

dossier_dmarc

DMARC checker

Find and parse the DMARC policy at _dmarc.<domain> into its tags (p, sp, pct, rua, ruf, adkim, aspf). Use to see whether spoofed mail is rejected, quarantined or only reported. Queries Cloudflare DNS-over-HTTPS, 5 s timeout. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.

Parametersdomainrequired

dossier_dkim

DKIM lookup

Probe a domain for DKIM public keys at <selector>._domainkey.<domain>. Pass selectors when you know them; omit to probe a built-in list of common selectors used by large mail providers. A selector not on the list will not be found, so an empty result does not prove the domain has no DKIM. Distinguishes a selector that is absent from one that could not be resolved. Parallel Cloudflare DNS-over-HTTPS TXT queries. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.

Parametersdomainrequiredselectors

dossier_dnssec

DNSSEC checker

Check whether a domain's zone is signed with DNSSEC and validates: DS and DNSKEY records plus the resolver's AD (authenticated data) flag. Queries Cloudflare DNS-over-HTTPS with DO=1, 8 s timeout. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.

Parametersdomainrequired

dossier_tlsrpt

TLS-RPT checker

Look up a domain's SMTP TLS Reporting policy at _smtp._tls.<domain>. Use to confirm the domain receives reports about failed TLS delivery of its inbound mail. Queries Cloudflare DNS-over-HTTPS. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.

Parametersdomainrequired

dossier_mta_sts

MTA-STS checker

Fetch and validate a domain's MTA-STS policy (mode, mx, max_age). Use to confirm inbound mail to the domain must be delivered over TLS. Resolves the _mta-sts TXT record, then fetches https://mta-sts.<domain>/.well-known/mta-sts.txt, 10 s timeout. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.

Parametersdomainrequired

dossier_tls

TLS certificate

Read the TLS certificate a domain presents on port 443: subject, issuer, validity dates, days remaining, subject alternative names, SHA-256 fingerprint and whether the chain validated. Use to check expiry or a name mismatch. It does not test cipher suites or protocol versions. One TLS handshake from the drwho.me server, 5 s timeout. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.

Parametersdomainrequired

dossier_redirects

Redirect chain

Trace the redirect chain from https://<domain>/, one entry per hop with its status code and target, up to 10 hops. Use to debug redirect loops or confirm an HTTP to HTTPS or apex to www redirect. 5 s per hop. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.

Parametersdomainrequired

dossier_headers

Security headers

Fetch https://<domain>/ and return every response header, so you can review Strict-Transport-Security, Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy and Permissions-Policy. Returns the final URL after redirects and the headers as served. One GET, 5 s timeout. For the redirect hops themselves use dossier_redirects. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.

Parametersdomainrequired

dossier_cors

CORS checker

Send a CORS preflight (OPTIONS) to https://<domain>/ and return the access-control-* headers in the answer. Use to check whether a site accepts cross-origin requests from a given origin and method. One request, 5 s timeout. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.

Parametersdomainrequiredmethodorigin

dossier_web_surface

Web surface

Summarise a domain's public web surface: robots.txt, sitemap.xml and the home page's title, description, OpenGraph and Twitter card tags. Use for a quick SEO or link-preview review. Three parallel HTTPS fetches capped at 64 KB each. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.

Parametersdomainrequired

dossier_ai_crawlers

AI-crawler policy

Report what a domain's robots.txt says to the major AI crawlers (GPTBot, ClaudeBot, Google-Extended, PerplexityBot, CCBot, meta-externalagent): allowed, blocked or unspecified for each. Use to answer whether a site lets AI models train on or retrieve its content. A missing robots.txt is data, not an error: every crawler is then unspecified. One fetch, 10 s timeout. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.

Parametersdomainrequired

dossier_llms_txt

llms.txt checker

Check whether a domain publishes an llms.txt, the markdown index some sites provide for AI agents. Requires a non-HTML content type and a leading markdown heading, so a catch-all page that answers 200 with HTML does not count. One fetch, 10 s timeout. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.

Parametersdomainrequired

dossier_security_txt

security.txt checker

Check whether a domain publishes /.well-known/security.txt (RFC 9116), the standard way to tell researchers where to report a vulnerability. Returns the Contact and Expires fields. Requires a non-HTML content type and a Contact field. One fetch, 10 s timeout. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.

Parametersdomainrequired

dossier_whois

WHOIS lookup

Look up a domain's registrar, creation date, expiry date and registry statuses. Use for an ownership or expiry check. Tries WHOIS over TCP port 43, then RDAP over HTTPS when the registry refuses; returns not_applicable when neither answers, which is common for some country-code domains. 15 s timeout. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.

Parametersdomainrequired

dossier_ct_log

Certificate log lookup

List subdomains of a domain that appear in Certificate Transparency logs. Use to map what hosts a domain has exposed through the certificates issued for it. Queries crt.sh, then certspotter if crt.sh fails; capped at 100 unique names, 10 s timeout. A name in the log is not proof the host still exists. Returns JSON with a status field: {status:"ok", data, fetchedAt} on success, {status:"not_applicable", reason} when the thing is genuinely absent, {status:"timeout", ms}, or {status:"error", message} when it could not be determined. Treat not_applicable as a finding and error as unknown.

Parametersdomainrequired

dns_lookup

DNS lookup

Resolve one DNS record type (A, AAAA, MX, TXT, NS, CNAME, SOA, CAA or SRV) for a name and return the raw answers. Use for a quick, targeted lookup, including on subdomains and names such as _dmarc.example.com; prefer dossier_dns for a domain's main records in one call. Queries Cloudflare DNS-over-HTTPS. Returns a JSON array of {name, type, TTL, data}; an empty array means the name exists but has no record of that type.

Parametersnamerequiredtyperequired

ip_lookup

IP lookup

Look up an IPv4 or IPv6 address: city, region, country, coordinates, timezone and the network (ASN and organisation) that announces it. Use when you need location or ownership context for an address; it does not accept hostnames, so resolve those with dns_lookup first. Data comes from ipinfo.io and location is approximate. Returns JSON {ip, city, region, country, loc, org, timezone}.

Parametersiprequired

user_agent_parse

User agent parser

Parse a User-Agent header into browser, operating system, device and rendering engine. Use when reading server logs or request headers. Runs locally with no network call. Returns JSON {browser:{name,version}, os:{name,version}, device:{type,vendor,model}, engine:{name}}; unknown fields are empty strings.

Parametersuarequired

base64_encode

Base64 encode

Encode UTF-8 text as base64. Set url_safe for the URL-safe alphabet (- and _ in place of + and /, no padding), as used in JSON Web Tokens. Runs locally. Returns the encoded string.

Parameterstextrequiredurl_safe

base64_decode

Base64 decode

Decode base64 to UTF-8 text. Accepts the standard and the URL-safe alphabet, with or without padding or line breaks. Fails when the input is not valid base64 or does not decode to text (binary data is not returned). Runs locally.

Parameterstextrequired

jwt_decode

JWT decoder

Decode a JSON Web Token's header and payload. It does NOT verify the signature, so never treat the claims as trusted on the strength of this tool. Use to inspect claims such as exp, iss and aud while debugging. Runs locally; the token is not stored or sent anywhere. Returns JSON {header, payload, signature}.

Parameterstokenrequired

json_format

JSON formatter

Validate JSON and re-print it with an indent of 2 or 4 spaces, or minified with indent 0. Use to check whether a string is valid JSON or to make it readable. Runs locally. Returns the formatted JSON, or the parser's error message.

Parameterstextrequiredindent

url_encode

URL encode

Percent-encode text for use in a URL query value or path segment (encodeURIComponent rules: everything except letters, digits and - _ . ! ~ * ' ( ) is encoded). Runs locally. Returns the encoded string.

Parameterstextrequired

url_decode

URL decode

Decode percent-encoded text. Fails on a malformed sequence such as a lone % sign. A plus sign is left as a plus; replace it with a space first if the text came from an HTML form. Runs locally.

Parameterstextrequired

uuid_generate

UUID generator

Generate UUIDs. Version 4 is fully random. Version 7 starts with a millisecond timestamp, so values sort by creation time, which suits database keys. Runs locally with a cryptographic random source. Returns a JSON array of strings.

Parameterscountversion

Version history

2
  1. v2.0.0LatestSep 17, 2026
  2. v0.1.0Sep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts