SPF
SPF lists the servers allowed to send mail for your domain. A missing or broken record makes receivers more suspicious of form notifications sent From that domain.
If your contact form submits but the email never arrives, check the recipient address first, then the spam folder, then your sender configuration, then the form backend log. This diagnostic sends you to the SPF, DKIM and DMARC checkers for the domain in your From address and explains what each result means.
Paste the domain from the From address into each checker, then use the notes below to read each result.
SPF lists the servers allowed to send mail for your domain. A missing or broken record makes receivers more suspicious of form notifications sent From that domain.
DKIM adds a cryptographic signature that receivers can verify, and it usually survives forwarding. You need the selector your email provider uses as well as the domain.
DMARC tells receivers what to do when SPF or DKIM fails, and it sends you reports. Start with a monitoring policy before you move to quarantine or reject.
These checkers read public DNS records. Passing DNS checks helps receivers trust your mail, but it does not guarantee inbox placement: reputation, content, recipient filters and sending volume still matter.
SPF tells receivers which servers may send mail for your domain. If the domain in your From address has no SPF record, or the record does not include the server that sends your form notifications, receivers have less reason to trust the message.
DKIM gives each message a cryptographic signature that the receiver can verify against a public key in DNS. A correct signature also survives many forwarding paths, where SPF can break.
DMARC ties SPF and DKIM to the From domain and tells receivers what to do when neither passes. A monitoring policy with reporting shows you which senders are failing before you tighten it.
These are public DNS records, so the checkers can only show what is published. They cannot see your inbox, your form backend or your sender reputation. Use them as evidence about the sender configuration, then keep working through the sequence below. For the full setup order and the alignment mistakes that cause failures, read the email authentication guide for form notifications.
A success message only confirms the browser reached the form backend. The notification email is a separate step after that, so the missing message is usually a wrong recipient address, a spam or quarantine folder, a sender authentication problem, or an error recorded in the form backend log. Work through those four checks in that order.
No. The records help receivers verify that your sending server is allowed to use your domain, and they reduce spoofing risk, but inbox placement also depends on sender reputation, message content, recipient filters and sending volume. Treat the DNS checks as one part of the diagnosis, not a guarantee.
Look at the From address on the notification your form sends, then use the part after the @ sign. If your form sends From hello@yourdomain.com, check yourdomain.com. For DKIM you also need the selector from your email provider, which appears as the s= value in a message's DKIM-Signature header.
Check the recipient address in your form backend settings for a typo or an unverified destination, search all mail plus spam and quarantine, confirm the sender configuration uses an address on your authenticated domain, and read the backend log to see whether the send was delivered, bounced or never attempted.
All free form tools · Contact form works but no email arrives · Why form emails go to spam
Enter monthly submissions and compare the cheapest listed plan across eight form backends.
Enter form views and submissions to get your contact form conversion rate, plus leads needed and total value for a target.
Enter a domain to check its SPF, DMARC and MX records and get a plain-English fix for each.
Look up a domain's SPF record, see each mechanism explained and count DNS lookups against the 10-lookup limit.
Pick a policy and report address and copy a ready _dmarc TXT record.
Look up a domain's DMARC record and see the policy and every tag explained.
Enter a domain and selector to check its DKIM key, with presets for common senders.
Tick your email providers and copy one SPF TXT record with a lookup count.
Paste form HTML to audit its honeypot, endpoint, CAPTCHA markers and spam resistance.
Generate a hidden anti-spam input with your chosen name and hiding technique.
Enter an endpoint, choose GET or POST, add an access key and field names, then copy the HTML.
Paste a form snippet to inspect required, type=email, minlength and pattern checks in a live preview.
Check a form action URL for reachability, CORS headers, POST acceptance and backend.
Encode your email so spam scrapers can't read it but people can still click it.
Build a mailto: URL with recipients, CC, BCC, subject and a pre-filled body.
Test letters and numbers only, spaces, handles and Unicode; copy validation patterns.
Test the WHATWG email regex and two other patterns against edge cases and your own list.
Test numbers against E.164, US/Canada and digits-only patterns and copy code snippets.
Test US ZIP, ZIP+4, Canadian and UK postal codes and copy the regex or HTML pattern.
Test digits, decimals, money and thousands separators and copy validation patterns.
Test dd/mm/yyyy, mm/dd/yyyy and ISO dates with leap-year checks and copy JS or HTML patterns.
Test name patterns for O'Brien, accents and Unicode letters; copy JS or HTML pattern snippets.
Test username presets for GitHub, Instagram and X; check reserved names and copy JS or HTML patterns.
Test IPv4, IPv6, CIDR and private-range patterns and copy JS or HTML pattern snippets.
Test website URLs against http(s) regex patterns and new URL(), and copy JS, HTML or PHP code.
Generate and verify webhook signatures for common providers in your browser.
Encode text, build an x-www-form-urlencoded body or parse a query string.
Pick strength rules, test passwords live and copy the regex or HTML pattern.
Build campaign URLs with UTM parameters, tag a CSV in bulk and check tagged links.
Paste HTML and get JSX or a working React/Next.js form component.
Convert images to Base64 data URLs in your browser and copy HTML and CSS snippets.
Paste a Base64 data URI to preview and download the decoded image.
Decode Base64 to readable UTF-8 text or encode text to Base64, locally in your browser.
Fetch a direct image URL in your browser and get its Base64 data URL.
Build a form visually and copy HTML, React JSX or Tailwind code.
Describe your form in plain English and copy working HTML.
Test 24-hour, AM/PM and ISO time patterns and copy JavaScript, Python or HTML snippets.
Test Visa, Mastercard 2-series, Amex and more card patterns with brand detection and a Luhn check.
Test #RGB, #RRGGBB and alpha hex colors plus rgb() and hsl() values with live color swatches.
Test UUID v1-v8, nil/max and GUID formats with version and variant checks; copy JS or HTML patterns.