# domain.created / domain.updated / domain.deleted: your sending identity changed
These events fire when a domain was successfully created, updated, or deleted in Resend.
## What to do on receipt
1. On `domain.created`: the domain is not ready to send yet. Complete DNS verification (SPF, DKIM, and DMARC records) in the Resend dashboard before any production traffic uses it. Sending from an unverified domain produces `email.failed` events.
2. On `domain.updated`: re-check verification status. Configuration changes can invalidate DNS records; confirm the domain still verifies before trusting it.
3. On `domain.deleted`: stop using it immediately. Move templates, scheduled sends, and default from-addresses to a live domain. Anything still addressed from the deleted domain will fail.
4. Log all three for audit: domain changes are security-relevant (a new sending domain can be abused for phishing from your account).
## The trap
Creating a domain and sending right away. Verification takes DNS propagation time, and unverified sends fail loudly. The other trap is stale references: templates and code that hardcode a from-address on a domain someone deleted in the dashboard.