Send an email to your test address. See SPF, DKIM, DMARC, IP blacklist status and content analysis in a single report.
Send a normal message to this address from the email account you want to test.
Most delivery problems come from a few common causes. The table below lists the most frequent reasons and suggested fixes.
| Neden | Etkisi | Ne yapabilirsiniz? |
|---|---|---|
| Missing SPF record | It can't be verified that your mail was sent from an authorized server. | Check your domain’s SPF record and add your authorized sending servers. |
| DKIM signature missing or invalid | The email's integrity and authenticity can't be verified. | Make sure the DKIM signature is created correctly and added to your emails. |
| No DMARC policy | Alignment of SPF and DKIM results with your domain can't be checked, and no reporting is produced. | Review your DMARC policy and monitor the reports. |
| IP on a blacklist | If the sending IP is on blacklists, messages may be rejected or land in spam. | Investigate the blacklisting reason, fix the issue and request delisting. |
| IP reputation and send volume | Irregular or high-volume sending can hurt IP reputation. | Send steadily and consistently, and avoid sudden volume spikes. |
| Suspicious content | Misleading links, excessive images or spammy phrases trigger filters. | Review your email content and avoid phrases that may be seen as spam. |
| Unsubscribe header | For messages treated as bulk email, missing this header raises spam risk. | Add the List-Unsubscribe header and make sure it works. |
| PTR / HELO mismatch | Inconsistencies in the sending server's setup can cause trust problems. | Check your server's reverse DNS (PTR) record and HELO value and make sure they match. |
Tip: To check your domain’s records and for configuration steps, see the DNS Tools ve Setup Documentation pages.
The score summarizes the technical checks on the tested message. Because of the recipient provider's filters and sender reputation, it doesn't guarantee inbox delivery.
A personal test address is created for you. You send a real message to it from the email account you use. The incoming message is run through technical checks and the results are shown in a single report.
The most common causes are: missing or incorrect SPF/DKIM/DMARC records, the sending IP being on a blacklist, poor IP reputation, spam-triggering content, no plain-text version, and a missing List-Unsubscribe header. Your test shows each of these items separately.
SPF defines which servers may send mail on your behalf. DKIM adds a digital signature to the email, proving the content was not altered. DMARC defines what to do when SPF/DKIM fail and where reports go. Together they prevent spoofing and improve delivery.
No. The score summarizes the technical checks on the message you sent (authentication, IP reputation, content and format). Because of the recipient provider's own filters and sender reputation, even a high score doesn't guarantee inbox delivery.
The PTR (reverse DNS) record is set by the server/hosting provider that owns your outbound IP. Through your provider’s panel or a support request, make sure your IP has a PTR record that matches your HELO name.
The DNS tool reads your domain's SPF/DKIM/DMARC/MX records directly from DNS. The mail test sends a real message and measures the end-to-end behavior of the sending path (signing, IP, content, format), so it reflects real delivery conditions.
Manage sender identity, IP reputation and email security together with MailGuard.
