Skip to main content
  1. Knowledge base
  2. Email security

BIMI Subdomain DMARC Inheritance: Why Subdomain Mail Shows No Logo

BIMI subdomain DMARC inheritance means a subdomain with no DMARC record of its own follows the organizational domain's sp= tag, not its p= tag. If sp=none sits beside p=reject, subdomain mail is unenforced, so mailbox providers withhold the BIMI logo and attackers can spoof it.

BIMI (Brand Indicators for Message Identification) is an email standard that lets a mailbox provider display a brand's logo next to authenticated messages. Its real prerequisites are DMARC enforcement and a verifiable organizational identity, not just a published logo record.

What causes missing logos on subdomain mail?

A receiver evaluating mail from news.example.com queries _dmarc.news.example.com. If nothing is published there, it falls back to _dmarc.example.com, the organizational domain. RFC 7489 specifies DMARC and defines this fallback. When the fallback record is used for a subdomain, the policy that applies is sp= if present, and p= only if sp= is absent.

That produces this common, dangerous record:

_dmarc.example.com. IN TXT "v=DMARC1; p=reject; sp=none; rua=mailto:[email protected]"

The apex looks enforced and the BIMI record is in place. But every subdomain without its own DMARC record is effectively at p=none. Providers that apply BIMI's enforcement requirement evaluate the policy for the sending domain, find monitoring only, and skip the logo. Exact behavior varies by provider, but a weak effective policy is a common reason for no logo.

Other variants cause the same symptom:

  • A subdomain publishes its own _dmarc record with p=none, overriding a strong parent.
  • The parent uses p=quarantine; pct=25, and BIMI requires full coverage.
  • The default._bimi record exists only on the apex, and the receiver does not fall back to it for that subdomain.

How does an attacker exploit weak subdomain DMARC?

Spoofing needs no compromised account. The attacker sends mail with a From address such as [email protected], a subdomain you never use. DMARC evaluation finds no subdomain record, applies sp=none, and the message is delivered despite failing alignment. Your p=reject never applies.

The result is a phishing message from a hostname containing your brand. It will not carry your logo, but recipients often judge by the domain text. If an organization later extends BIMI coverage to subdomains without fixing sp=, the gap also becomes a path to a trusted-looking brand indicator. For a related bypass, see displaying a fake brand logo without a VMC.

Auditors flag this because it contradicts a stated control. The organization claims DMARC enforcement, yet a third of its namespace, or more, is unprotected. Dangling DNS and forgotten marketing subdomains make this worse.

The cost is concrete: brand-impersonation incidents, support load, failed BIMI rollouts after logo and certificate spend, and findings in compliance questionnaires that ask about enforcement across all domains.

How do I fix BIMI subdomain DMARC inheritance?

Work from monitoring to enforcement, not straight to sp=reject.

  1. Inventory subdomains that send mail. Use DMARC aggregate reports (rua) to see which subdomains appear as sources, including ones you forgot.
  2. Align legitimate senders. Make sure each subdomain's SPF and DKIM align with its From domain. The mechanics are covered in DMARC alignment bypass.
  3. Raise sp= in steps. Move from none to quarantine, watch reports, then reject.
  4. Add explicit records for special cases. A subdomain that needs a different policy can publish its own _dmarc record.
  5. Publish non-sending subdomain protection. Parked or unused subdomains benefit from a strict policy inherited from the parent.

The target state:

_dmarc.example.com. IN TXT "v=DMARC1; p=reject; sp=reject; pct=100; rua=mailto:[email protected]"

If a subdomain must stay in monitoring while you migrate it, isolate it explicitly:

_dmarc.legacy.example.com. IN TXT "v=DMARC1; p=quarantine; rua=mailto:[email protected]"

Keep that exception temporary and tracked. Then confirm the BIMI record resolves where you expect:

default._bimi.example.com. IN TXT "v=BIMI1; l=https://example.com/logo.svg; a=https://example.com/vmc.pem"

For the apex-level version of this problem, see why BIMI DMARC policy is not enforced. If the logo is still rejected after policy is fixed, check the file format next: BIMI SVG Tiny PS errors.

How do I verify the effective policy with dig?

Query both the subdomain and the organizational domain, and read the tags yourself:

dig +short TXT _dmarc.news.example.com
dig +short TXT _dmarc.example.com
dig +short TXT default._bimi.example.com

An empty answer for the first command means the subdomain inherits. Then read the second answer for sp=. If sp= is missing, p= applies. If sp= is weaker than p=, the subdomain is effectively weaker than the apex.

How would monitoring catch it?

Point-in-time checks go stale, so automate three things:

  • Effective policy per hostname. Compute the policy each known subdomain actually receives, including the sp= fallback, and alert when it is weaker than the apex p=.
  • Report review. Aggregate reports showing unaligned, undisposed mail from subdomains are direct evidence of the gap.
  • Change detection. Alert when sp=, pct=, or any _dmarc record changes, since a well-meaning edit often introduces the weakness.

Common questions

Does a strong p=reject protect my subdomains automatically?

No, not if sp= is set to something weaker. The sp= tag overrides p= for subdomains without their own DMARC record. If sp= is absent, subdomains inherit p=. Always check the published record for an explicit sp= value, not just the headline policy.

Can I enable BIMI for only one subdomain?

Generally yes, but the sending subdomain still needs enforced DMARC and a resolvable BIMI record. You can publish a _dmarc record and a default._bimi record at that subdomain. Provider handling of fallback to the apex BIMI record varies, so test with the receivers you care about.

Is sp=none ever the right choice?

Only temporarily, during a migration when you are still discovering legitimate subdomain senders. It leaves every inheriting subdomain spoofable, so set a deadline to move it to quarantine and then reject. Leaving it indefinitely defeats the apex enforcement you advertise.

Key takeaways

  • Subdomains without their own DMARC record follow sp= if present, otherwise p=.
  • p=reject; sp=none leaves subdomains spoofable and typically disqualifies their mail from BIMI logo display.
  • Fix by inventorying senders, aligning SPF and DKIM, then stepping sp= up to reject.
  • Verify with dig on both the subdomain and the apex, and monitor for policy drift.
  • SetEnforce's email scan checks the DMARC policy and sp= tag, the BIMI record, and whether subdomain enforcement matches the organizational domain.

Check whether your own domain gets this right. Scanning is free and needs no account.

Scan your domain

All articles