Loupe LookoutSaltbrush & Sage

Saltbrush & Sage · Lookout Score 89

DNS and email 90

The domain resolves, the records a store needs are right, and mail from the domain is authenticated (SPF, DKIM, DMARC). Weight 10 of 105 in the Lookout Score.

Domain resolves and the nameservers answer Pass

saltbrushandsage.com resolves to 23.227.38.65; www.saltbrushandsage.com resolves; 2 of 2 nameservers answer.

DNS from the Lookout server, 21 Nov 2026, 23:40 MST · weight 3 · checked daily

Why it matters, and what to do

If the name does not resolve, nothing else matters. Two answering nameservers is the minimum for the domain to survive one of them failing.

What to do: Check the records at the DNS host and that the nameservers set at the registrar are the ones carrying the records.

Rule: Bare domain or www not resolving, or fewer than two nameservers answering: fail, and an alert.

The records Shopify expects Pass

Bare domain 23.227.38.65 (Shopify), www to shops.myshopify.com.

DNS from the Lookout server, 21 Nov 2026, 23:40 MST · weight 2 · checked daily

Why it matters, and what to do

Shopify serves the store only when the bare domain points at its address and www is a CNAME to shops.myshopify.com. Stray records from the previous host cause intermittent certificate errors and the occasional visitor landing on the old site.

What to do: Set the A record and the www CNAME exactly as the Shopify domains page shows, and delete the old host's records.

Rule: Shopify stores only. Bare domain not pointing at Shopify, www not a CNAME to shops.myshopify.com, or leftover records from the old host: warn.

Mail exchangers present Pass

Mail delivered to aspmx.l.google.com (Google Workspace).

DNS from the Lookout server, 21 Nov 2026, 23:40 MST · weight 1 · checked daily

Why it matters, and what to do

MX records say where mail for the domain is delivered. A domain that sends mail but cannot receive replies looks wrong to mailbox providers.

What to do: Add the MX records your mail provider publishes.

Rule: No MX record but an SPF record that sends mail: warn. No mail at the domain at all: not applicable.

SPF record Pass

One record, 3 lookups, ends ~all, includes _spf.google.com, shops.shopify.com.

DNS from the Lookout server, 21 Nov 2026, 23:40 MST · weight 3 · checked daily

Why it matters, and what to do

SPF lists who may send mail as the domain. A domain can have only one SPF record; two make every receiver fail the check, which is the most common cause of store mail landing in spam. The 10-lookup limit is in the standard: past it, receivers stop evaluating.

What to do: Merge the sources into one record, drop duplicate a and mx mechanisms and redundant + prefixes, and keep ~all until every sender is confirmed.

Rule: Exactly one record, valid syntax, 10 or fewer DNS lookups, ending ~all or -all, including each known sender. Two records, none, more than 10 lookups or +all: fail. A known sender missing: warn.

DKIM selectors published Pass

Selectors found for Google Workspace, Shopify and Klaviyo: google, shopify, kl, kl2.

DNS from the Lookout server, 21 Nov 2026, 23:40 MST · weight 2 · checked daily

Why it matters, and what to do

DKIM signs each message so receivers can tell it was not altered. Each sending platform publishes its own selector; the record is usually a CNAME the platform asks you to add.

What to do: Add the selector records from the sending platform's email authentication page.

Rule: A selector expected for a known sender (Google Workspace, Microsoft 365, Shopify, Klaviyo, Mailchimp) missing: warn.

DMARC policy Warn

p=none, reports to mailto:dmarc@saltbrushandsage.com.

DNS from the Lookout server, 21 Nov 2026, 23:40 MST · weight 3 · checked daily

Why it matters, and what to do

DMARC tells receivers what to do when SPF and DKIM fail, and since 2024 Google and Yahoo require it from anyone sending in volume. p=none only reports; quarantine or reject is what actually protects the domain from being spoofed.

What to do: Publish a _dmarc record with p=quarantine and a rua address once SPF and DKIM pass for every sender.

Rule: Missing: fail. p=none: warn. quarantine or reject: pass. A reporting address (rua) is noted.

Ask RDA to handle this

BIMI, MTA-STS, TLS-RPT, CAA and DNSSEC Info

None of the optional records are published.

DNS from the Lookout server, 21 Nov 2026, 23:40 MST · weight 0 · checked daily

Why it matters

The optional layers: BIMI shows the logo in inboxes, MTA-STS and TLS-RPT enforce and report encrypted delivery, CAA limits who may issue certificates, DNSSEC signs the zone.

Rule: Informational, not scored.

Domain and site address not on the public blocklists Pass

Clear on Spamhaus DBL, SURBL, Spamhaus ZEN, SpamCop, PSBL. Advisory.

Spamhaus, SURBL, SpamCop and PSBL from the Lookout server's resolver, 21 Nov 2026, 23:40 MST · weight 1 · checked daily

Why it matters, and what to do

A listing on Spamhaus or SURBL means mail from the domain, or mail linking to the site, is being refused or filed as spam somewhere.

What to do: Each list has its own removal page; the listing reason (a compromised form, a bad shared address) has to be fixed first.

Rule: Listed: warn, and an alert. Advisory: the public lists are queried a few times a day from our own resolver and can be unavailable.