Does a root domain BIMI record apply to subdomains without their own record?

Updated on 17 Oct 2026: We clarified subdomain BIMI fallback and certificate coverage, with corrected DMARC enforcement checks.
Yes. If a subdomain sends mail and has no BIMI record for the chosen selector, the record at its Organizational Domain can apply. In practical terms, mail with a visible From domain such as news.example.com can use the BIMI record at default._bimi.example.com when the lookup at default._bimi.news.example.com does not produce a local BIMI assertion.
BIMI display requires strong DMARC on both the Organizational Domain and the visible From domain. A root BIMI record does not make the subdomain eligible when the Organizational Domain uses p=none, the subdomain publishes its own p=none, or either checked DMARC record contains sp=none.
- Short answer: Organizational Domain BIMI can cover subdomains that do not publish a local record for the chosen selector.
- DMARC condition: Both the Organizational Domain and visible From domain must have an enforcing DMARC policy of quarantine or reject.
- Override rule: A valid subdomain BIMI assertion takes priority for that subdomain and selector.
When root BIMI applies to subdomains
Treat this as a two-part lookup. The receiver starts with the Author Domain in the visible From address and checks the BIMI record for the chosen selector. If no BIMI candidate remains after the initial lookup, it queries that same selector at the Organizational Domain. Here, 'root domain' means the Organizational Domain, typically example.com or example.co.uk, rather than every intermediate parent of a deeper subdomain.
That means one Organizational Domain BIMI record can cover ordinary subdomains, provided no local BIMI assertion stops fallback and both DMARC checks qualify. This is the same practical answer behind parent domain BIMI checks. The BIMI Group FAQ confirms Organizational Domain inheritance and subdomain overrides.

Subdomain BIMI lookup with Organizational Domain fallback and DMARC enforcement checks.
DMARC still applies to inherited BIMI
BIMI processing stops if either checked domain has p=none, or either checked DMARC record contains sp=none. A local p=reject does not bypass the sp=none check, even when the Organizational Domain has a valid SVG and certificate.
How BIMI inheritance works
BIMI records are TXT records under a selector. Most senders use the default selector, so the Organizational Domain record is normally published at default._bimi.example.com. A subdomain-specific BIMI record uses the same pattern below the subdomain, such as default._bimi.news.example.com.
If the subdomain has one usable BIMI assertion for the selector, that local record controls the result. If no candidate remains after BIMI version filtering, the receiver queries the same selector at the Organizational Domain. A malformed current-version assertion, multiple BIMI1 records, or a DNS lookup failure is not a reliable opt-out or fallback mechanism. Inspect the exact response and use a valid empty assertion for an intentional opt-out.
|
|
|
|---|---|---|
Absent | Valid | Organizational logo can apply |
Valid | Valid | Subdomain record wins |
Explicit decline | Valid | No logo for that selector |
Malformed BIMI1 record or multiple BIMI1 records | Valid | No dependable fallback; fix the local record |
Absent | Absent | No BIMI assertion found |
BIMI lookup outcomes for a subdomain using the default selector.
Selectors matter too. If a message has a BIMI-Selector header naming a custom selector, the receiver looks for that selector at the Author Domain and then the Organizational Domain. It does not substitute the Organizational Domain's default selector when the named selector is absent.
Where the certificate fits
The logo file and any Verified Mark Certificate (VMC) or Common Mark Certificate (CMC) still need to satisfy the mailbox provider's BIMI rules. Certificate coverage, SVG Tiny PS formatting, HTTPS hosting, and provider-specific display rules all come after DNS discovery. Referenced files must be publicly retrievable over HTTPS without authentication.
How to stop inheritance for one subdomain
Leaving the subdomain without a BIMI record does not opt it out. Absence is what triggers the Organizational Domain lookup. To decline BIMI for one subdomain and selector, publish a syntactically valid assertion with both the logo and authority evidence locations empty.
Subdomain BIMI declinationdns
Host: default._bimi.private.example.com Type: TXT Value: v=BIMI1; l=; a=;
This valid empty assertion means the domain owner declines to publish a logo for that selector. It stops the Organizational Domain logo from appearing on mail sent with the visible From domain private.example.com. This applies to that exact From domain and selector; it does not automatically opt out deeper subdomains or other selectors. Document why it exists so it is not mistaken for an incomplete record.
Root and subdomain BIMI record examples
This Organizational Domain BIMI record can cover a subdomain with no local assertion, assuming DMARC qualifies at both required domains. Keep the BIMI record simple, because display failures often come from inaccessible logo hosting or a certificate that does not cover the selected BIMI assertion rather than TXT syntax.
Root domain BIMI recorddns
Host: default._bimi.example.com Type: TXT Value: v=BIMI1; l=https://assets.example.com/logo.svg; a=https://assets.example.com/vmc.pem
If the marketing team wants a different logo for news.example.com, publish a BIMI record at the subdomain. That record then controls that subdomain and selector.
Subdomain-specific BIMI recorddns
Host: default._bimi.news.example.com Type: TXT Value: v=BIMI1; l=https://assets.example.com/news.svg; a=https://assets.example.com/news-vmc.pem
Use organizational domain BIMI
- Best fit: All subdomains should show the same brand logo.
- DNS load: One BIMI record has less operational work.
- Risk: One mistake affects every relying subdomain.
Use subdomain BIMI
- Best fit: A subdomain needs a different logo or certificate.
- DNS load: Each subdomain has its own record to maintain.
- Risk: A local record error can prevent logo display.
Can subdomains share a BIMI certificate?
A separate certificate is not automatically required for every sending subdomain. First identify which BIMI assertion the receiver uses. The VMC validation draft checks the certificate's Subject Alternative Name (SAN) against the selected assertion's domain or its full selector name.
For example, when news.example.com falls back to default._bimi.example.com, a VMC covering example.com can satisfy that domain check. Publishing a local record at default._bimi.news.example.com changes the assertion being checked.
- If a local BIMI record uses the same logo, confirm that the certificate covers that local assertion before reusing its a= URL.
- If the subdomain uses a different logo, obtain a certificate for that logo where the mailbox provider requires certified BIMI.
DMARC requirements for subdomain BIMI
BIMI requires strong DMARC on both the Organizational Domain and the RFC5322.From domain. For mail from a subdomain, checking only whether one inherited policy is enforcing misses half of the requirement. The Organizational Domain must use p=quarantine or p=reject, and the subdomain must be covered by a strong subdomain policy.
An enforcing policy does not authenticate a message. Confirm dmarc=pass in the receiving mailbox's Authentication-Results header. At least one successful SPF or DKIM result must satisfy DMARC alignment with the visible From domain. A pass for an unrelated domain is insufficient.
The Organizational Domain DMARC record can include sp= for subdomains. If sp=quarantine or sp=reject applies, the subdomain has strong policy coverage. If sp=none appears in either checked record, BIMI processing stops even when a local record enforces DMARC. When sp is absent, the p value supplies the subdomain policy.
Organizational Domain DMARC policy for subdomain BIMIdns
Host: _dmarc.example.com Type: TXT Value: v=DMARC1; p=quarantine; sp=quarantine; rua=mailto:dmarc@example.com
A subdomain can publish its own DMARC record. That record takes priority for policy applied to the subdomain, but it does not remove BIMI's separate Organizational Domain policy checks or its prohibition on sp=none in either checked record. This is why subdomain DMARC overrides matter for BIMI. These additional restrictions are defined in the BIMI draft.
Subdomain DMARC record that blocks BIMI displaydns
Host: _dmarc.news.example.com Type: TXT Value: v=DMARC1; p=none; rua=mailto:dmarc@example.com
DMARC policy strength for BIMI
Both checked domains need enforcement. The message must also authenticate, and neither checked record can contain sp=none.
None
p=none
Monitoring only, not enough for BIMI display.
Quarantine
p=quarantine
Strong policy accepted by BIMI programs.
Reject
p=reject
Strong policy accepted by BIMI programs.
Legacy BIMI guidance rejects pct values below 100 for quarantine policies. RFC 9989 made pct historic and introduced t for testing. BIMI specifications and provider checks still reference the older percentage rules. Leave pct absent, or use pct=100 for compatibility; keep t absent or t=n. Under RFC 9989, p=quarantine; t=y requests a policy of none for failures and is unsuitable for BIMI.
RFC 9989 obsoletes RFC 7489 and RFC 9091 and replaces Public Suffix List-based Organizational Domain discovery with a bounded DNS Tree Walk. The current BIMI draft still defines fallback using RFC 7489 Organizational Domain discovery. Do not assume that a receiver's DMARC upgrade changes its BIMI lookup. A local DMARC record makes the subdomain's policy explicit; it does not guarantee the same Organizational Domain or BIMI fallback at every receiver.
How to verify BIMI fallback for a subdomain
Start with the exact visible From domain, not the domain used in internal documentation. A sending platform can use mail.example.com, news.example.com, or example.com as the user-facing domain. BIMI discovery starts with the domain recipients see.
- Confirm the From domain: Send a real message and inspect the visible From address, BIMI-Selector header if present, and the receiving system's dmarc=pass result.
- Check subdomain BIMI: Query the chosen selector under the exact From domain first.
- Check Organizational Domain BIMI: Verify the matching selector, logo URL, and certificate URL at the fallback domain.
- Check both DMARC policies: Confirm enforcement at both required domains, no sp=none in either checked record, and no policy testing that reduces enforcement.
- Check provider display: After DNS caches expire, send fresh messages and check the provider's certificate, reputation, and display requirements. A valid record does not guarantee a logo.
For a focused DNS check, the DMARC checker confirms whether the policy syntax is valid. For a broader authentication review, run a domain health check before changing BIMI.
?
What's your domain score?
Deep-scan SPF, DKIM & DMARC records for email deliverability and security issues.
Suped's DMARC reporting platform helps with this operational check. Its DMARC monitoring view shows which sources pass authentication, where subdomain policy gaps exist, and which issues need action. That evidence helps separate BIMI DNS problems from underlying authentication failures.
DMARC record detail view showing SPF, DKIM, DMARC, rDNS diagnostics, and DNS records
For teams with many domains, Suped's Hosted DMARC can stage policy changes and keep subdomain enforcement easier to manage. It is useful when different business units own DNS and the BIMI rollout depends on consistent policy at every active From domain.
BIMI fallback on deeper subdomains
The easiest setup uses one Organizational Domain BIMI record. It pairs strong DMARC at both required levels with no local BIMI assertions unless they are intentional. Complexity rises when each subdomain has its own DMARC policy or BIMI selector, especially when separate teams manage DNS.
If you use several subdomain layers, such as promo.eu.example.com, test the exact From domain directly. BIMI does not try every intermediate parent. It queries the Author Domain and, when fallback applies, the Organizational Domain. A record only at eu.example.com is not used unless that is the Organizational Domain. This distinction matters when checking BIMI subdomain levels.
Best operating model
- Default path: Publish one valid Organizational Domain BIMI record unless a subdomain needs a local assertion.
- Policy path: Use strong DMARC at the Organizational Domain and every visible From domain.
- Exception path: Publish subdomain BIMI when it needs a different logo or an explicit opt-out.
Views from the trenches
Best practices
Check the exact From domain first, then test BIMI and DMARC at that same subdomain.
Keep root BIMI as the default path unless a subdomain needs a separate logo for its mail.
Confirm strong DMARC at the Organizational Domain and every active visible From domain.
Common pitfalls
Assuming a root logo works while a subdomain DMARC record still uses p=none for its mail.
Leaving a broken subdomain BIMI record in DNS and expecting root fallback to fix it.
Testing only the root domain when the sender actually uses a deeper subdomain in production.
Expert tips
Document which subdomains intentionally override BIMI so future DNS changes stay clear.
Treat DMARC policy and BIMI lookup as separate checks before blaming mailbox display.
When fallback differs by receiver, record the exact BIMI assertion domain selected in each test.
Marketer view
Marketer from Email Geeks says a root BIMI record applies when the subdomain has no BIMI record of its own.
2025-09-24 - Email Geeks
Marketer view
Marketer from Email Geeks says the answer changes if a subdomain DMARC record removes enforcement.
2025-09-24 - Email Geeks
Frequently asked questions
A BIMI record at the Organizational Domain can apply when the subdomain has no local assertion for the chosen selector. DMARC enforcement and message authentication must also qualify; inheritance alone does not guarantee logo display.
Yes. A valid subdomain BIMI assertion controls that subdomain and selector. Fix local record errors instead of depending on fallback.
It supplies enforcement for the subdomain when no local DMARC record overrides it, but the Organizational Domain must also use p=quarantine or p=reject. Neither checked DMARC record can contain sp=none, and the message must authenticate.
No. A local p=none record prevents the strong DMARC posture BIMI requires for that visible From domain.
Publish a valid local BIMI assertion for the selector with empty l and a values. Omitting the record triggers Organizational Domain fallback instead of opting out. The opt-out applies to that exact From domain and selector.
Not automatically. Mail using a covered Organizational Domain assertion can reuse its certificate. A local BIMI record or different logo requires a fresh certificate coverage check against the assertion the receiver selects.

