Sendermap
Type a domain, see every service that sends email as it, and the public evidence for each one.
Status: early release (0.1.9). The command-line tool works, and the website runs at . Needs Python 3.12 or later.
에이전트 강화
게시자의 자체 명령입니다. PlugMCP 엔드포인트가 아닙니다.
Host a copy with our keys and logs.
uvx sendermap==0.1.15Claude Code에는 로컬 명령용 설치 링크가 없습니다. 아래 명령을 복사해 터미널에서 실행합니다.
claude mcp add io.github.marmot7775-sendermap -- uvx sendermap==0.1.15터미널에서 실행합니다.
{ "mcpServers": { "io.github.marmot7775-sendermap": { "command": "uvx", "args": [ "sendermap==0.1.15" ] } }}claude_desktop_config.json
원격 URL인가요, 내 컴퓨터에서 실행하는 명령인가요? 두 설치 방식의 차이
PlugMCP에서 실행
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
실행게시자 제공
Type a domain, see every service that sends email as it, and the public evidence for each one.
Status: early release (0.1.9). The command-line tool works, and the website runs at . Needs Python 3.12 or later.
Maps every service that sends email as a domain, with the public record behind each one.
For any domain, Sendermap builds a map of the services that send or receive its mail: mailbox providers, marketing and transactional platforms, support desks, security gateways and the services that receive its reports. Each one comes with:
It looks beyond the main domain: brands often send from subdomains such as email., mg. or
bounce., which a check of the main domain never sees. It also points out what needs attention:
DKIM records that point at names that no longer exist, SPF records past the 10 lookup limit,
revoked keys, and senders nobody can name. Raw IP ranges nobody can name are grouped by the
network that announces them, so a dozen ranges from one provider read as one line.
Each DKIM key is shown with the tags that change what it does: t=y (testing, so verifiers
treat mail signed with it as unsigned), t=s (strict), h= (hash algorithms), s= (service
types) and k= (key type). A tag that weakens the key, such as testing mode or SHA-1 only, is
raised as a finding. Each key also gets a fingerprint, fp and 16 hex characters, so the same
key published at two selectors is easy to spot, and the map points it out when it is.
The map also lists what it looked for and did not find, with the DNS answers that show it. Today that covers DKIM keys. Whether "not there" can be trusted depends on how the domain's DNS answers for a name that does not exist, so at each name Sendermap first asks for a selector nobody publishes and reads the answer as one of four classes:
_domainkey itself does
not exist, no selector exists under it. The map checks only the few names the domain's SPF and
MX point to, rather than its full list, and says so. If _domainkey exists but every name asked is missing, the map says selectors exist but
none of the names it tried is one.Everything comes from public sources: DNS, certificate transparency logs, the domain's own website, and public records of who owns each network. Each finding is shown with the record that supports it, so you can check it yourself.
s1, credits its service (Klaviyo) only where the
domain's SPF, MX or an NS delegation already shows that service.--ct (off by default), crt.sh is read too, since it also holds expired certificates,
and every logged name is resolved now and matched like any DNS record, so a branded tracking
link such as link.example.com pointing at an email platform shows up. A logged name that no
longer resolves but still points at a service is listed as a possible past vendor, not a
current sender. crt.sh is often slow; it is tried three times, each log's answers are cached
for a day, and a log that never answers is listed as not checked while the map finishes
without it.Run it from the command line. It installs from PyPI (Python 3.12 or later):
pip install sendermap
uvx sendermap example.com # run without installing
The latest code, ahead of a release, installs from GitHub with
pip install git+https://github.com/marmot7775/sendermap.
sendermap example.com
sendermap example.com --evidence # every piece of evidence
sendermap example.com --markdown # a summary to paste
sendermap example.com --json # everything, for scripts
sendermap example.com --ct # resolve every name in certificate logs, crt.sh too
sendermap example.com --claimed "Office 365, Mailchimp" # hold the services you were told of against the map
sendermap example.com --json --output map.json # write the map to a file
For scripts and agents: the exit code is 0 when the map was built, 2 for bad input and 3 when
the domain's own records could not be read (no map). Progress goes to stderr, and only to a
terminal, so stdout holds the map alone. sendermap --help explains every flag.
The website keeps no record of the domains looked up.
With the mcp extra, sendermap mcp serves two tools over MCP on stdio: sendermap_map, whose
structured content is the map as sendermap/1 JSON (summary or full), and sendermap_vendor,
one vendor's patterns, proofs and documented setup. The schema and the vendor list are resources.
{
"mcpServers": {
"sendermap": { "command": "uvx", "args": ["--from", "sendermap[mcp]", "sendermap", "mcp"] }
}
}
The website serves the same tools at /mcp over streamable HTTP. For agents without MCP,
skills/sendermap/SKILL.md is an Agent Skill that runs the command
line and reads the JSON.
sendermap DOMAIN --json and the site's API give one map as JSON, schema sendermap/1,
described by sendermap/data/schema/sendermap-1.json
(JSON Schema 2020-12; sendermap.schema() in Python, /schema/sendermap-1.json on the site).
sendermap/1 grows by addition only: new fields and new values (a new kind of evidence, a new
gap kind) may appear, and nothing is removed, renamed or changed in meaning. Ignore fields you do
not know and tolerate values you do not know. A breaking change would be sendermap/2.
All vendor knowledge lives in one file, sendermap/data/vendors.json, one block per
service, so adding or correcting a vendor is a small pull request. The first version was imported
from the vendor tables in dns-audit (MIT).
Each vendor gets one block in sendermap/data/vendors.json, and everything known about it goes
there. Every pattern in a block (an SPF include, an MX host, a CNAME target, a report address, a
verification token, a network, a website host, a selector name, a subprocessor name) carries one
proof of its own: a live domain that publishes it, the record name or page as found, and the
date checked (a numbered series of selectors such as s1, s2 needs one for the series). A pattern without a proof
does not get merged, and Sendermap refuses to load one. A block may also list aliases, the
other names customers call the service by ("Office 365" for Microsoft 365). An alias needs no
proof, since it matches only what a person types, never a record.
Patterns not yet proven wait in sendermap/data/vendors_pending.json, each block with a note of
what was checked; Sendermap never reads that file, so a record they would match shows as not
recognised. A vendor moves from pending to vendors.json with one proof per pattern, the same rule
as any new block. tools/hunt_proofs.py looks for those proofs on the customer domains in
data/hunt_domains.txt, with the same checks as the weekly recheck.
Which vendor to add next comes from the benchmark: tools/benchmark.py
maps the same 300 domains each release and ranks what it could not name by how many domains
publish it. On 0.1.7, 83 such groups showed at two domains or more.
Every proof is rechecked against live DNS and the web each week and on any pull request that
touches vendors.json. A proof that no longer holds opens an issue, so a stale pattern is caught
and fixed.
A tag v* builds the release files and, while the repository variable PYPI_READY is true
(Settings, Secrets and variables, Actions, Variables), publishes them to PyPI by trusted
publishing and makes the GitHub release with the tag's notes from CHANGELOG.md.
MIT
Maps every service that sends email as a domain, with the public record behind each one.
{ "mcpServers": { "io.github.marmot7775-sendermap": { "command": "uvx", "args": [ "sendermap==0.1.15" ] } }}도구
아직 도구 목록이 없습니다. 원격 서버는 첫 상태 확인 후에 도구 목록이 생깁니다.
FAQ
이 페이지에서 Cursor, Claude Desktop, Claude Code 또는 VS Code용 stdio 설정을 복사합니다. PlugMCP 프록시가 아니라 게시자의 설치 방식을 사용합니다.
이 레코드에는 필수 환경 변수가 등록되어 있지 않습니다.
Sendermap은(는) stdio를 통해 로컬에서 실행됩니다.
마지막 확인: 2026-11-17. Maps every service that sends email as a domain, with the public record behind each one.