Skip to content
NewSee how
Fix

Email authentication Details tab matches the Technical tab

The Details tab in email authentication no longer shows a stale zero percent score, and the Technical tab no longer flashes a status banner before settling.

The email authentication section of FirstSales had two related display bugs where the Details tab and the Technical tab could tell you different, and sometimes wrong, stories about the same mailbox. Both are fixed, so the two tabs now stay in sync and show you an accurate picture of your authentication status.

What changed

In a mailbox's email authentication settings, the Details tab shows a summary score for how well your domain is authenticated, and the Technical tab shows the underlying record-by-record breakdown, SPF, DKIM, DMARC, and so on. Previously, the Details tab could get stuck showing a stale score of zero percent, even after your domain's actual authentication had improved or fully passed. If you glanced at the Details tab to get a quick read on your status, a lingering zero percent score made it look like nothing was configured correctly, even when the Technical tab underneath showed records that were actually passing.

Separately, the Technical tab had a visual glitch where its status banner would flash briefly, showing one state and then flipping to another, before settling on the correct status. That flash didn't change your actual authentication status, but it made the tab feel unreliable to read, especially if you happened to glance at it during that brief flicker and took the first thing you saw at face value.

Both issues are fixed. The Details tab score now reflects your domain's current authentication state accurately instead of getting stuck on a stale value, and the Technical tab renders its status banner cleanly on load instead of flashing between states.

How to use it

Open a mailbox's email authentication settings and check the Details tab for a summary of your authentication score. That score now reflects your actual current status, so if your domain's SPF, DKIM, and DMARC records are properly configured, you'll see that reflected in the score rather than a leftover zero percent from before your records were set up.

Switch to the Technical tab to see the full breakdown record by record. The status banner at the top now shows the correct state on load, without flashing through an intermediate state first, so what you see the moment the tab renders is the state you can act on.

If you've recently fixed a DNS record and want to confirm the change is reflected, check both tabs: the Details tab should show an updated score, and the Technical tab should show the specific record as passing, with no flicker in between.

To put the two tabs in context: the Details tab is meant to be the one you check quickly, a single score that tells you whether a mailbox's authentication is in good shape without needing to know what SPF, DKIM, and DMARC actually check for individually. The Technical tab is where you go when you need the specifics, whether a particular record is present, correctly formatted, and passing, which matters most when you're troubleshooting a delivery issue or verifying a change you just made at your registrar.

Those two views are only useful together if they agree with each other. A Details tab stuck at zero percent while the Technical tab underneath shows records actually passing works directly against the reason the Details tab exists: to give you a fast, accurate summary you don't have to double check against the technical breakdown every time. With this fix, checking the Details tab for a quick read and confirming specifics on the Technical tab when needed both point at the same underlying state, which is what makes either of them worth trusting on its own.

Why it matters

Email authentication status is something you check specifically because you need to trust it, usually right before you're about to rely on a domain for sending, or right after you've made a DNS change and want to confirm it worked. A summary score that's stuck showing zero percent when your domain is actually configured correctly undermines exactly the thing that tab exists to do: give you a fast, trustworthy read on your status without having to dig into the technical detail underneath.

The banner flash on the Technical tab is a smaller issue but points at the same problem: a status indicator that briefly shows the wrong thing, even for a moment, trains you not to trust the first thing you see, which means you end up double-checking a status that should have been reliable at a glance in the first place.

Fixing both means the Details tab and the Technical tab now agree with each other and with your domain's actual state, so you can check either one and act on what you see without second-guessing it.

This fix is also a good reminder to check both tabs after any change you make to your domain's DNS setup, not because either one is unreliable now, but because authentication status is exactly the kind of thing worth a quick second glance whenever you've touched a setting that affects deliverability. With this fix, that second glance takes seconds instead of requiring you to reconcile two tabs that used to disagree.

If you're setting up a new sending domain for the first time, expect to check both tabs a few times in the course of getting everything configured: the Details tab to confirm your overall progress, and the Technical tab to see which specific record, if any, is still outstanding. With this fix, both will consistently reflect the same underlying reality throughout that process.

Authentication status is not something you want to have to double-check against a second source before trusting it; that's the whole point of fixing both tabs at once rather than patching one and leaving the other inconsistent.

Both tabs are part of the same settings page, so switching between them to confirm a detail takes one click, and now that click gets you a consistent answer either way.

Availability

This fix is already live everywhere and applies automatically the next time you view a mailbox's email authentication settings.

All updates

Outreach that keeps going after you log off.Leads, emails, follow-ups and replies, handled.

Connect unlimited mailboxes and let AI agents find leads, write each email and follow up. Or send your own templates in manual mode. From $29/mo.

$1 for 3 days · Cancel anytime · No contract

Install with AI

Your coding agent sets up the FirstSales CLI and skills for you.

Prompt for Claude Code

I'm setting up FirstSales (https://firstsales.io), an AI outbound sales platform: campaigns, contacts, a reply inbox, deliverability and lead signals. Help me get my workspace sending real, good emails end to end, from Claude Code.

Read these first so you know how FirstSales works:
- Developer docs and API: https://developer.firstsales.io
- CLI: https://www.npmjs.com/package/@firstsales.io/cli
- Skills for coding agents: https://github.com/firstsalesio/firstsales-skills (read README.md and GUIDE.md)

Setup
1. Install the CLI: npm install -g @firstsales.io/cli
2. Install the FirstSales skills:
   claude plugin marketplace add firstsalesio/firstsales-skills
   claude plugin install firstsales@firstsales
3. Ask me if I already have a FirstSales account. If not, send me to https://app.firstsales.io to sign up.
4. Ask me to create an API key under Settings → API → API Keys, with only the scopes we need.
   Never ask me to paste the key into this chat. Tell me to run this in my own terminal, so the key stays hidden:
   read -rs FS_KEY && firstsales auth login --api-key "$FS_KEY"; unset FS_KEY
5. Run `firstsales whoami` and tell me which workspace and organisation we are connected to.

Then ask me about my business: what I sell, who I sell to (roles, company size, countries), my best customers, and what I use today for outbound (tools, lists, mailboxes). Walk me through:
1. Teaching FirstSales my business: website, offer, proof points and case studies in the knowledge base, so the AI writes like someone who knows the product.
2. Connecting my sending mailboxes and checking my sending domain: SPF, DKIM, DMARC and warm-up. If anything is unhealthy, tell me the exact DNS record to add.
3. Bringing in contacts: import my CSV or CRM export into a clean list, remove duplicates and bad emails, and block domains I must never email (customers, competitors, my own).
4. Building my first campaign: the right list, senders, steps and timing. Write the sequence with me, show me the drafts, and do not launch until I say yes.
5. Setting up Signals if it fits: find people engaging with LinkedIn posts about topics my buyers care about, and turn them into leads.
6. Inviting my team and giving each person the right access.

Once campaigns run, show me how to work the reply inbox from here: which replies need an answer, draft responses in my voice, and move good conversations into deals. If I use Cal.com, connect it so follow-ups can offer my booking link (not the first email).

Throughout, as you learn about my business, proactively suggest and help create:
- Reply templates for the questions and objections my prospects are likely to raise, based on my product, site and codebase if you can see them.
- Campaign ideas and segments worth testing, with the reason for each.

Safety rules:
- Show every change as a dry run (--dry-run) first and wait for my yes. Never send emails, launch campaigns or delete anything without my yes.
- Tell me before anything that spends credits, and how many.

Be opinionated. If the docs give a sensible default, just use it. Don't make me choose between five options.