Adding a sending service
Review your authentication records when connecting a marketing platform, CRM, or transactional email service.
Run an email domain health check for SPF, DKIM, DMARC, mail servers, and nameservers. Review the published records, configuration findings, and suggested next steps in one report.
Check whether your DMARC reporting destination is configured.
Fictional example data for illustration. Results depend on the domain and selector checked.
Review your authentication records when connecting a marketing platform, CRM, or transactional email service.
Inspect published mail-server and nameserver records after configuration changes.
Bring authentication and email DNS findings together before planning your next investigation.
See the records behind your email setup and the findings that deserve attention.
v=spf1 include:_spf.google.com include:send.example.net ~allInspect your SPF record, included sending services, policy qualifier, and the lookup information shown in the report. Review findings alongside the services your business uses to send email.
googleChoose a standard DKIM selector or enter a custom one. Review whether a record is found at that selector, its published value, and the available record findings.
v=DMARC1; p=quarantine; aspf=r; adkim=r; sp=noneReview your published DMARC policy, reporting destinations, SPF and DKIM alignment settings, and subdomain-policy configuration.
| Priority | Mail server |
|---|---|
| 10 | mx1.example.net |
| 20 | mx2.example.net |
Review your mail-server hostnames and their MX priorities in one table. Inspect the receiving configuration and the provider information identified by the report.
ns1.example.netFoundns2.example.netFoundSee the published nameservers and the provider information identified by the scan. Use the findings to review your domain’s DNS hosting configuration.
v=DMARC1; p=quarantine; aspf=r; adkim=r; sp=noneFinding: Check whether your DMARC reporting destination is configured.
Review status labels, explanatory findings, and suggested actions within each record section. Copy the available authentication record values when sharing details with your administrator or provider.
Illustrative previews show the structure of a domain scan report.
Provide the domain whose email DNS configuration you want to inspect.
Select a standard option or enter the selector supplied by your email service.
Explore the record sections, status labels, and recommendations. Run another scan after updating your configuration to review the newly published records.
The scan reads published DNS information. DNS changes are made through your provider.
Review domain configuration alongside your campaign-testing tools in one account.
It is a diagnostic review of your domain’s published email and DNS configuration. InboxPlacement.io brings SPF, DKIM, DMARC, MX, and nameserver findings into one report.
It shows the supported records found during the scan, their values, status labels, and configuration findings. You can use the report to investigate your setup and plan changes with your administrator or provider.
A selector identifies the DKIM record used by a sending service. Choose the selector supplied by your provider, or find the s= value in a message’s DKIM-Signature header.
The result applies to the selector checked in that scan. Your domain may publish DKIM records under other selectors. Confirm your sending service’s selector and scan again.
Domain Forensic Scan examines published configuration at the time of the scan. DMARC Monitoring analyzes reports received over time, including sending sources and authentication results.
It reviews domain configuration. Use Inbox Placement Test to observe placement across the available seed inboxes.
The scan displays records and findings. Apply configuration changes through your DNS or email provider.