Is your email landing in spam?

The most common technical cause is missing or broken SPF, DKIM or DMARC records - without them, inbox providers can’t confirm the email really came from you. Content, sending volume and your domain’s reputation matter too, but authentication is the foundation the rest depends on.

SPF lists the servers allowed to send email for your domain. DKIM adds a signature to each email, so receivers can tell it wasn’t altered and really came from you. DMARC ties the two together - it tells receivers what to do when an email fails, and sends you reports on who is sending as your domain.

Yes. Since 2024, Gmail and Yahoo require every sender to have SPF or DKIM, and anyone sending in bulk to have SPF, DKIM and a DMARC record. Email that doesn’t meet the rules is more likely to be sent to spam or rejected.

DKIM keys are published under a name called a selector, and there is no way to list a domain’s selectors. We check the defaults used by common providers, but many services use custom ones. Find the selector in your email provider’s DKIM settings and enter it to check it directly.

Start with p=none and a reporting address, so you can see every service sending as your domain without affecting delivery. Once the reports show all your real senders passing, move to p=quarantine, then to p=reject for full protection against spoofing.

Usually a few minutes, but it can take up to 48 hours depending on your DNS provider and the record’s TTL setting. If a fix doesn’t show up yet, check again later.

Yes. The checker only reads public DNS records - the same information any mail server looks up when you send an email. We don’t send any email, need no login and don’t store your results.