Configure DKIM and DMARC for your domain

Publish authentication records at the DNS provider that currently answers for your domain: Dashboard → DNS only when PK Hosting hosts DNS, otherwise Cloudflare or your registrar. List every service that sends as your domain before editing a record, including website forms and campaign tools.

1. Check SPF and DKIM for each sender

SPF is a TXT record at the domain that lists authorized senders. Start with the value shown in your hosting service details and merge any legitimate third-party sender into the one SPF record; two SPF records can break evaluation. Do not copy another company's include: value without confirming you use that provider.

DKIM signs outgoing mail with a provider-specific key. Ask support for the exact selector and TXT value for your PK Hosting mailbox; a third-party sending platform gives you its own selector and key. Publish each at the requested DNS name unchanged, then enable signing in the sending service where required.

2. Begin DMARC in monitoring mode

DMARC is a TXT record at _dmarc.yourdomain.com. A starting example is v=DMARC1; p=none; rua=mailto:reports@yourdomain.com, but only use an address you control and can receive aggregate reports at. Monitoring mode does not tell receivers to reject failing mail. Move to quarantine or reject only after checking legitimate senders and alignment; otherwise genuine invoices and form mail may be blocked. DMARC.org explains the staged policy.

3. Verify a real message

Send a test message from each sending platform to a mailbox you control. Inspect its authentication results for SPF, DKIM and DMARC pass/fail and the From domain, rather than relying on a DNS editor's saved state. Wait for DNS to propagate and retest. If one sender fails, send support the failing result and provider name without sharing private keys or mailbox passwords. Google's sender guidelines describe why domain alignment matters; passing authentication improves legitimacy but does not guarantee inbox placement.