Check your email domain’s DNS records.
See whether your domain’s SPF, DKIM, DMARC and MX records are in place, and what to fix before you send. It runs in your browser, and queries go directly to Cloudflare or Google; Kirora doesn’t see or keep the domain. It checks published DNS records; it doesn’t test inbox placement.
The DNS services didn’t return a result. Try again in a moment, or check your connection.
DKIM
Checking…DMARC
Checking…MX
Checking…What each record does
- SPF
- A TXT record on your domain that lists the services allowed to send its email, such as
v=spf1 include:… ~all. A domain has exactly one; two or more make SPF fail. Eachincludecan lead to more DNS lookups, and more than 10 in all also fails. - DKIM
- A public key at
selector._domainkey.yourdomain.com. Your email service signs each message, and the receiving server checks the signature against this key, so it knows the email wasn’t changed on the way. Each service picks its own selector, and the checker tries the common ones. - DMARC
- A TXT record at
_dmarc.yourdomain.comthat states your domain’s policy for mail that fails DMARC authentication:p=nonerequests no change to handling,p=quarantineasks receivers to treat the mail as suspicious andp=rejectasks them to reject it. Receiving providers decide how to handle each message. Gmail and Yahoo require a DMARC record from bulk senders. - MX
- The servers that receive email for your domain. Sending doesn’t need them, but most domains that take replies publish them; a null MX record (
0 .) says the domain accepts no email.
Why these records matter, and what bounces and complaints do to your sending: Email deliverability basics. Setting up a domain in Kirora: Set up a sending domain.
Build your next customer campaign with Kirora.
Create a free workspace, verify your sending domain and import your contacts. Build a campaign or automate a welcome journey, then review it before sending.
See our Acceptable Use Policy, Terms and Privacy Policy.