Sharing your record.

Where the link goes

• In proposals and quotes, where it demonstrates the business is looked after by somebody
• In the footer of your site, where it sits permanently at no effort
• In partner and supplier onboarding, where the same questions get asked every time
• In responses to insurers and procurement, in place of assembling documentation
• In client reporting, if you are an agency looking after somebody else's domain

What it saves

The questions that arrive from outside are repetitive and time consuming: is this looked after, since when, has anything lapsed, who is responsible. Answering them individually costs an hour each time and produces an assurance rather than evidence.

A link answers all of them at once, from a source the other side can check for themselves, which is a materially stronger position than being believed.

Control over what is shown

The page is public once you publish it, because it is meant to be shared, and it shows only public facts about a domain. It carries a no-index instruction, so it is found by being sent to somebody rather than by being searched for. You can take it down at any time, and the address stays reserved for you, so a link you sent last year works again if you put it back.

Publishing asks for one DNS record first, to show the domain is yours. If you signed up with an address at the domain, that already counts and there is nothing to add. Separately, you choose whether the page names what changed. Off by default: the dates and the severity are published either way, but "the DMARC record was removed" tells a spoofer the domain is spoofable, and that is not something to publish by accident.

Knowing it is read

On every paid plan, the record notes when it was opened by someone outside the business. Two things follow from that. You find out whether anyone is actually reading it, which tells you whether sharing it is worth doing. And the access history becomes part of the record itself.

It reports how many times and by how many different people, and nothing beyond that, because nothing beyond that is kept. A reader is reduced to a key that expires at midnight before anything is written down, and the address and browser it was built from are never stored anywhere. So the record can tell you four people read it on Tuesday. It cannot tell you who they were, and it cannot tell you that one of them came back on Wednesday, because Wednesday's key is a different key and none of this works backwards. Crawlers and link previews are not counted as readers. Neither are you, so checking your own record does not report itself back to you as interest.

One honest note

If you never share the link, this is a private monitoring tool with a good memory, which is still worth having. The published record only does its job if it ends up somewhere other people encounter it, so it is worth putting in one durable place rather than sending it once and forgetting.

For what the other side is actually asking, see what procurement actually asks.