Diagnostic, not generative
SigLint starts with existing HTML. It is not another template or signature generator.
Why SigLint exists
HTML email signatures often look correct in a browser and then behave differently when copied into Outlook, Gmail or another email client. SigLint is built for the point between “I already have signature HTML” and “I need to know what is risky before I install or send it.”
Evidence before scores
The product reports concrete findings, affected clients and recommendations instead of inventing a compatibility percentage.
Browser-local by default
The current checker analyzes pasted or uploaded HTML in the browser. Signature source is not sent to a SigLint application backend.
Clear limitations
Static analysis cannot prove pixel-perfect rendering. Important signatures should still be tested in the actual email clients used by recipients.
Current scope
The current release focuses on deterministic compatibility checks for Outlook Classic, Gmail and general HTML signature risks, plus a transparent Rules Library and source-backed methodology.
Rules LibrarySee exactly what the checker currently knows.MethodologyUnderstand evidence tiers, severity and limitations.ChangelogReview material rule and product changes.
What SigLint does not claim
SigLint does not emulate Outlook, Gmail or Apple Mail. It does not currently provide screenshot previews from real email clients, enterprise signature deployment, account-based project storage or automated redesign of arbitrary signature layouts.
Product stage
SigLint is in an early public validation stage. The immediate goal is to make the checker genuinely useful and auditable, then use real search and product usage to decide what deserves expansion.