---
title: "Beyond DMARC: Strengthening Email Security for Businesses | DMARC Report"
description: "Learn how businesses can go beyond DMARC with layered email security, advanced authentication, threat detection, and proactive defenses against cyberattacks."
image: "https://dmarcreport.com/og/blog/beyond-dmarc-strengthening-email-security-for-businesses.png"
canonical: "https://dmarcreport.com/blog/beyond-dmarc-strengthening-email-security-for-businesses/"
---

Quick Answer

Businesses can go beyond DMARC by implementing SPF, DKIM, multi-factor authentication, secure email gateways, phishing detection, employee training, and continuous threat monitoring to strengthen email security and protect against spoofing, phishing, and business email compromise.

Share 

[ ](https://www.linkedin.com/sharing/share-offsite/?url=undefined%2Fblog%2Fbeyond-dmarc-strengthening-email-security-for-businesses%2F "Share on LinkedIn") [ ](https://twitter.com/intent/tweet?text=Beyond%20DMARC%3A%20Strengthening%20Email%20Security%20for%20Businesses&url=undefined%2Fblog%2Fbeyond-dmarc-strengthening-email-security-for-businesses%2F "Share on X/Twitter") [ ](https://www.facebook.com/sharer/sharer.php?u=undefined%2Fblog%2Fbeyond-dmarc-strengthening-email-security-for-businesses%2F "Share on Facebook") [ ](https://reddit.com/submit?url=undefined%2Fblog%2Fbeyond-dmarc-strengthening-email-security-for-businesses%2F&title=Beyond%20DMARC%3A%20Strengthening%20Email%20Security%20for%20Businesses "Share on Reddit") [ ](mailto:?subject=Beyond%20DMARC%3A%20Strengthening%20Email%20Security%20for%20Businesses&body=Check out this article: undefined%2Fblog%2Fbeyond-dmarc-strengthening-email-security-for-businesses%2F "Share via Email") 

![Beyond DMARC](https://media.mailhop.org/dmarcreport/dmarc-compliance-5822-1795004913065.jpg) 

## Try Our Free DMARC Checker

Validate your DMARC policy, check alignment settings, and verify reporting configuration.

[ Check DMARC Record → ](/tools/dmarc-checker/) 

Most companies treat [email security](https://dmarcreport.com/blog/email-security-meets-cybersecurity-understanding-the-role-of-dmarc-reports/) as finished once SPF, DKIM, and DMARC are in place and the reports look clean. Those protocols matter, and every business that sends mail should have them. Still, the attacks that cost companies real money often come from a real account, a lookalike domain, or a phone call that follows up a perfectly authenticated email. This article explains what domain authentication actually protects and where it stops helping. It also covers the account, device, and process controls that close the gaps, so a passing DMARC check doesn’t give anyone a false sense of security.

You can set up SPF, DKIM, and DMARC perfectly and still have someone in accounts payable wire money to a scammer. That sounds backward after all the hours spent on [DNS records](https://www.cloudflare.com/learning/dns/dns-records/), but it happens all the time. **Authentication and security** overlap. They aren’t the same thing.

_Authentication lets a receiving server check whether a message that claims to come from your domain really does_. It can’t tell an employee whether the request inside that message is honest. It won’t stop a stolen password from being used, and it doesn’t help much once an attacker is sitting inside a real corporate mailbox.

So locking down the domain is a good first move. Most of the risk, though, sits before and after the **email lands in someone’s inbox**.

## Where Email Authentication Stops

![The DMARC Blind Spot](https://media.mailhop.org/dmarcreport/how-to-check-dmarc-record-7245-1795005005108.jpg)

The three protocols split the work. SPF lists the servers allowed to send mail for your domain. DKIM adds a [cryptographic signature](https://myequals.org/blog/cryptographic-signatures-explained/), so a recipient can confirm that the signed parts of the message weren’t altered in transit and that the signing domain stands behind it. DMARC ties both checks to the address people actually see in the From line, and it tells receiving servers what to do with mail that fails.

Set up properly, they cut down a **lot of direct spoofing**. They also give admins a useful view of who is sending mail in the company’s name without permission.

Attackers know this, so many of them just don’t bother spoofing a protected domain. They register a lookalike with one letter swapped. They take over a real employee account. Or they send through a mail service with a decent reputation. Mail sent from a hijacked account passes authentication without trouble, because it really did come from an authorized system.

[Remote access](https://www.fortinet.com/resources/cyberglossary/remote-access) has the same blind spot. Your email can be fully authenticated and still cause problems when staff log in from infected devices, or when someone has **phished their credentials**.

That’s why some companies add a [VPN for business](https://proton.me/business/vpn) to their remote-access setup. A business VPN encrypts traffic between a device and the VPN endpoint, and it gives you tighter control over who reaches internal systems. _It wonâ€™t stop phishing, and itâ€™s no substitute for authentication_. It does protect connections and limit access to company resources, which is a separate job.

Every control covers one piece of an **attack and leaves** other pieces to something else.

## DMARC Monitoring Should Be an Ongoing Process

Publishing a DMARC record takes maybe 20 minutes. Keeping track of every service that sends mail for your business takes a lot longer.

Picture a company running Microsoft 365 for staff email, a [marketing platform](https://joinbrands.com/blog/what-is-a-marketing-platform/) for newsletters, and **another tool for invoices**. Each one needs its own authentication setup. Then finance signs up for a new billing platform and doesn’t mention it to IT.

![Continuous DMARC Monitoring](https://media.mailhop.org/dmarcreport/spf-record-generator-3857-1795005199159.jpg)

If nobody configures that platform correctly, real invoices start failing authentication. Depending on your DMARC policy and how the receiving server handles failures, messages end up in quarantine or are bounced outright, and customers don’t get paid on time.

Admins have to tell a **broken configuration apart** from someone actually abusing the domain. Aggregate reports are where that happens. They show which sources are sending, how those messages were authenticated, and what receivers did with them. Look at them over a few weeks and unfamiliar senders start to stand out, along with legitimate services that were never set up properly.

This matters even more when you move to a different provider. Our guide, [How To Analyze DMARC Results With A New Email Provider](https://dmarcreport.com/blog/how-to-analyze-dmarc-results-with-a-new-email-provider/), explains how to set a baseline, check SPF and DKIM alignment, and work through failures while the switch is underway.

Don’t stop checking once the dashboard turns green. Vendors change their settings, new tools get added, and somebody in sales will connect an app without asking anyone. Regular reviews catch those changes before they open a **security hole or break delivery**.

## The Threat Doesn’t Always Come From a Fake Domain

[Business email compromise](https://foleyhoag.com/news-and-insights/blogs/security-privacy-and-the-law/2026/april/business-email-compromises-current-legal-trends-and-key-strategies/) shows clearly where domain authentication runs out.

Once an **attacker gets into a mailbox**, they can read old threads, work out who pays whom, and send messages that look completely routine.

![Out-of-Band Verification Process](https://media.mailhop.org/dmarcreport/dkim-lookup-3852-1795005239190.jpg)

Say a supplier emails your accounting team every month. Someone takes over the supplier’s account and sends a short note saying their bank details have changed. _The message comes from the usual address_. It passes SPF, DKIM, and DMARC. It might even sound like the person who normally writes. None of that proves the new account number is real.

This kind of fraud is part of a bigger trend. In its look at the [cyber threats to watch in 2026](https://www.weforum.org/stories/cybersecurity/2026-cyberthreats-to-watch-and-other-cybersecurity-news), the World Economic Forum points to cyber-enabled fraud and the growing role AI is playing in attacks. It lists phishing, scam phone calls, and **malicious text messages** among the most common forms of fraud hitting individuals.

For a business, the lesson is that attackers switch channels. An email sets up the request, and a phone call a day later makes it feel legitimate. Your procedures need to treat that as one scheme, not two unrelated messages.

## Protecting the Accounts Behind Business Communications

When an attacker controls a real mailbox, email authentication can’t do much for you. Keeping people out of accounts deserves as much attention as **protecting the domain**.

[Multifactor authentication](https://www.onelogin.com/learn/what-is-mfa/) is the obvious place to begin. A stolen password alone stops being enough to get in. Phishing-resistant options like FIDO2 security keys and passkeys hold up far better against credential-harvesting pages than one-time codes, which can be phished in real time.

Turning MFA on doesn’t finish the job, though. Check how people actually reach their email, which third-party apps have permission to connect to company accounts, and whether old accounts are still active. Someone who left in March shouldn’t still be able to read the shared inbox. An integration nobody has used in two years **shouldn’t keep its access** either. These are boring admin chores, and skipping them is exactly how attackers get in.

Watch for warning signs too. Sign-ins from odd locations, forwarding rules nobody remembers setting up, and unexpected app authorizations often mean an account has been taken over. The sooner someone spots them, the less damage gets done.

![Layered Email Defense](https://media.mailhop.org/dmarcreport/create-dmarc-record-7242-1795005081415.jpg)

## Remote Work Changes the Security Equation

Company email used to **live on office desktops** behind a managed network. Now people check it at home, in hotel lobbies, at airport gates, and on their own phones. Some use laptops IT manages. Others use devices IT can’t see into at all.

Public Wi-Fi gets a lot of attention, but HTTPS and encrypted mail connections already protect most of that traffic. The bigger risks are usually infected devices, malicious sites, [stolen logins](https://cxtoday.com/massive-credential-leak-exposes-149-million-stolen-logins-for-gmail-facebook-netflix-and-more), and people having access to systems they don’t need.

A VPN creates an encrypted tunnel and, when **configured for corporate access**, controls how staff accesses private systems. It can’t clean up a compromised laptop or stop someone from typing their password into a fake login page.

So device hygiene still counts. Keep operating systems supported and patched, run endpoint protection where appropriate, and set clear rules for accessing sensitive data.

Access should also match **what each person actually does**. A marketing coordinator rarely needs the finance system. A contractor on a three-month project might need one app, not the whole network. _The less each account can reach, the smaller the damage when one gets compromised_.

## Employees Need Procedures, Not Just Warnings

Most awareness training teaches people to spot suspicious emails. That helps, but some phishing is very hard to spot. Some of it is sloppy and full of typos. Some of it is well written, mentions a real vendor, and shows up the same week an invoice is due.

![Secure Verification Process](https://media.mailhop.org/dmarcreport/dmarc-record-6857-1795005564285.jpg)

Rather than expecting staff to catch every fake, build processes that make fraud hard to complete. A change to a **supplier’s bank details** could require a call to a number you already had on file, not the one in the email. Requests for [sensitive data](https://abcnews.com/Politics/pentagon-breach-exposed-sensitive-data-3-million-people/story?id=136832909) could need sign-off from a second person. Those checks still work when nobody notices anything strange.

Reporting matters just as much. People should be able to flag a weird message without feeling stupid for asking. If someone clicks a malicious link or enters their password somewhere they shouldn’t, a fast report gives the security team time to act.

Training works better when it matches people’s real jobs. Accounting needs examples of invoice fraud. Support staff needs to know what dodgy attachments and [fake customer data](https://cybernews.com/security/deutsche-telekom-passport-data-leak/) requests look like. Nobody needs to **become a security analyst**. Making the safe choice should simply be the easy one during a normal workday.

## Making Email Security Part of Everyday Operations

Layered security doesn’t have to mean buying a stack of new products. For many companies, the harder part is getting existing protections to work together.

The person who manages DNS often has nothing to do with [identity management](https://www.hpe.com/us/en/what-is/identity-management.html). Whoever sets up a new mail platform may not know what the DMARC policy is. And employees keep adding tools without **realizing they affect authentication**.

Most of these gaps stem from no one being clearly responsible. Assign an owner for [email authentication](https://dmarcreport.com/blog/setting-up-dmarc-for-stronger-email-authentication-and-trust/), one for account security, one for remote access, and one for incident response, and make sure each of them knows how their choices affect the others.

![Beyond DMARC Email Security Overview](https://media.mailhop.org/dmarcreport/dmarc-generator-7842-1795005320194.jpg)

In practice, that looks like this. A new email provider gets its authentication checked before it sends anything important. A departing **employee loses access** on their last day, not a month later. A reported phishing email goes through a set investigation process instead of sitting in someone’s inbox.

A regular review pulls it all together. A quarterly session, for example, could cover [DMARC](https://dmarcreport.com/) reports, access logs, third-party app permissions, and any recent incidents. Adjust how often you do it based on your risk level and how much your environment changes. _Looking at everything together gives a far clearer picture than running each control as its own separate project_.

## Stronger Protection Starts With Understanding the Gaps

DMARC is still one of the best defenses against [domain spoofing](https://www.infosecurity-magazine.com/news/infosec2025-email-domains-spoofing/). Configure it properly, monitor the results, and work your way up to an enforcement **policy that suits your setup**.

Just don’t treat a pass as proof that a message is safe. Real accounts get hijacked. Smart employees fall for convincing requests. A neglected laptop can leak data while your mail infrastructure runs exactly as it should.

The goal is to keep those weak spots from **becoming real incidents**. That takes domain authentication, account protection, sensible access controls, verification steps people actually follow, and ongoing monitoring.

The best-protected companies usually don’t have the longest list of security tools. They know what each control does, where it stops helping, and what happens next when something slips through.

![Brad Slavin](https://media.mailhop.org/dmarcreport/images/team/brad-slavin.jpg) 

[ Brad Slavin ](/authors/brad-slavin/) 

General Manager

General Manager of DuoCircle. Product strategy and commercial lead for DMARC Report's 2,000+ customer base.

[LinkedIn Profile →](https://www.linkedin.com/in/bradslavin) 

## Take control of your DMARC reports

Turn raw XML into actionable dashboards. Start free - no credit card required.

[Start Free Trial](https://app.dmarcreport.com/signup?plan=free) [Check Your DMARC Record](/tools/dmarc-checker/) 

 AutoSPF 

Automatic SPF Flattening

Streamline your SPF record management, enable DMARC compliance, and improve your email deliverability by fixing the SPF 10-lookup limitation.

[ Fix My SPF Record! → ](https://autospf.com/pricing/?utm%5Fsource=dmarcreport&utm%5Fmedium=blog-sidebar&utm%5Fcampaign=autospf-cross-promo&utm%5Fcontent=fix-my-spf) [ See How It Works ](https://autospf.com/how-it-works/?utm%5Fsource=dmarcreport&utm%5Fmedium=blog-sidebar&utm%5Fcampaign=autospf-cross-promo&utm%5Fcontent=how-it-works) 

Share this article

[ ](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fdmarcreport.com%2Fblog%2Fbeyond-dmarc-strengthening-email-security-for-businesses%2F) [ ](https://twitter.com/intent/tweet?text=Beyond%20DMARC%3A%20Strengthening%20Email%20Security%20for%20Businesses&url=https%3A%2F%2Fdmarcreport.com%2Fblog%2Fbeyond-dmarc-strengthening-email-security-for-businesses%2F) [ ](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fdmarcreport.com%2Fblog%2Fbeyond-dmarc-strengthening-email-security-for-businesses%2F) Copy 

Related Articles

- [ ![10 Reasons Why DKIM Fails](https://media.mailhop.org/dmarcreport/images/2022/04/dmarc-alignment-6379.jpg)  10 Reasons Why DKIM Fails Intermediate ](/blog/10-reasons-why-dkim-fails/)
- [ ![ActiveCampaign SPF DKIM DMARC Setup](https://media.mailhop.org/dmarcreport/dmarc-service-6087-1795078247977.jpg)  ActiveCampaign SPF, DKIM & DMARC Setup Guide Intermediate ](/blog/activecampaign-spf-dkim-dmarc-setup-guide/)
- [ ![AppRiver SPF Record](https://media.mailhop.org/dmarcreport/dmarc-check-7224-1785846270575.jpg)  AppRiver SPF Record: How To Set It Up (Owned By Zix) Intermediate ](/blog/appriver-spf-record-setup-guide-for-zix-email-security-platform/)
- [ ![Best DMARC Reporting Tools in 2026: Honest Comparison](https://media.mailhop.org/dmarcreport/images/2022/04/dmarc-report-4236.jpg)  Best DMARC Reporting Tools in 2026: Honest Comparison Intermediate ](/blog/best-dmarc-reporting-tools-2026/)

## Related Articles

[  Intermediate 4m  10 Reasons Why DKIM Fails  Apr 19, 2022 ](/blog/10-reasons-why-dkim-fails/)[  Intermediate  ActiveCampaign SPF, DKIM & DMARC Setup Guide  Nov 19, 2026 ](/blog/activecampaign-spf-dkim-dmarc-setup-guide/)[  Intermediate  AppRiver SPF Record: How To Set It Up (Owned By Zix)  Aug 4, 2026 ](/blog/appriver-spf-record-setup-guide-for-zix-email-security-platform/)[  Intermediate 8m  Best DMARC Reporting Tools in 2026: Honest Comparison  Mar 25, 2026 ](/blog/best-dmarc-reporting-tools-2026/)

```json
{"@context":"https://schema.org","@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com","logo":{"@type":"ImageObject","url":"https://dmarcreport.com/images/dmarcreport-logo.png"},"description":"DMARC reporting and email authentication management. Monitor aggregate and forensic DMARC reports, analyze authentication results, and enforce DMARC policies across all your domains.","parentOrganization":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138883901","name":"DuoCircle LLC","url":"https://www.duocircle.com","sameAs":["https://www.wikidata.org/wiki/Q138883901","https://www.crunchbase.com/organization/duocircle-llc","https://www.linkedin.com/company/duocircle","https://github.com/duocircle"],"subOrganization":[{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897912","name":"Phish Protection","url":"https://www.phishprotection.com"}]},"sameAs":["https://www.wikidata.org/wiki/Q138898167","https://www.linkedin.com/company/duocircle","https://x.com/duocirclellc","https://www.g2.com/products/dmarc-report/reviews","https://github.com/duocircle","https://www.crunchbase.com/organization/duocircle-llc","https://www.trustradius.com/products/duocircle/reviews"],"aggregateRating":{"@type":"AggregateRating","ratingValue":"4.8","reviewCount":"473","bestRating":"5","worstRating":"1","url":"https://www.g2.com/products/dmarc-report/reviews"},"contactPoint":{"@type":"ContactPoint","contactType":"customer support","url":"https://dmarcreport.com/support/"},"knowsAbout":["DMARC","DMARC Reporting","DMARC Aggregate Reports","DMARC Forensic Reports","Sender Policy Framework","DKIM","Email Authentication","Email Security","DNS Management","Email Deliverability"]}
```

```json
{"@context":"https://schema.org","@type":"WebSite","name":"DMARC Report","url":"https://dmarcreport.com","description":"DMARC reporting and email authentication management. Monitor aggregate and forensic DMARC reports, analyze authentication results, and enforce DMARC policies across all your domains.","publisher":{"@type":"Organization","name":"DMARC Report","url":"https://dmarcreport.com","logo":{"@type":"ImageObject","url":"https://dmarcreport.com/images/dmarcreport-logo.png"},"description":"DMARC reporting and email authentication management. Monitor aggregate and forensic DMARC reports, analyze authentication results, and enforce DMARC policies across all your domains.","parentOrganization":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138883901","name":"DuoCircle LLC","url":"https://www.duocircle.com","sameAs":["https://www.wikidata.org/wiki/Q138883901","https://www.crunchbase.com/organization/duocircle-llc","https://www.linkedin.com/company/duocircle","https://github.com/duocircle"],"subOrganization":[{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897912","name":"Phish Protection","url":"https://www.phishprotection.com"}]}}}
```

```json
[{"@context":"https://schema.org","@type":"BlogPosting","headline":"Beyond DMARC: Strengthening Email Security for Businesses","description":"Learn how businesses can go beyond DMARC with layered email security, advanced authentication, threat detection, and proactive defenses against cyberattacks.","url":"https://dmarcreport.com/blog/beyond-dmarc-strengthening-email-security-for-businesses/","datePublished":"2026-11-18T00:00:00.000Z","dateModified":"2026-11-18T00:00:00.000Z","dateCreated":"2026-11-18T00:00:00.000Z","author":{"@type":"Person","@id":"https://dmarcreport.com/authors/brad-slavin/#person","name":"Brad Slavin","url":"https://dmarcreport.com/authors/brad-slavin/","jobTitle":"General Manager","description":"Brad Slavin is the General Manager of DuoCircle, the company behind DMARC Report, AutoSPF, Phish Protection, and Mailhop. He founded DuoCircle in 2014 and has led the company's growth to 5,000+ customers across its email security product family. Brad's focus is product strategy, customer relationships, and the commercial and compliance side of email authentication (DPAs, SLAs, enterprise procurement).","image":"https://media.mailhop.org/dmarcreport/images/team/brad-slavin.jpg","knowsAbout":["Email Security Strategy","SaaS Product Management","Enterprise Compliance","Customer Success","Email Deliverability Business"],"worksFor":{"@type":"Organization","name":"DMARC Report","url":"https://dmarcreport.com"},"sameAs":["https://www.linkedin.com/in/bradslavin"]},"publisher":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com","logo":{"@type":"ImageObject","url":"https://dmarcreport.com/images/dmarcreport-logo.png"},"description":"DMARC reporting and email authentication management. Monitor aggregate and forensic DMARC reports, analyze authentication results, and enforce DMARC policies across all your domains.","parentOrganization":{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138883901","name":"DuoCircle LLC","url":"https://www.duocircle.com","sameAs":["https://www.wikidata.org/wiki/Q138883901","https://www.crunchbase.com/organization/duocircle-llc","https://www.linkedin.com/company/duocircle","https://github.com/duocircle"],"subOrganization":[{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138898167","name":"DMARC Report","url":"https://dmarcreport.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897474","name":"AutoSPF","url":"https://autospf.com"},{"@type":"Organization","@id":"https://www.wikidata.org/wiki/Q138897912","name":"Phish Protection","url":"https://www.phishprotection.com"}]},"sameAs":["https://www.wikidata.org/wiki/Q138898167","https://www.linkedin.com/company/duocircle","https://x.com/duocirclellc","https://www.g2.com/products/dmarc-report/reviews","https://github.com/duocircle","https://www.crunchbase.com/organization/duocircle-llc","https://www.trustradius.com/products/duocircle/reviews"],"aggregateRating":{"@type":"AggregateRating","ratingValue":"4.8","reviewCount":"473","bestRating":"5","worstRating":"1","url":"https://www.g2.com/products/dmarc-report/reviews"},"contactPoint":{"@type":"ContactPoint","contactType":"customer support","url":"https://dmarcreport.com/support/"},"knowsAbout":["DMARC","DMARC Reporting","DMARC Aggregate Reports","DMARC Forensic Reports","Sender Policy Framework","DKIM","Email Authentication","Email Security","DNS Management","Email Deliverability"]},"mainEntityOfPage":{"@type":"WebPage","@id":"https://dmarcreport.com/blog/beyond-dmarc-strengthening-email-security-for-businesses/"},"articleSection":"intermediate","keywords":"","image":{"@type":"ImageObject","url":"https://media.mailhop.org/dmarcreport/dmarc-compliance-5822-1795004913065.jpg","caption":"Beyond DMARC"},"speakable":{"@type":"SpeakableSpecification","cssSelector":[".answer-block","h1"]}}]
```

```json
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://dmarcreport.com/"},{"@type":"ListItem","position":2,"name":"Blog","item":"https://dmarcreport.com/blog/"},{"@type":"ListItem","position":3,"name":"Intermediate","item":"https://dmarcreport.com/intermediate/"},{"@type":"ListItem","position":4,"name":"Beyond DMARC: Strengthening Email Security for Businesses","item":"https://dmarcreport.com/blog/beyond-dmarc-strengthening-email-security-for-businesses/"}]}
```
