Loupe LookoutSaltbrush & Sage
The domain resolves, the records a store needs are right, and mail from the domain is authenticated (SPF, DKIM, DMARC).
saltbrushandsage.com resolves to 23.227.38.65; www.saltbrushandsage.com resolves; 2 of 2 nameservers answer.
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.
Bare domain 23.227.38.65 (Shopify), www to shops.myshopify.com.
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.
Mail delivered to aspmx.l.google.com (Google Workspace).
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.
One record, 3 lookups, ends ~all, includes _spf.google.com, shops.shopify.com.
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.
Selectors found for Google Workspace, Shopify and Klaviyo: google, shopify, kl, kl2.
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.
p=none, reports to mailto:dmarc@saltbrushandsage.com.
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.
Ask RDA to handle thisNone of the optional records are published.
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.
Clear on Spamhaus DBL, SURBL, Spamhaus ZEN, SpamCop, PSBL. Advisory.
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.
Ask about any figure, check or change on this page. Every answer names its source and date.
Loupe answers from the figures on this page. For anything else, your RDA team is at support@rubydigitalagency.com.