Blog
The Email Settings Carriers Check Even When the Form Doesn't Ask
Most owners meet the email questions on a cyber-insurance application as two simple boxes. Do you require MFA for email? Do you filter incoming email for threats?
Those are asked often. In our review of 13 public carrier applications (November 2026), 10 asked about MFA on email, and 8 asked about email filtering, a secure email gateway, or "sandboxing," which means opening suspicious attachments and links in a safe, walled-off place before they reach anyone's inbox.
There's a third email question that only 5 of the 13 forms asked outright, and it's the one I'd pay the most attention to: whether your domain publishes the email-authentication records called SPF, DKIM and DMARC. Fewer forms ask it, but anyone, including carriers and the security-rating firms they work with, can check it from the outside without asking you at all.
Why email gets so much attention
Email is where money moves and passwords get reset. It's where a fake invoice lands, where a criminal impersonates the CEO, and where a stolen login quietly lets someone read months of conversations. When an underwriter looks at a company of 50 to 250 people, email is one of the most likely ways a claim starts.
The three email controls on the forms each block a different version of that.
Control one: MFA on email
MFA (multi-factor authentication) means a password alone can't open a mailbox. You also need a code, a phone prompt or a security key.
The form is asking whether anyone can open company email with only a password, from anywhere: webmail on a home computer, the mail app on a personal phone, an old desktop mail program. Older mail apps are the quiet gap. Some connect using older sign-in methods that can't ask for a second factor at all. Microsoft and Google have been retiring those older methods for years, but it's worth asking your IT provider to confirm they're blocked in your account.
Control two: filtering what comes in
Microsoft 365 and Google Workspace both filter spam and malware out of the box. Many companies add a dedicated email security product on top, which can rewrite links so they're checked when clicked, open attachments in a sandbox first, and flag messages that come from outside the company or from lookalike domains.
When the form asks about filtering, it wants a product name, not "Outlook catches spam." If you rely only on the built-in protection, that may be fine. Just know which settings are on, and say so plainly.
Control three: proving your email is really from you
This is the one most owners haven't heard of, so here it is in plain words.
When someone sends email, the "From" line is just text. Anyone can type your company name and domain into it, the same way anyone can write your return address on an envelope. Three public records, published in your domain's DNS (the internet's phone book), let receiving mail systems check whether a message claiming to be from you really is:
- SPF is a list of the servers allowed to send email for your domain.
- DKIM is a digital signature added to each outgoing message, which the receiver checks against a public key you publish.
- DMARC tells receivers what to do when a message fails those checks: let it through, send it to spam, or reject it. It also asks them to send you reports.
DMARC is what turns the other two into protection. Without it, a receiver may notice a forged message and deliver it anyway.
These records protect your customers and vendors from fake emails that look like they came from you. They also help your real email arrive. Google's email sender guidelines, for example, require bulk senders to publish SPF, DKIM and DMARC.
Why the outside view matters
Because these records are public, anyone can see in seconds whether your domain is protected. Security-rating services see it, carriers see it, and so do criminals looking for a domain that's easy to impersonate. You can't answer this question vaguely, because the answer is already public.
When I ran IT at a company of about 200 people, DMARC sat on the to-do list for far too long. It wasn't hard; it just never felt urgent next to the projects people could see. Getting it to full enforcement mostly took patience: finding every service that sends email for you, such as the newsletter tool, the invoicing system and the HR platform, and making sure each one was set up properly before telling the world to reject everything else.
The "monitor only" trap
DMARC has three settings, called policies: none (just report), quarantine (send failures to spam) and reject (block failures). A lot of companies publish DMARC at "none," which is the right first step, and then stop there for years. At "none," nothing is blocked. You're watching forgeries go by.
The goal is to move to quarantine and then reject once the reports show that all your legitimate senders pass. That's a project measured in weeks, not a weekend, but it's a short one.
Don't forget the old domains
Most companies own more domains than they use: an old company name, a misspelling bought defensively, a product site. A domain that doesn't send email at all should say so with a strict SPF and DMARC record. Otherwise, criminals can use it to send convincing fakes with a name your customers recognize.
What to do Monday morning
- Confirm with your IT person or provider that MFA is required for webmail and for email on phones, and that older mail sign-in methods are blocked.
- Write down what filters your incoming email, with the product name, and whether links and attachments get checked.
- Ask for a list of every domain you own, including old ones, and whether SPF, DKIM and DMARC are published for each.
- If DMARC is missing or stuck at "none," put a date on moving it to quarantine and then reject, and ask who's reading the reports in the meantime.
- Make a list of every service that sends email as you (marketing, invoicing, HR, the website contact form). That list is the key to reaching enforcement safely.