Will your app's emails land in the inbox?
Type the domain your Lovable app sends email from, or any address on it. We read its public DNS records and tell you, in plain English, whether the SPF, DKIM and DMARC records that Gmail and Yahoo look for are in place, and what to fix first. It is free and takes a few seconds.
Check your domain
We only look up public DNS records, and we store nothing.
What this checks
It checks
- MX records: whether replies and bounces sent to your domain have a mail server to go to, and which mailbox provider it looks like.
- SPF: that there is exactly one record, how it ends (-all, ~all, ?all or +all), and that it needs no more than 10 DNS lookups once its include:s are followed.
- DKIM: a key under 21 common names (selectors), such as resend, google, selector1 and k1, and whether it has been revoked. Also the send. subdomain with MX and SPF records that Resend's domain setup uses.
- DMARC: that there is exactly one record, and its policy (none, quarantine or reject), report address and pct.
It does not check
- Whether a particular email will reach the inbox. Nothing outside the inbox provider can promise that.
- Your sending reputation, your spam-complaint rate, or whether your domain is on a blocklist.
- The content of your emails, or their links.
- The DKIM selector your provider actually uses, if it is not one of the common names: your provider's dashboard shows it.
- Which sender your app uses. On Lovable Cloud or your own Supabase project, that is a setting, not a DNS record.
Why these records: Gmail and Yahoo require SPF or DKIM from every sender, and SPF, DKIM and DMARC from bulk senders, which Google defines as more than 5,000 messages a day to Gmail. Setting up the records with Resend? Our guide to Lovable email with Resend covers it step by step. For a wider look at what stands between your app and real users, take the free production-readiness check.
Questions about the checker
Does a good result mean my emails will reach the inbox?
No. It means the DNS records inbox providers look for are in place. Gmail and Yahoo also judge your sending reputation, your spam-complaint rate and what your emails say, and a new domain typically needs a few weeks of steady sending to build trust. We cannot see any of that from DNS.
Why couldn't the checker find my DKIM key?
A domain's DKIM keys sit under names (selectors) that cannot be listed, so we try 21 common ones. If your provider uses another name, the key can be there and still not show here. Your provider's domain settings show the selector it uses and whether DKIM is verified.
Which domain should I check?
The one in the From address of your app's emails. If you send from a subdomain, such as auth.yourapp.com, which Supabase and Resend both suggest, check that subdomain: SPF and DKIM are set per name. For DMARC we also look at the parent domain when the subdomain has no record of its own.
Do I need DMARC for a small app?
Gmail and Yahoo only require it from bulk senders, which Google defines as more than 5,000 messages a day to Gmail. It is still worth adding from the start because it is one DNS record and it protects your domain from spoofing. Start with p=none and a reporting address, then tighten it.
Do you store the domain I check?
No. We look up public DNS records while the check runs and keep nothing afterwards. To stop the tool being abused, your IP address is counted in memory (10 checks per 10 minutes) and never written down.
Records right, emails still missing?
Our engineers find the cause, fix the sender and the records, and test every email on your live app.
See vibe coding rescue