Cryptographic Proof
DKIM signs headers and body using a private key on the sending mail server, which mailbox providers verify against the public key published in your DNS.
Verify DKIM cryptographic signatures, discover active selectors automatically across major ESPs, resolve CNAME delegations, and audit key security.
Querying TXT & CNAME records across top ESP selectors and mail server signatures...
-
DKIM1
rsa
-
-
Always ensure your DKIM record is aligned with your Return-Path and From domain headers. For maximum mailbox provider reputation (Gmail, Yahoo, Microsoft), use 2048-bit RSA keys and maintain a strict DMARC quarantine or reject policy.
DKIM signs headers and body using a private key on the sending mail server, which mailbox providers verify against the public key published in your DNS.
Selectors allow domains to support multiple sending platforms (e.g. Google, SendGrid, Amazon SES) simultaneously under distinct selector._domainkey records.
When DKIM passes and the signing domain matches the From address, your emails achieve DMARC alignment, stopping spoofing and lifting delivery straight to the primary inbox.
Our scanner performs prioritized infrastructure analysis (MX and SPF records) followed by worldwide provider checks and pattern sweeps (selector1-100, dkim1-100, s1-100, k1-100, m1-100, mail1-100, email1-100, smtp1-100, em1-100, mg1-100, send1-100, and date rotations).
google, 20230601, 20210112, 20220608, 20240101selector1, selector2, s1, s2sig1, sig2, apple, iclouds1024, s2048, s1, s2protonmail, protonmail2, protonmail3mesmtp, fm1, fm2zoho, zmail, zeptomailses, amazonses, ses1, ses2s1, s2, smtpapi, sendgrid, m1k1, k2, mailgun, mg1, smtp20200101, pm, postmark, pm1mail, brevo, sendinbluemailjet, mj1, mj2scph, scph01..12, sparkpostresend, rs, reapi, elasticemail, eekl, klaviyo, kl1..3hs1, hs2, hubspotsfdc, salesforce, sf1, pardotzendesk1, zendesk2, zd1freshdesk, fd, fwac, dkim1, dkim2convertkit, ck, kitdefault, cpanel, plesk, xcloudflare, mimecast, barracuda, proofpoint