Additional service signals
Published SPF, DKIM and discovery records can reveal configured links to major platforms beyond incoming mail.
Mail-client discovery
Microsoft 365
! Non-European provider
CNAME autodiscover → autodiscover.outlook.com
The standard Outlook discovery name routes mail-client setup to Microsoft 365. This is stronger evidence of tenant configuration than an old verification token, but does not reveal mailbox storage location.
Current DNS record ↗Provider setup guide ↗
Mail-signing setup
Microsoft 365
! Non-European provider
CNAME selector1._domainkey → selector1-commandersact-com._domainkey.tagco.onmicrosoft.com · selector2._domainkey → selector2-commandersact-com._domainkey.tagco.onmicrosoft.com
A provider-specific DKIM record is published for Microsoft 365. This shows configured mail-signing infrastructure, but not that every message currently uses it.
Current DNS record ↗Provider setup guide ↗
Sender authorisation
Microsoft 365
! Non-European provider
SPF include:spf.protection.outlook.com
Microsoft 365 is authorised to send email for this domain. The SPF entry can be unused or stale and does not reveal the configured data region.
Current DNS record ↗Provider setup guide ↗
This is a targeted check, not a complete zone inventory. Generic Google and Microsoft verification tokens are ignored because they do not prove product use or a data flow. DNS normally cannot list arbitrary subdomains or customer-chosen DKIM selectors, including Salesforce selectors. Missing signals are not proof that a provider is unused.