← Back to Cloudflare History
minor✓ Resolved

Resolution Issues for .de Domains

Cloudflare•Tue, May 5, 2026, 09:17 PM
Status
resolved
Duration
17h 52m
Updates
7
Coverage
0 articles

INCIDENT TIMELINE

✓ ResolvedWed, May 6, 2026, 03:10 PM
This incident has been resolved.
monitoringWed, May 6, 2026, 12:40 PM
We have removed our mitigations and we are monitoring the results.
monitoringTue, May 5, 2026, 10:37 PM
The issue has been identified as a DNSSEC signing problem at DENIC, the organization responsible for the .DE top-level domain. Cloudflare has temporarily disabled DNSSEC validation for .de domains on 1.1.1.1 resolver (as per RFC 7646) in order to allow .DE names to continue to resolve. DNSSEC validation will be re-enabled when the signing problems at DENIC are known to have been resolved. See RFC 7646 for more details: https://datatracker.ietf.org/doc/html/rfc7646
identifiedTue, May 5, 2026, 10:14 PM
We are continuing to work on a fix for this issue.
identifiedTue, May 5, 2026, 10:07 PM
We are continuing to work on a fix for this issue.
identifiedTue, May 5, 2026, 10:01 PM
The issue has been identified as a DNSSEC signing problem at DENIC, the organization responsible for the .DE top-level domain. Cloudflare is temporarily disabling DNSSEC validation for .de domains on 1.1.1.1 resolver (as per RFC 7646) in order to allow .DE names to continue to resolve. DNSSEC validation will be re-enabled when the signing problems at DENIC are known to have been resolved. See RFC 7646 for more details: https://datatracker.ietf.org/doc/html/rfc7646
identifiedTue, May 5, 2026, 09:20 PM
The issue has been identified and a fix is being implemented.
investigatingTue, May 5, 2026, 09:17 PM
We are observing issues with authoritative resolution for the .de TLD.

📊 TECHNICAL DETAILS

Internal ID
eaacecfb-d252-4c05-85a4-3ac23832738c
External ID
vjrk8c8w37lz
🕐 Started
Tue, May 5, 2026, 09:17 PM
🔄 Last Updated
Wed, May 6, 2026, 03:10 PM
✓ Resolved
Wed, May 6, 2026, 03:10 PM
MINOR
Impact Level
17h 52m
Total Duration
7
Status Updates
Affected Components
Recursive DNS
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed