Diagnostics and monitoring are in development

Email DNS, minus the mystery.

NettleMX is being built to help in-house email teams and agencies understand the records behind business email. Here is what the planned checks look at—and what you can do when something needs a closer look.

The checks below explain the planned scope. No live or scheduled scans are available yet.

For in-house email teams and agencies managing client domains.

NETTLEMX / EMAIL CHECKS
ILLUSTRATIVE
SAMPLE DOMAIN

company.example

NO LIVE DATA
CHECK AREASNOT RESULTS
  • SPFSender policy and includes
  • DMARCEnforcement and alignment
  • DKIMSelectors and published keys
  • MXMail-routing records
  • DNSBLDomain or sending-IP listings
  • MTA-STSDNS record and HTTPS policy
  • BIMIRecord, logo and certificate

A sample view of the settings a future diagnostic could explain.

01 / THE CHECKS

Seven records and policies, in plain English.

A diagnostic can inspect what is published and explain why it may matter. It cannot promise that a message will be accepted or land in an inbox.

  • SPF

    Who is allowed to send?

    What it inspects
    Reads the domain’s SPF TXT record, follows include and redirect chains, and checks the final policy qualifier (all).
    Why it matters
    SPF has a limit of 10 DNS-lookup terms. Too many can make evaluation fail; an overly broad policy may authorise senders you did not intend.
    A sensible next step
    Ask your email administrator to reconcile approved senders and includes, keep DNS-lookup terms within 10, then publish one consolidated SPF record through your DNS provider.
  • DMARC

    What happens when checks fail?

    What it inspects
    Reads p, subdomain sp and non-existent-subdomain np policies where present, SPF/DKIM alignment settings, and any rua aggregate or ruf failure-report destinations.
    Why it matters
    A policy can ask receivers to take no action, quarantine or reject mail that fails DMARC. Misalignment can cause legitimate mail to fail; reporting destinations may not receive every type of report.
    A sensible next step
    Review aggregate reports with your mail administrator before tightening enforcement, and make sure report addresses can receive mail from outside your organisation.
  • DKIM

    Can a receiver verify the signature?

    What it inspects
    Uses selectors from your sending services or message headers to find the matching public key or provider record under selector._domainkey.
    Why it matters
    Receivers use that public key to check a message’s DKIM signature. A missing or mismatched key can make verification fail.
    A sensible next step
    Ask each mail provider which selectors it uses, compare those with DNS, and retire old keys only after the sender no longer needs them.
  • MX

    Where should incoming mail go?

    What it inspects
    Reads the domain’s MX records and their preference numbers.
    Why it matters
    MX records tell other mail systems where to deliver incoming messages. If the domain should receive mail, incorrect destinations or priorities can cause delays or rejection.
    A sensible next step
    Confirm the exact hosts and priorities with your email provider, then make any DNS change in your DNS provider’s control panel.
  • DNSBL

    Is a sender on a blocklist?

    What it inspects
    Checks a sending IP, and relevant domain-based entries where supported, against named DNS-based blocklists.
    Why it matters
    Some receiving systems consult particular lists when deciding whether to accept or filter a message. A listing is one signal; it does not decide every receiver’s outcome.
    A sensible next step
    Check the list operator’s own evidence and removal process. If an IP is listed, confirm whether it belongs to you or your mail provider before acting.
  • MTA-STS

    Is the inbound TLS policy reachable?

    What it inspects
    Checks the _mta-sts TXT record and the HTTPS policy file’s mode and MX patterns at https://mta-sts.<your-domain>/.well-known/mta-sts.txt.
    Why it matters
    An enforce-mode policy asks supporting senders to require valid TLS for matching mail servers. A stale or unreachable file can undermine that protection; testing and none modes behave differently.
    A sensible next step
    Ask your hosting provider to serve the correct file over HTTPS and match its MX patterns to your current MX records. Update the policy ID in DNS through your DNS provider after the file is ready.
  • BIMI

    Are the brand references in place?

    What it inspects
    Reads a BIMI TXT record and checks its published SVG logo reference and any VMC or CMC certificate reference.
    Why it matters
    A compliant BIMI setup may help show a brand mark in inboxes that support it. Mailbox-provider rules vary, and display is never guaranteed.
    A sensible next step
    Ask your email or brand administrator to validate the logo, DMARC policy and certificate requirements with participating providers before changing DNS.

Review a finding with your email or DNS administrator. Publish DNS changes through your DNS provider; NettleMX does not publish them.

02 / MONITORING

Monitoring is part of the plan. It is not running yet.

NettleMX does not currently collect DNS snapshots, maintain a live scorecard or send change alerts. Monitoring is a planned part of the service, not an available feature today.

01

Notice a record change

A monitoring service could compare published records over time. NettleMX does not run scheduled checks or keep DNS snapshots today.

02

Understand the context

A changed include, alignment rule or mail route can affect sending and receiving in different ways. Review the record with the person who manages that service.

03

Update it at the source

Your email or DNS administrator can confirm the right value. DNS records are published through your DNS provider; an MTA-STS policy file is served by your HTTPS host.

Treat any proposed record as something to review, not a one-click fix. Changes belong with the provider that manages the record or policy file.

03 / FOR AGENCIES

Useful context for the domains you look after.

Agencies often work across several clients, sending platforms and DNS providers. NettleMX’s intended direction is to make those settings easier to explain and review with each client.

Client portfolios, white-label pages and shareable reports are not available yet. The panel is only a layout preview.

Discuss agency needs
AGENCY OVERVIEWPREVIEW ONLY
A POSSIBLE LAYOUT

Client domain overview

DomainReview status

No client domains or live statuses are shown in this preview.

NO CLIENT RECORDSNO SHARE LINKS

A FEW CLEAR ANSWERS

Before you change a record.

Are these checks running on my domain?

No. NettleMX does not run live or scheduled scans today. The scorecard above is illustrative, shows no live data and has not queried a domain.

Will a good result guarantee inbox placement?

No. Published DNS settings are only part of email delivery. Receiving providers also consider their own policies and other signals, so no DNS diagnostic can promise delivery or inbox placement.

Does NettleMX publish DNS changes?

No. Review a finding with your email or DNS administrator, then publish any DNS record change through your own DNS provider. NettleMX does not publish DNS. MTA-STS also uses a policy file hosted at your HTTPS web host.

Can an agency share branded reports with clients?

Not at this stage. Agency portfolios, white-label pages and shareable reports are not available. The agency panel on this page is a preview, not a working client workspace.

Can every DKIM selector be found from DNS alone?

No. A domain does not publish a complete directory of its DKIM selectors. An administrator or sending provider can identify the selectors in use; a diagnostic can then inspect the matching published keys.

A QUESTION ABOUT YOUR SETUP?

Bring your email team into the conversation.

NettleMX is happy to hear what your team or agency needs to understand.

nettlemx@polsia.io