Free, reads live DNS
Email risk scan
A quick pre-send risk check for the deliverability signals that quietly sink cold outreach.
Risk score: /100
for · setup score /100 ()
Risk signals
No major risk signals detected — your authentication looks solid.
Direct answer
What makes a sending domain risky?
The fastest way a new or cold-email domain lands in spam is a missing DMARC record, an SPF record that returns PermError, or a domain that has never sent mail and then sends a lot at once. This scan scores those DNS signals before the first campaign. It does not measure inbox placement. Only a seed test to real mailboxes can show that.
- No DMARC record means a receiver has no policy and no report address for the domain.
- An SPF PermError is treated like a broken record, even when the IP would have been allowed.
- A domain that only exists to send, with no website and no MX, is a common spam pattern.
- A low risk score means the DNS is ready. It does not mean the first 1,000 emails should go out on day one.
Questions people ask
What is a high-risk result?
High risk means at least one authentication record is missing or invalid, usually DMARC or SPF. Fix that record before sending. Medium risk often means the records exist but the policy is still p=none or the lookup count is close to 10.
Can a risk scan see if I am on a blacklist?
This scan reads authentication DNS. Use the blacklist checker for DNSBL listings of the sending IP. A clean blacklist and a high risk score can happen at the same time.
Should I send from a new domain if the scan is low?
Low risk is the starting point. Send a small volume first, to people who expect the mail, and increase only while complaints stay low. Authentication does not replace a sending history.
How is this different from the full audit?
The audit lists every record and the DNS change for each one. The risk scan turns the same signals into a single pre-send judgment: send, fix first, or fix and then warm up.
The records are only half of inbox placement.
Once SPF, DKIM, and DMARC pass, a cold domain still needs a slow sending history. iSend warms the domain and sends with the same authentication these tools just checked.