DMARC reports
Gmail, Outlook, Yahoo and most other large mail providers send a daily report to every domain that asks for one. Each report lists the servers that sent mail claiming to be from your domain, how many messages each sent, and whether they passed SPF, DKIM and DMARC. Tissue Mast takes those reports in, reads them, and shows you who is sending as your domain. When a server you've never seen starts sending as you and failing, it pages you.
Add a domain under Email in the web app. Mast gives you an address for it, and you put that address in the domain's DMARC record.
Adding a domain
Add a domain asks for the domain in your From: addresses, like example.com. You get an address shaped like this:
k3vq2xw7mnc4rdy5@dmarc.tissue.systemsEach domain has its own address. The same address takes aggregate reports (rua), failure samples (ruf) and TLS reports, and Mast sorts them by what arrives.
Then publish the record at your DNS host. With no DMARC record yet, add a TXT record at _dmarc.example.com:
v=DMARC1; p=none; rua=mailto:k3vq2xw7mnc4rdy5@dmarc.tissue.systemsp=none asks receivers to deliver your mail the way they do today and only send reports. Keep it there until the sources page shows nothing of yours failing, then move to quarantine and reject.
If you already have a record, keep it and add our address to its rua list, after a comma. Every address in the list gets every report, so a service you already send reports to keeps getting them:
v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com,mailto:k3vq2xw7mnc4rdy5@dmarc.tissue.systemsThe setup page shows the record your domain has now and the exact record to publish in its place, with our address added.
Checking
A domain is waiting for DNS until Mast finds its address in the domain's _dmarc record. Check DNS looks straight away, once every 10 seconds at most, and Mast looks again every day by itself. Finding the address there is the proof the domain is yours, since only someone who runs its DNS could have put it there, so there's no other record to add.
Reports that arrive before the check are kept. Google and Microsoft send one report a day, so the first numbers usually turn up within about 24 hours of the record going live.
If the record stops naming our address, the domain stays as it is for 7 days, in case you're in the middle of an edit. After that it's lapsed, and reports sent to its address are refused until you publish it again and check.
One account at a time can hold a domain. If another account already has it, adding it answers 409. The domain frees up 7 days after its record stops naming that account's address.
A new address
New address on the setup page issues a fresh address, for when the old one turned up somewhere it shouldn't. The old one keeps working for 7 days while you publish the new record. The address is on show to anyone who looks up your _dmarc record, so the most anyone can do with it is send reports that claim to be from a receiver. Mast checks each report's own DKIM signature, and rows from a report that doesn't pass are kept out of the sources page unless you ask to see them.
Sources
A domain's main page shows the last 7, 30 or 90 days: how many messages the reports covered, the share that passed DMARC, the share with aligned DKIM and aligned SPF, and a bar for each day split into passed and failed.
Below that, Who sends as lists every sending IP the reports named, busiest first, with its reverse DNS name, its message count, and how many of its messages passed DMARC, had aligned DKIM and had aligned SPF. A source we saw for the first time in the window is marked new.
A message passes DMARC when DKIM or SPF passes for your domain itself, not for some other domain. A newsletter service that signs with its own domain passes DKIM but fails DMARC for you; set it up to sign as your domain and it passes. Most sending services have a domain authentication page that gives you the DKIM record to publish.
Open a source to see it by receiver: each report that named it, the SPF and DKIM results with the domains they were for, whether it passed DMARC, and what the receiver did with the mail (delivered, quarantined or rejected). The page reads the 15 newest reports in the window for this, and says so when there are more.
Paging on a new source
A new sending IP that fails DMARC the first time it shows up, and has sent more than 10 messages, pages the domain's alert source once. A source that keeps failing doesn't page again. One that fails with only a few messages, like a forwarder or a test, shows on the page without paging.
Reports
Reports lists every aggregate report in the window: who sent it, the day it covers, its message and failure counts, and whether its own mail was signed. Open one to see each row the receiver sent, the policy it saw on your domain, and Download the XML for the original file.
Originals are kept for 30 days on every plan. The Company plan keeps them for 400 days.
Failure samples
Some receivers also send a copy of the headers of single messages that failed DMARC. To ask for them, add ruf with the same address, and fo=1 to get a sample when either SPF or DKIM fails:
v=DMARC1; p=none; rua=mailto:k3vq2xw7mnc4rdy5@dmarc.tissue.systems; ruf=mailto:k3vq2xw7mnc4rdy5@dmarc.tissue.systems; fo=1Failure samples come with the Company plan. On other plans they're turned away when they arrive. Mast keeps the headers for 30 days and throws away any message body as soon as it arrives. Only a few receivers send these, and most take out the body and personal fields first, so treat them as examples, not counts.
TLS reports
TLS reports are about mail coming in to your domain. Servers that deliver to you report how many of their connections to your mail servers succeeded over TLS, and why the others failed. To get them, add a TXT record at _smtp._tls.example.com with the same address:
v=TLSRPTv1; rua=mailto:k3vq2xw7mnc4rdy5@dmarc.tissue.systemsTLS reports on the domain's page lists them by day and receiver.
Limits
| Plan | Domains | Reported messages a month | Failure samples | Originals |
|---|---|---|---|---|
| Free | 1 | 100,000 | no | 30 days |
| Team | 10 | 2 million | no | 30 days |
| Team 10 (closed) | 10 | 2 million | no | 30 days |
| Company | 100 | 50 million | yes | 400 days |
A domain that has had no mail reported for 30 days doesn't count toward the domain cap. Adding one past the cap answers 402 plan_limit.
The monthly number counts the messages the reports describe, not the reports. Past it, reports are still taken in, so receivers don't retry them for days, but for the rest of the month each one is kept as its totals only, without the per-source rows, and the page says so. Reports and their rows are kept for the plan's history.
From the API
With a token that has mast:read (and mast:write to change anything):
curl -s https://api.tissue.systems/v1/mast/mail/domains \
-H "Authorization: Bearer $TISSUE_TOKEN"
curl -s -X POST https://api.tissue.systems/v1/mast/mail/domains \
-H "Authorization: Bearer $TISSUE_TOKEN" -H "Content-Type: application/json" \
-d '{"domain": "example.com"}'The answer to the second carries the token and the exact rua to publish. The API lists every route.