Look for a delegated subdomain
Nothing is delegated at the host you entered. Sending subdomains are often set up under a different prefix. This checks the prefixes Salesforce implementations use most often.
Domain configuration check
Domain configuration check
Verify that a domain's DNS is configured correctly for Salesforce marketing products, before you activate it in the platform.
Nothing is delegated at the host you entered. Sending subdomains are often set up under a different prefix. This checks the prefixes Salesforce implementations use most often.
Results come from public resolvers, which cache answers for the length of each record's TTL. A change made in the last few hours may not be visible yet. Re-run the check later rather than changing DNS again.
No. The expected record sets are what Salesforce documents for a full configuration, and plenty of working accounts skip parts of them. A domain with no Reply Mail Management will have no reply records, for example. Read a missing row as something to confirm, not something to fix on sight.
DNS only proves the records exist. Sending can still fail if the domain was never activated in the platform, if the business unit points at a different domain, or if a DMARC policy rejects the alignment. Those live in the application, not in DNS.
Lookups go to Google and Cloudflare over DNS-over-HTTPS, whichever answers first, and the resolver used is named next to the results. Both are public recursive resolvers, so you see what the rest of the internet sees rather than what your own network sees.
No. The lookups run in your browser. No domain you enter is sent to High Tide or saved anywhere, and nothing is logged.
DKIM keys are published at a name only the sender knows, in the form selector._domainkey.yourdomain.org. There is no way to discover it from DNS, so without the selector the key cannot be found. Platforms that manage DKIM for you, like delegated Engagement and Marketing Cloud Next, do not need one and the field is hidden for them.