Lockally

      Use your API key in the examples

      Replaces lk_live_… in the code samples on this site so you can copy and run them. It is stored in this browser only and is never sent anywhere, including to Ask AI.

      It will be visible on the page. Use a test key if you are sharing your screen or taking screenshots.

      Email authentication

      Authentication is the one part of deliverability that is mechanical. You either did it or you did not, and unauthenticated mail is rejected or foldered before anything else about it is considered.

      Full record-by-record setup lives in DNS records in full. This page is why each one matters and what the platform does with it.

      The three, and what each proves

      SPF says which servers may send for your domain. It authenticates the envelope sender, which is not the address your recipient sees.

      DKIM cryptographically signs the message. It proves the content was not altered and that it came from somebody holding your key. This is the strongest of the three and the one that survives forwarding.

      DMARC ties the other two to the From: address your recipient actually reads, and tells receivers what to do when neither aligns. Without DMARC, SPF and DKIM authenticate things the reader never sees.

      Alignment is the part that bites

      A message can pass SPF and still fail DMARC. This is the most common authentication surprise, so it is worth being explicit.

      DMARC requires that a passing SPF or a passing DKIM is aligned: the domain it authenticated must match the domain in the visible From:. A message passing SPF for a platform’s own bounce domain, with a From: of yours, passes SPF and fails DMARC.

      What makes it align here:

      • DKIM signs with your domain’s key, so it aligns by construction once the domain is verified.
      • SPF aligns when the envelope sender is on your domain, which is what a custom Return-Path gives you.

      DKIM alignment alone satisfies DMARC, which is why domain verification is the step that matters most.

      What the platform does

      Verify a domain and the platform signs every message from it with DKIM and publishes what you need for SPF. You do not manage keys or rotation.

      What it cannot do is publish your DNS for you, which is why verification is a gate rather than a formality: an unverified domain cannot send.

      Configure automatically can write the records for you at supported registrars.

      Publish DMARC, then tighten it

      Start permissive and move:

      v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com

      p=none changes nothing about handling and starts the reports. Read them, confirm everything legitimate aligns, then move to p=quarantine and eventually p=reject.

      The platform ingests aggregate reports for domains hosted here:

      DOMAIN=yourdomain.com
      
      curl -s https://api.lockally.com/v1/domains/$DOMAIN/dmarc \
        -H "Authorization: Bearer $LOCKALLY_API_KEY"

      Checking it worked

      The fastest check is to send yourself a message and read the headers. In Gmail, “Show original” shows SPF, DKIM and DMARC results and, crucially, which domain each one authenticated.

      Three passes and a DMARC domain matching your From: is the target. Anything less, and fix that before investigating anything else on your deliverability.

      What authentication does not do

      It proves you are you. It does not make your mail wanted, and it will not keep mail out of spam if people do not engage with it or mark it as spam. It is the floor, not the ceiling: necessary, cheap, and not sufficient.