Verifying Domain Ownership
How DNS TXT verification works and why reports stay locked until it passes.
Updated
Adding a domain to SpoofKiller takes a name and a click. Seeing that domain’s reports takes proof that it is yours. This page explains the proof, which is a single DNS TXT record, and what to check when it is not found. It is step four of Getting Started.
Why verification exists
DMARC aggregate reports describe who sends mail as a domain (what they contain is covered in the knowledge base), from which servers, in what volume, and how much of it authenticates. That is a fair map of a company’s email vendors and habits. If typing a domain name were enough to see it, anybody could add a competitor’s domain, or a target’s, and read along.
So the rule is simple: nobody sees a domain’s report data by merely adding its name. An organization must first show that it controls the domain’s DNS, which is the same control needed to publish a DMARC record in the first place. Reports that arrive for an unverified domain are not accepted.
The record
When you add a domain, SpoofKiller generates a random token for it. The verification record is:
| Field | Value |
|---|---|
| Type | TXT |
| Host / Name | _verification (full name _verification.example.com) |
| Value | spoofkiller-verification=<token> |
| TTL | Your provider’s default is fine |
The token is 40 lowercase letters and digits and is unique to the domain within your organization. Copy the whole value from the domain’s setup page (it is also in the email sent when the domain was added) rather than retyping it. For a subdomain such as mail.example.com, the full record name is _verification.mail.example.com, so in the example.com zone the host is _verification.mail.
When you press Verify, SpoofKiller looks up the TXT records at that name and compares each one with the expected value. The match is exact, apart from surrounding whitespace. Other TXT records at the same name are ignored, so the record can coexist with anything else.
Steps
- Open the domain’s setup page and copy the host and the value.
- At your DNS provider, add a TXT record with that host and value.
- Give it a few minutes, then confirm that the record is visible with the DNS propagation checker or a command-line lookup:
dig +short TXT _verification.example.com "spoofkiller-verification=k3v9…" - Press Verify. On success the page reports that the domain is verified and that monitoring has started.
Common mistakes
When verification fails, the message says which of three things happened. Each has its usual causes.
| Message | Likely cause | Fix |
|---|---|---|
| No TXT record found at the name yet | Doubled domain. You entered _verification.example.com in a host field that appends the domain, producing _verification.example.com.example.com. | Enter only _verification. If your provider wants a fully qualified name, use _verification.example.com (some want a trailing dot). |
| No TXT record found at the name yet | Propagation. The record was saved but is not yet served by your nameservers, or the record was added in a zone that is not the live one for the domain. | Wait a few minutes and try again. If it never appears, check that the nameservers you edited are the ones the domain is delegated to. |
| A verification record exists but its value does not match | Quotes or truncation. You typed quotation marks into a field that adds its own, so the published value contains literal quotes; or part of the token was cut off; or the token is from another domain or organization. | Paste the value exactly as shown, without adding quotes, and compare the published value character by character. |
| The DNS lookup failed | The lookup itself returned an error, for example because DNSSEC validation is failing for the zone or the nameservers did not answer. | Try again in a moment. If it persists, run the DNS security checker on the domain. |
Two smaller ones: the record must be of type TXT, not CNAME; and it belongs at _verification, not at _dmarc and not at the root of the domain. Verification attempts are limited to twenty per domain per hour, which is more patience than DNS usually requires.
What stays locked until the domain is verified
| Before verification | After verification |
|---|---|
| The initial DNS scan, its findings, and a Protection Score based on DNS alone | Scheduled DNS scans every six hours, compared against a stored baseline so that record changes are detected |
| Manual re-scans | The domain’s unique reporting address, and acceptance of reports sent or uploaded for it |
| The setup page with the verification record | DMARC analytics, sending sources, and the report archive |
| Nothing derived from reports | Findings and alerts for the domain, including report-based detection |
| No scheduled checks | Daily blacklist, lookalike-domain, and domain-expiration checks, where the plan includes them |
| No exports | Report exports, scheduled reports, and the report-derived API endpoints |
The pre-verification scan reads only public DNS
Verification happens once
A verified domain stays verified. SpoofKiller does not re-check the TXT record on a schedule, and you may remove the record afterward. Pausing and resuming monitoring does not require verifying again. Removing a domain from the organization and adding it back does: the new entry gets a new token.
Verification is also per organization. If the same domain is added to two organizations, each has its own token and each must publish its own record. This is deliberate: a second party does not inherit access because a first one proved ownership. The same holds for an agency’s client workspaces, each of which verifies its own domains.
