How to fix what Canary found

Everything Canary can report, and the fix for each. No technical background needed.

Social connection - reconnect

What it is. The login that lets the platform post to a client's Facebook, Instagram, LinkedIn or Google page. It has an end date.

Why it matters. After that date scheduled posts fail, and nothing tells anyone until the client notices their page has gone quiet.

The fix. In the client's account open Social Planner, click the gear icon, then Integrations. Disconnect the account Canary named and connect it again. It takes about two minutes.

Whoever reconnects has to be an admin of that page. If the page belongs to the client, forward them this section.

Facebook and Instagram push the date forward every time a post goes out, so an active page rarely gets close. The ones that run out are the quiet ones - a client between campaigns, a page nobody has posted to in two months.
The three email records below live in the same place: wherever the domain's DNS is managed - Cloudflare, GoDaddy, Namecheap, or your client's hosting panel. If someone else manages the domain, forward them the relevant section.

Sender check - SPF

What it is. A list of who is allowed to send email using your domain.

Why it matters. Without it, anyone can send mail that looks like it came from you, and your own mail is more likely to be filtered.

The fix. Add one TXT record:

TypeTXT
Name@  (the domain itself)
Valuev=spf1 include:_spf.google.com ~all

The include: part names your email provider. Google Workspace is shown above; Microsoft 365 uses include:spf.protection.outlook.com. Whoever sends your mail publishes the exact line - search for "<provider> SPF record".

Only one SPF record per domain. If one already exists, add the new include: to it rather than creating a second.

Spoofing policy - DMARC

What it is. An instruction telling Gmail and Outlook what to do with mail that fails the sender check.

Why it matters. Gmail has expected this since 2024. A domain without it looks unconfigured, and its mail gets pushed toward spam - quietly, with no bounce to tell you.

The fix. Add one TXT record:

TypeTXT
Name_dmarc
Valuev=DMARC1; p=none; rua=mailto:you@yourdomain.com

p=none means "watch, do not block". Start there - it is safe and cannot break sending. After a few weeks of reports, tighten to p=quarantine.

Signing key - DKIM

What it is. A cryptographic signature on every message, proving it really came from your domain.

Why it matters. Without it, a receiving server has no way to confirm the mail was not altered or forged.

The fix. You cannot write this record by hand - your email provider generates it. In Google Workspace it is under Apps → Google Workspace → Gmail → Authenticate email. The provider gives you a record to paste into DNS.

The selector

DKIM records live at <selector>._domainkey.yourdomain.com, and the selector differs per provider. Canary cannot guess it, which is why the field is optional - leave it blank and the check is skipped rather than reported wrongly.

ProviderUsual selector
Google Workspacegoogle
Resendresend
Mailchimpk1
Microsoft 365selector1

Certificate - SSL

What it is. The certificate that makes a page load over https without a warning.

Why it matters. When it lapses, visitors get a full-page browser warning instead of the site. Any ad traffic pointed there is wasted while it lasts.

The fix. Almost every host renews automatically - the usual cause of a lapse is that auto-renewal was switched off, or the domain was moved and nobody re-issued it. Open the hosting panel for that domain and confirm renewal is on.

If the domain belongs to the client, tell them while there is still time. A certificate that expires on a Saturday takes the site down until someone notices.

Canary reads the expiry date from the public certificate transparency log rather than from the live server. In almost every case that is the certificate being served. The exception is a certificate that was issued but never installed - so treat this as a warning to check, not as proof.

Still stuck

Send the domain and what Canary reported to contact@jimapps.dev and we will look at it.