Use suggestions and mail checks

Suggestions are starting points

Discovery and provider patterns suggest monitor configurations for records that may matter. Treat these as templates to review, not a statement that your organization uses a particular service or that every discovered record needs monitoring.

A detected mail-provider pattern is a heuristic based on DNS. A record returned by a named DNS source is a measured observation. Neither proves ownership, intended configuration or successful email delivery.

1. Open a domain's Suggestions after discovery.
2. Choose the relevant hostname and record type. Review the expected behavior before enabling it.
3. Adjust the interval and notifications to the service's importance. Edit an existing monitor instead of creating another for the same hostname/type.

Email policies in plain language

MX tells senders where incoming email should go. SPF describes who may send using a domain in the envelope address. DMARC describes alignment and how receivers should handle failures. A p=none policy asks receivers to observe rather than request blocking.

DKIM uses a configured selector to find a public signing key. DNStracr does not enumerate every possible selector. Ask your email provider for the selector and configure that record explicitly.

SPF analysis follows bounded includes and checks common policy problems, but it is not a complete sender-IP authorization test. DKIM key checks do not verify a real email signature. Policy presence does not guarantee deliverability.

Before changing an email policy

Inventory legitimate sending services with your email administrator. Removing an SPF include or tightening DMARC without checking those services can affect legitimate mail. DNStracr provides evidence; make changes in your DNS provider after reviewing their impact.