How to prevent BIMI and Apple Branded Mail logos from displaying on subdomains without affecting deliverability?
Published 5 Jul 2025
Updated 14 Oct 2026
12 min read
Summarize with

Updated on 14 Oct 2026: We clarified subdomain logo suppression for BIMI selectors and Apple Branded Mail while preserving email authentication.
To stop an inherited BIMI logo, publish a BIMI declination record for each affected visible From subdomain and selector. The record v=BIMI1; l=; a=; says that this DNS name declines to publish a BIMI indicator. It changes logo participation without changing SPF, DKIM, or DMARC. Inbox placement still depends on authentication, sender reputation, recipient behavior, and receiver policy.
Apple Branded Mail needs a different scope strategy. Apple Business, formerly Apple Business Connect, documents root-domain approval as covering that domain and its subdomains, and it does not document a negative child-subdomain exception. To keep selected subdomains unbranded, approve only the specific subdomains or email addresses that should show the logo instead of approving the root domain and all its descendants.
- BIMI: Publish a declination for the relevant selector under the subdomain in the visible From address.
- Apple: Use subdomain-only or address-only approval when root-wide branding is too broad.
- Deliverability: Keep SPF, DKIM, DMARC alignment, sending reputation, and complaint control intact.
The BIMI declination record
If the organizational domain has a default BIMI indicator and a subdomain should not display it, publish a complete declination record on that subdomain. The BIMI draft defines an explicit declination when both l= and a= are empty.
Safe BIMI suppression pattern
Use a valid BIMI declination only at the subdomain selectors that must suppress logo display. Replace any existing BIMI assertion at that exact DNS name instead of adding a second BIMI TXT record. Do not change SPF, DKIM, MX, return-path, or DMARC records to solve a logo-display problem.
BIMI declination recorddns
default._bimi.client.example.com. IN TXT "v=BIMI1; l=; a=;"
That record sits under the BIMI namespace for the subdomain. For mail with client.example.com in the visible From address and no custom selector, the BIMI lookup target is default._bimi.client.example.com. That is where the declination belongs.
The default record does not cover every selector. If a message uses an authenticated BIMI-Selector header with s=marketing, the lookup uses marketing._bimi.client.example.com. Publish the same declination for every selector used by that subdomain, or return those messages to the default selector. The BIMI Group's selector guidance explains how selectors and DKIM signing affect this lookup.
Root domain with logo and subdomain without logodns
default._bimi.example.com. IN TXT ( "v=BIMI1; " "l=https://brand.example/logo.svg; " "a=https://brand.example/vmc.pem" ) default._bimi.client.example.com. IN TXT "v=BIMI1; l=; a=;"
A BIMI declination is not a negative reputation signal by itself. It tells a BIMI-aware receiver to stop BIMI processing for that domain and selector, although the receiver always controls final display. Check the related DMARC checker output before and after the change because logo suppression can be confused with authentication changes during a DNS rollout.
Why logo suppression leaves authentication intact
A valid BIMI declination does not itself request message rejection or change authentication. BIMI does not guarantee inbox placement. A receiver can accept a message, authenticate it, and decide not to show a logo.
The practical risk is accidental collateral damage: changing the wrong TXT record, weakening the subdomain's DMARC policy, breaking DKIM signing, or creating an SPF lookup problem while editing DNS. Suped's DMARC monitoring product groups authentication results by sending source so teams can check for regressions after the logo change.
?
What's your domain score?
Deep-scan SPF, DKIM & DMARC records for email deliverability and security issues.
For a before-and-after DNS check, start with Suped's domain health checker. Check whether DMARC remains enforced and whether SPF and DKIM records are present. Also verify a delivered message's Authentication-Results header to confirm that the actual sending path passes authentication.
What filters care about
- Authentication: Configure SPF and DKIM. DMARC passes when at least one passes with domain alignment to the visible From address.
- Reputation: The sending IP, domain, complaint rate, and engagement history still matter.
- Policy: DMARC enforcement and subdomain policy must match the sending model.
What logo systems control
- BIMI display: The receiver decides whether to display the published brand indicator.
- Apple display: Apple Business manages Branded Mail registration; Apple Mail also supports BIMI.
- No-logo state: Suppressing a logo is separate from suppressing mail delivery.
How BIMI inheritance works
BIMI lookups use the visible From domain (RFC5322.From) after the message meets the receiver's authentication requirements. If a subdomain sends mail and has its own BIMI assertion, receivers evaluate that assertion for the subdomain. If no BIMI record is published there, the lookup falls back to the organizational domain for the same selector. A subdomain declination stops that fallback for the selected domain and selector.
That matters in B2B2C setups. The parent company can own example.com and run client mail through client.example.com. If the root-domain logo appears on client traffic, recipients see the wrong brand. Keep DMARC intact and publish an explicit BIMI decline at the client subdomain. For more detail on lookup behavior, see subdomain BIMI display.

BIMI lookup for a subdomain ending in a declination record and no brand logo.
Publish a declination for every visible From domain that needs suppression. A record on client.example.com does not automatically suppress mail from alerts.client.example.com: BIMI checks that exact From domain, then the organizational domain for the same selector, rather than checking every intermediate parent subdomain.
Do not solve this with weak DMARC
Weakening p=reject or sp=reject to p=none or sp=none to stop a logo removes DMARC enforcement. Handle logo display through BIMI or Apple branding settings while DMARC continues protecting the domain.
How Apple Branded Mail differs
Apple Branded Mail uses Apple Business. The brand owner verifies the business and sending scope, submits the brand and logo for approval, and controls display in the Mail app on supported Apple devices and in iCloud Mail on the web. BIMI uses DNS records; Apple Branded Mail uses brand approval and DNS verification.
A blank or fake Apple TXT record is not a suppression mechanism. Apple verification TXT values prove control of a domain, and Apple does not define an empty value as an opt-out. Apple also requires customer email to authenticate with DKIM; SPF-only authentication is unsupported. Keep DMARC and aligned DKIM working while changing the Branded Mail scope.

Illustration of Apple Business Connect Branded Mail settings for domain and subdomain logo display.
Apple's Branded Mail instructions explain domain, subdomain, and address-level setup. The separate comparison of BIMI and Apple covers the operational differences between the two systems.
BIMI
- Control plane: DNS records under the BIMI namespace.
- Opt-out method: A valid declination record with empty logo and evidence tags.
- Risk area: Wrong DNS name, broken assertion syntax, or weak DMARC enforcement.
Apple Branded Mail
- Control plane: Apple Business domain and brand settings.
- No-logo method: Approve only the subdomains or addresses that should show the logo.
- Risk area: Root-domain approval includes subdomains and can make the scope too broad.
How to restrict Apple Branded Mail to specific senders
Apple Branded Mail supports approval at the domain, subdomain, or individual-address level. Adding example.com allows that domain and any subdomain to use Branded Mail. Adding members.example.com limits the scope to that subdomain, while adding billing@example.com limits it to one address. Apple's domain structure instructions do not describe a child-subdomain exclusion that overrides an approved root domain.
- Inventory the senders: List each root address and subdomain that should display the Apple logo.
- Replace a broad scope: Remove the root-domain entry from Branded Mail, then add only the intended subdomains or specific root-domain addresses. Allow for a temporary branding gap while the narrower entries are reviewed.
- Complete verification: Publish each TXT value within Apple's verification window of 14 calendar days and allow up to seven working days for brand review.
- Plan for the limit: A brand can contain no more than 100 combined domains, subdomains, and email addresses.
Remove the Branded Mail entry in Apple Business
In Apple Business, open Brands > Branded Mail, select More next to the relevant domain or address, then select Remove and confirm. Apple's Branded Mail instructions state that removal stops Branded Mail branding on future email for that scope. Re-adding the entry requires a new TXT verification value.
A practical B2B2C rollout pattern
In a B2B2C model, separate authentication control from brand-display control. The platform owner should keep the domain family authenticated and monitored. Document each client-facing subdomain's BIMI record and its separate Apple Branded Mail approval scope.
|
|
|
|
|---|---|---|---|
BIMI | Logo | Decline | Publish subdomain declination |
DMARC | Enforced | Enforced | Monitor |
Apple | Specific addresses | Not added | Approve intended senders only |
Reports | Central | Segmented | Track |
A compact control map for a root domain and client subdomains.
Suped is a DMARC reporting and email authentication platform. Use Suped's DMARC monitoring to compare authentication results across the root domain and client subdomains and investigate failures after a branding change. Confirm inbox placement and logo display with real test messages.
DMARC record detail view showing SPF, DKIM, DMARC, rDNS diagnostics, and DNS records
If DNS access is distributed across several teams, Suped's Hosted DMARC workflow lets teams stage DMARC policy changes centrally. Keep existing policies stable during logo suppression, and monitor authentication results before making any separate enforcement change.
What to document per subdomain
- Owner: Which client, business unit, or platform team controls the subdomain.
- Authentication: Which systems send mail and which DKIM domains sign that mail.
- BIMI state: Logo record, declination record, or no published BIMI assertion.
- Apple state: Root-wide, subdomain-only, address-only, pending review, or not configured.
Operational checks before and after suppression
Treat this as a small DNS and Branded Mail scope change with a clear rollback plan. Take a snapshot first, publish the subdomain declination and adjust the Apple scope where applicable, wait through DNS TTL and provider review, then send fresh test mail through the affected subdomain.
- Record name: Confirm the BIMI TXT record uses the exact visible From subdomain and every selector used by its messages.
- DMARC policy: Confirm the organizational domain and branding-enabled subdomains retain DMARC enforcement at quarantine or reject.
- DKIM signing: Send a message and confirm DKIM passes with domain alignment, as Apple Branded Mail does not support SPF-only authentication.
- SPF path: Confirm the return-path domain and SPF record were not changed during the DNS edit.
- Apple scope: Confirm no approved parent-domain entry still includes the subdomain that should remain unbranded.
- Logo result: Compare fresh subdomain and parent-domain messages after DNS caches refresh. Older messages are not a reliable test of future branding.
DNS names to verifytext
default._bimi.example.com default._bimi.client.example.com _dmarc.example.com _dmarc.client.example.com
Inspect the receiver-added Authentication-Results header for dmarc=pass and, where reported, bimi=declined. A provider that omits the BIMI result needs a separate DNS and display check.
The success condition is simple: the subdomain's mail still authenticates, DMARC still passes, the parent logo no longer appears where it should not, and Apple Branded Mail includes only the intended senders.
Risk checks after changing logo controls
Use these bands to decide whether the rollout is healthy or needs rollback.
Healthy
Pass
Authentication still passes and the unwanted logo is gone.
Review
Watch
Logo state is right, but one reporting source shows alignment failures.
Rollback
Fix
Mail authentication changed, or Apple domain approval no longer matches the plan.
If a logo still appears in Apple Mail
Apple Mail supports BIMI independently of Apple Branded Mail. Apple's BIMI support requirements describe verification by a participating mailbox provider, including a trusted BIMI Evidence Document and receiver-added headers. Removing a Branded Mail entry does not remove the sender's BIMI assertion, and a BIMI declination does not remove Apple branding approval.
- If Apple branding remains after a BIMI declination, check whether the sender is still covered by a root-domain, subdomain, or address-level Branded Mail approval.
- If a logo remains after removing Apple approval, check the BIMI record for the exact visible From domain and active selector, then retest with a fresh message after caches refresh.
Mail Privacy Protection (MPP) is a recipient privacy setting. Apple's Mail Privacy Protection instructions describe enabling Protect Mail Activity on the recipient's device. MPP is not a sender TXT record or a mechanism for authorizing BIMI selectors.
Views from the trenches
Best practices
Publish BIMI declinations for each visible From subdomain and selector that must stay unbranded.
Keep DMARC policy and alignment unchanged while adjusting BIMI or Apple logo controls.
Avoid root-wide Apple approval when a client subdomain must remain unbranded in Mail.
Common pitfalls
Teams edit the root BIMI record and remove the logo for every legitimate sender.
Teams weaken subdomain DMARC policy to stop a logo, creating a clear security gap.
Teams assume Apple TXT verification has the same semantics as a BIMI declination.
Expert tips
Document each subdomain's sender, brand owner, BIMI state, and Apple approval state.
Use short TTLs during rollout, then restore normal TTLs once logo behavior is confirmed.
Test with real mail after DNS propagation because inbox logo caches can delay feedback.
Marketer view
Marketer from Email Geeks says an empty BIMI logo value is a valid declination to publish, so BIMI processing should stop for that subdomain.
2025-05-14 - Email Geeks
Marketer view
Marketer from Email Geeks says a blank BIMI declination should not affect deliverability because it only controls logo participation.
2025-05-14 - Email Geeks
Frequently asked questions
No. A valid BIMI declination changes logo participation without changing mail authentication. Inbox placement still depends on sender reputation and receiver filtering, so verify authentication on delivered messages after the change.
No. Add it for each visible From subdomain and selector that must avoid the parent logo. A declination on one subdomain does not automatically cover deeper From subdomains. Subdomains that need their own logo should publish their own valid BIMI assertion.
No. Apple Branded Mail is managed through Apple Business. A BIMI declination does not change Apple branding approval, and an empty Apple verification record has no documented opt-out meaning.
Apple's current instructions do not document a negative child-subdomain exception. Replace root-wide approval with subdomain-only or address-only entries that cover only the senders that should display the logo.
DMARC subdomain policy controls authentication enforcement, not logo choice. BIMI requires the right assertion or declination at the relevant visible From domain and selector.
Configure SPF and DKIM for the subdomain and ensure DMARC passes through at least one passing mechanism with domain alignment. Apple Branded Mail also requires DKIM authentication. Publish the client's BIMI assertion or a declination, and approve Apple branding only for the intended sender.

