---
title: domain.restored
seo:
  title: Handle the domain.restored webhook event
description: "domain.restored fires when a domain's missing DKIM record has been back in DNS for an hour before the domain was lost. The domain signs as before."
sidebar:
  label: domain.restored
  icon: globe
---

A domain's missing DKIM record has been back in DNS for an hour before the domain was lost. It signs as before, and `dkim_missing_since` and `stops_sending_at` on the domain are null again.

One check that finds the record is not enough: it is rechecked every 15 minutes once it is back, and the event fires when every check for an hour has found it. A check that misses it in that hour starts the hour again, and `stops_sending_at` stays where it was.

The event is sent for the domain that holds the records. A wildcard's subdomains get no `domain.restored` of their own.

## Payload

Every field, with an example body, is in the [`domain.restored` reference](/api/endpoints/webhook-events/domain-restored), generated from the API contract.

## Handling it

Clear whatever warning [`domain.at_risk`](/webhooks/events/domain-at-risk) put up. The domain kept sending the whole time, so there is nothing to resume.

**[Domains](/guides/domains#staying-verified)**

Background rechecks, and what happens during the 72 hours.