SPF Record Checker
Validate SPF syntax and count the DNS lookups.
Test an address against the RFC rules, rule by rule.
The Email Syntax Checker walks an address rule by rule against RFC 5322 and 5321 — characters, quoting, dots, hyphens, labels and every length limit — and names the rule that fails.
A syntax checker that shows its working. Instead of one pass or fail, it walks the address rule by rule: the characters the local part may hold unquoted, whether a quoted form is balanced, leading and trailing dots, consecutive dots, the 64-character local limit, then the domain labels, their length, their hyphens, the top-level domain and the 254-character total.
That makes it useful for the argument you are actually having — whether a form is right to reject an address. A surprising amount of perfectly legal syntax gets refused by validation regexes written from memory: plus signs, apostrophes, single-character local parts, long new TLDs and international domains all trip them up.
Every rule cites what it is testing, so you can take the result to whoever wrote the regex.
Each check names what it tested and what it found.
Quoted local parts and IP literals get a warning, not a cross.
Local part, domain, each label and the TLD shown separately.
Plus signs, apostrophes and long TLDs are correctly accepted.
Nothing you paste is sent anywhere.
The one a form accepted or rejected that you want to settle.
Each RFC rule is listed with a tick, a warning or a cross.
The local part, domain, labels and TLD are shown separately.
A warning is legal syntax that many systems reject anyway.
Yes. The plus sign is in the RFC 5322 atext set and is perfectly legal in a local part. Most providers also treat what follows it as a routing tag, which is a separate convention on top of the syntax.
The local part is capped at 64 characters, the domain at 253, and the whole address at 254 in an SMTP reverse path. This checker tests all three.
Because some legal syntax is refused in practice. A quoted local part and an IP address literal are both valid RFC 5322 and both rejected by most real mail systems, so they get a warning rather than a pass.
It is stricter and more informative. A regex gives one yes or no; this names the rule that failed, which is what you need when the answer is surprising.
What people who use the Email Syntax Checker think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the Email Syntax Checker. It takes half a minute and no account.
Write the first reviewValidate SPF syntax and count the DNS lookups.
Catch gmial.com, yahooo.com and every near miss.
Find the info@, admin@ and sales@ addresses in a list.
Tell a hard bounce from a soft one, and from a block.
Validate the email column and keep the rest of the row.
Read a message header: route, delays and auth results.
Score any address out of 100 and see what moved it.
One report on a list before you spend money sending to it.