Hover does not sign zones on its own nameservers. For a domain on other nameservers it takes a DS record, whose values come from the DNS host that signs the zone.
| What it is | Registrar |
| DNSSEC | Partly |
| Signing | No — zones on Hover’s nameservers are not signed |
| DS record | Not applicable |
Is DNSSEC working for your domain?
Enter a domain: we read the DS record at its registry and the keys its nameservers publish, check that they match and the signatures are current, and ask a validating resolver.
The DS record
For a domain not on Hover’s nameservers: the domain’s Overview, DNSSEC, Add DS record:
- Key tag
- Algorithm
- Digest type
- Digest
Before moving the domain or its DNS
Hover’s help page says to turn signing off at the DNS host before removing the DS. The standard order, and every other provider’s, is the reverse: remove the DS first, wait out its TTL, then stop signing — turning signing off while a DS is still published is what makes validating resolvers fail.
Whose nameservers a domain uses: Hover’s.
Sources
Checked on 27 September 2026 against these official sources:
- Manage DNSSEC Records for Hover Domains — support.hover.com
- RFC 6781: DNSSEC Operational Practices, Version 2 — rfc-editor.org
- Disabling DNSSEC signing — docs.aws.amazon.com