What this screen is for
The panel is everything your account holds: the Dashboard, the domains you monitor, your check history, your organisation and the people on it, your API tokens and your profile. It is one page with a sidebar rather than six pages, for the reason in the last section.
How to move around it
Navigation is the sidebar on the left. It lists every section, grouped -
the Dashboard on its own, then Email security, then Your account. The
section you are in is marked three ways at once: an accent bar, heavier text, and
aria-current, so a screen reader announces it and nobody has to see a colour
to know where they are.
Every item is an ordinary link, so Tab reaches it and Enter opens it. Once one has focus, Up and Down move between sections without leaving the keyboard.
Along the top of the content area is a breadcrumb trail - your panel, the group, then the section you are looking at. On a narrow screen the sidebar folds into a Sections button above the content, which names the section you are in and opens the list; picking one closes it again, and Escape closes it too.
What each section shows
- Dashboard
- The landing screen: whether mail can be forged as you right now, what changed recently, and what to do next. It has its own help page, including why a tile is sometimes deliberately blank.
- Domains
- The domains whose DMARC reports we collect. Free covers 1; Pro allows up to 5. See plans and limits.
- Check history
- Every check run on this account, newest first - including any you ran anonymously before signing up.
- Organisation
- Your organisation, the plan it is on and what that plan permits - including the meter showing domains used against the plan limit - and who holds a seat. See organisations, seats and roles.
- API tokens
- Credentials that let a script or an MCP client act on this organisation. See API tokens.
- Profile
- The account you are signed in as.
Beside Sign out at the top of the panel, Help opens this page, and the arrow next to it opens the rest of the account help. That control is the way in to all of it - account help is not in the site header, and the public help for the free check and the thirteen checks is at /help/ instead.
When a section says something is unavailable
Several routes deliberately refuse an interactive session, because the session is not scoped to a single organisation and the API will not guess which one you meant. Where that happens the section says so in the API's own words and names what is missing.
That is a design choice, not a bug being hidden: a screen of plausible rows would look like success and conceal that the feature does not work. Nothing in the panel invents data.
What this screen does not do
A refresh signs you out, and several actions are not built
The session lives in memory only, so reloading ends it. Signing in again takes seconds; the durable fix is an httpOnly session cookie from the API and it is not built yet.
Not built from the panel today: creating an API token, inviting a member, editing your profile, and adding a domain to monitoring. Each of those views says so where it applies rather than showing a button that fails.
The empty panel is delivered to the sign-in page, and that is deliberate
Because the session lives in memory, signing in must not load a new document - so the sign-in and sign-up pages carry this panel already, hidden, and swap to it in place. Its structure is therefore in the page source before you sign in, and anybody can read it.
What is in that structure is the section names and the sentence under each one - the same words this help page publishes openly. No name, no address, no count and no identifier belonging to any account is ever written into it: every one of those arrives afterwards, from a call made with your session. Nothing is rendered and no call is made until the guard confirms one.
When the API can set the session as an httpOnly cookie, the panel becomes a page of its own and the sign-in page stops carrying it at all.