What it helps identify
A malformed address cannot become deliverable later. Removing structural errors early keeps later checks focused on addresses that could genuinely exist.
Email cleaning method
Find malformed addresses before they reach your campaign.
Syntax validation checks whether an address follows the structural rules required for email. Addresses with missing parts, invalid characters or impossible formatting can be classified immediately.
Why this check matters
Is the address written in a structure that an email system can understand?
Each validation layer answers one defined question. Keeping the scope clear prevents a positive signal from being mistaken for proof of everything else.
How the result stays useful
Structurally invalid addresses are separated from normal deliverable results with a clear status.
1ReceiveRead the selected email column
→
2EvaluateApply this validation signal
→
3ClassifyReturn a clear status
Inside the check
What happens during syntax validation.
Syntax validation is the deterministic first layer. It separates the local part before the @ sign from the domain after it, then checks whether both parts are present and structurally plausible.
The check looks for problems such as missing components, impossible spacing, repeated separators and characters that cannot appear in the submitted position. Harmless surrounding whitespace can be normalized without rewriting the address itself.
Passing this layer only means that the address is well formed enough to continue. The domain, mail servers and mailbox still need their own checks.
Step by step
How the signal is produced.
ListCleaner applies the check in a deliberate sequence and retains the original row so the result remains useful in your own system.
Split the address
Identify the local part and domain around one valid @ separator.
Apply structural rules
Check length, characters, separators and required domain labels.
Route the result
Stop impossible addresses early and pass plausible addresses to domain checks.
Interpret the evidence
Pass, review and failure do not mean the same thing.
The exact final status reflects all applicable validation layers. This method contributes the following evidence.
Positive signal
The structure is plausible, so verification continues. This is not yet proof that the mailbox exists.
Uncertain or contextual
Unusual but technically possible formatting may deserve review if the source system altered the address.
Negative signal
The address cannot be used as submitted and should not enter a normal sending list.
What this looks like in real data.
An entry such as “alex.example.com” has no @ separator and can be rejected immediately. “alex@example.com” is structurally plausible, but it still needs domain, MX and mailbox checks.
What this check cannot prove.
Syntax rules cannot tell whether the domain exists, whether its mail servers work or whether a recipient mailbox has been created. A perfectly formatted fictional address can pass this step.
How to use the result.
Keep the original value available for correction. Do not silently guess where punctuation or an @ sign belongs, because an automatic “fix” can create a different person’s address.
Frequently asked questions
Understand the signal before acting on it.
Email validation describes the evidence available at the time of a check. It does not replace consent, suppression lists or responsible sending practices.
Can syntax validation prove a mailbox exists?
No. It confirms that the address is structurally plausible. Domain and mailbox checks provide the later signals.
Does ListCleaner change malformed addresses?
No. The service classifies submitted data; it does not guess or silently rewrite an address.
Why not automatically correct every likely typo?
A suggestion can be shown to the person entering the address, but changing it without confirmation can turn one invalid address into a valid address owned by someone else.
Does capitalization change the result?
Domain names are case-insensitive. In practice most mailbox systems also treat the local part case-insensitively, but ListCleaner avoids relying on capitalization as proof of identity.
Can I use this method through the API?
ListCleaner exposes email verification and list-cleaning workflows through its API. The returned status summarizes the applicable validation results.
The complete process
Explore all nine validation methods.
Each page explains one part of the layered workflow and the decision it supports.
@↯⊘!MX◎≈↩◈
Syntax validation
Syntax validation checks whether an address follows the structural rules required for email. Addresses with…
Explore this check →Disposable emails
Disposable email services issue short-lived inboxes that people can abandon immediately. ListCleaner compares domains with…
Explore this check →Spam trap check
Spam traps are addresses used to identify poor acquisition or sending practices. ListCleaner checks submitted…
Explore this check →Complainers check
Complaint activity can affect sender reputation and inbox placement. This layer checks addresses against internal…
Explore this check →MX server check
Mail exchanger records tell sending systems where a domain expects to receive email. ListCleaner checks…
Explore this check →Domain validation
Domain validation evaluates the domain portion of an address and its supporting DNS signals. It…
Explore this check →Catch-all domain
Catch-all mail systems can appear to accept any address at a domain, including addresses that…
Explore this check →Hard bounce check
Hard-bounce risk can come from nonexistent mailboxes, inactive accounts or permanent domain failures. ListCleaner combines…
Explore this check →Tor exit node check
Tor exit nodes can obscure the originating network of an account or submission. This method…
Explore this check →Clean your list with all nine methods.
Upload a supported file, select its email column and follow progress in your dashboard.
