mxcheck
v2.0.0 open-sourceThe section your link pointed to isn't on mxcheck's page any more, so we've brought you to the top.
Info scanner for e-mail servers checking DNS records, DANE/TLSA, TLS, open ports, blacklists, SMTPSmuggling, and open relay status.
mxcheck --verbose example.com mxcheck -g -target mail.example.com mxcheck -p <domain>
Summary
mxcheck is an open-source, free command-line scanner that audits an e-mail server's DNS and transport security posture, checking MX, SPFSPFAn email authentication standard that lets a domain owner publish, via DNS, which mail servers are authorized to send on its behalf, so receiving servers can reject spoofed senders., DKIMDKIMAn email authentication standard that lets a sending mail server cryptographically sign outgoing messages so receiving servers can verify the signature was not forged or tampered with in transit., DMARC, MTA-STSSTSAWS Security Token Service, an Amazon Web Services API that issues short-lived credentials for IAM roles, letting cyber tools authenticate to AWS without storing long-term secrets., TLSRPT, BIMI and DANE/TLSA records alongside StartTLS support, open ports, blacklist status and SMTPSMTPThe application-layer protocol used to send email between servers and from clients to servers; cyber tools use it to relay alerts, phishing simulations, or exfiltrated data over standard mail infrastructure. smuggling vulnerability. It runs as a single Go binary against a target domain, with flags to set a DNS server, DKIM selector, disable port scanning or write a TSVTSVA plain-text format storing tabular data with fields separated by tab characters, making it easy for cyber tools to parse and exchange structured records without a CSV parser's quoting complexity. report, which suits mail administrators and security engineers auditing mail infrastructure rather than broad network recon. It sits in the reconnaissance category alongside other DNS and mail-hygiene checkers, focused specifically on the mail-server surface. First committed in 2018 and still active, with 7 contributors and 26 commits in the past year across seven tracked releases, the most recent 136 days ago.
Info scanner for e-mail servers checking DNS records, DANE/TLSA, TLS, open ports, blacklists, SMTPSmuggling, and open relay status.
How mxcheck helps
Which of my e-mail authentication records are missing or misconfigured before a spammer or auditor finds out?
parses SPF, DKIM, DMARC, MTA-STS, TLSRPT and BIMI for the domain and reports each record's presence and content, so gaps in the authentication chain show up directly
Is my mail server exposing a transport-layer weakness right now?
connects to each MX host to check StartTLS support, pulls the TLS certificate details and checks DANE/TLSA records against the host's certificate, flagging mismatches or missing pinning
Is my mail server vulnerable to SMTP smuggling?
actively probes the target server for the smuggling behavior and reports whether the vulnerability is present
Has my domain's mail service ended up on a blacklist?
checks the service against blacklist sources and reports listing status alongside the rest of the scan
Is my server unintentionally relaying mail for anyone who asks?
sends test messages using configurable mailFrom and mailTo addresses, from both external and local perspectives, to check whether the server accepts and forwards mail it shouldn't
Which ports and information leaks on my mail server would a scan from outside reveal?
scans ports 25, 465 and 587 and inspects the server banner and VRFY command response to show what an external prober would learn, with an option to skip the port scan where probing isn't wanted
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for mxcheck, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail mxcheck puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
7 entries
No entries match these filters.
- April 20261
- March 20261
- November 20251
- June 20251
- March 20241
- May 20231
- March 20221
Project health
Issue, contributor and maintainer activity in steffenfritz/mxcheck, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 2 −1 vs prior 12 months
- Maintainers 2 +1 joined · −1 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 0% of issues opened, last 12 months
- Median time to close < 1 day first maintainer reply 0.5 hours
- Open backlog 0 of 27 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 0
- Contributors / month 0
- Commits / month 0
- Stars 146
- features 50%
- other 50%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.