---
title: "DKIM record check — Lemwatch Help"
description: "Verifies DKIM selector records exist and use ≥1024-bit keys — the invisible half of email deliverability that most teams forget."
canonical: "https://lemwatch.com/help/dkim-record-check"
source: "https://lemwatch.com"
---

# DKIM record check

> Verifies DKIM selector records exist and use ≥1024-bit keys — the invisible half of email deliverability that most teams forget.

## Quick answer

 Add your DKIM selectors in the site editor. Lemwatch checks that each selector._domainkey record resolves and uses a strong key.

## What it checks

- Selector TXT record resolves

- Key length (flags <1024-bit as weak)

- p= (public key) is not empty (empty means revoked)

- v=DKIM1 tag present

## Where to find it in Lemwatch

 **Site details → Security → Email auth → Selectors.** Add one row per selector (e.g. google , s1 ).

## How to fix

- Ask your mail provider for their DKIM selector name.

- Add the selector in Lemwatch.

- Publish the TXT record at <selector>._domainkey.yourdomain.com .

- Rotate keys yearly to 2048-bit.

## FAQ

### How many selectors can I add?

 Up to 5 per site.

### Does Lemwatch verify signatures on real messages?

 No — record health only. For signature verification use your provider's dashboard.

## Related

- SPF record check

- DMARC record check

- DNS MX record check


## Related

- [Help centre](https://lemwatch.com/help)
- [SPF record check](https://lemwatch.com/help/spf-record-check)
- [DMARC record check](https://lemwatch.com/help/dmarc-record-check)
- [DNS MX record check](https://lemwatch.com/help/dns-mx-record-check)
- [Blacklist & reputation check](https://lemwatch.com/help/blacklist-reputation-check)
- [Lemwatch pricing](https://lemwatch.com/pricing)
- [Discord Integration](https://lemwatch.com/help/discord-integration)