JavaScript Requires Chilkat v11.0.0+
JavaScript
Verify a signed message with a trusted public key file
See more DKIM Examples
Use the saved signed message and its matching public PEM file to test a signing configuration before publishing DNS. This verifier caches the key for the exact selector and domain. A different pair can trigger normal DNS lookup, so the example also checks which signature actually verified.
Load the key from a trusted source independent of the received message. A pass with a locally supplied key confirms the cryptographic match. Use the published-key check to test what recipients can retrieve.
Note
This example is intended for running within a Chilkat.Js embedded JavaScript engine. All Chilkat JavaScript examples require Chilkat
v11.4.0 or greater.
var success = false;
// Assumes Chilkat is unlocked. See Global Unlock Sample.
var message = new CkBinData();
success = message.LoadFile("signed.eml");
if (success !== true) {
console.log("Could not read signed.eml.");
return;
}
var verifier = new CkDkim();
var domain = "example.com";
var selector = "mail2026";
success = verifier.LoadPublicKeyFile(selector,domain,"dkim-public.pem");
if (success !== true) {
console.log(verifier.LastErrorText);
return;
}
// signed.eml from the signing example has our newly added signature at index zero.
if (verifier.NumDkimSigs(message) == 0) {
console.log("No DKIM signature in signed.eml.");
return;
}
success = verifier.DkimVerify(0,message);
if (success !== true) {
console.log(verifier.LastErrorText);
console.log(verifier.VerifyInfo);
return;
}
var info = new CkJsonObject();
success = info.Load(verifier.VerifyInfo);
if ((success !== true) || (info.StringOfEquals("domain",domain,true) !== true) || (info.StringOfEquals("selector",selector,true) !== true)) {
console.log("The first signature is not from the selected domain and selector.");
return;
}
console.log("Signature verified with the saved key for " + selector + "._domainkey." + domain);