How it works
Every step, and exactly what it's allowed to do
This page exists so you never have to guess what domain-repair.com can touch. If a step needs a permission, it's named here.
Connect your sender
Instantly or Smartlead, read-only. We pull the list of sending domains you're already running outbound through. Nothing about your campaigns or leads. Paste an API key, validated live on connect, not an OAuth grant.
Scan every 6 hours
SPF, DKIM, DMARC, MX, and blacklist status for every connected domain, checked automatically every 6 hours. This is the same read-only lookup the free scan runs, just on a schedule instead of on demand.
Detect and explain
A finding isn't just a red dot. It's a plain-language explanation of what's wrong and why it matters, with a severity level, in the workspace.
Review or remediate
Where you've connected GoDaddy (or, once verified, Cloudflare), a proposed fix appears as a before/after diff. By default it waits for your approval. You can opt a domain into automatic remediation; you can opt it back out at any time.
Notify and report
You're told first, in the workspace, and by Slack if you connect a webhook. A client-ready written summary follows on a schedule, not as a raw DNS dump you have to translate yourself.
Sample, after connecting a sending platform
| Domain | Discovered from |
|---|---|
| vantage-cold.com | Instantly |
| northwind-outreach.co | Smartlead |
| brightline-sales.io | Instantly |
Try the fix logic yourself
This runs the exact SPF analysis and fix-proposal code the product uses, live, on a real domain or on a record you paste in. Nothing here is a mockup.
Review-before-apply vs. automatic remediation
The default once a provider is connected and write access is on for a domain. A proposed fix appears as a diff and sits there until someone clicks Approve, then Apply. Nothing is written without both of those being a real, separate click.
Turned off is always the fastest way out
Current status: GoDaddy has live, working write access, connect once with a Personal Access Token and proposed fixes can be applied directly. Cloudflare has real client code built against its published API but isn't yet verified against a live account, so it stays scan-only for now. See the Integrations page for the exact status of every provider.
Logging and rollback
Every proposed, approved, or applied change is recorded with who made the decision (a person or domain-repair.com itself), what changed, and when. The change log on the dashboard is that record, not a marketing mockup. For an applied fix, the previous record value is retained so it can be restored, one click, no support ticket.
Sample, illustrates the applied/revert format
SPF has no explicit "all" mechanism at the end. Eligible for auto-apply once turned on for this domain.
The revert button above is real in your workspace