A fatal issue occurred during the DNS lookup process for dnssec-failed.org/A.
DNS response for dnssec-failed.org had fatal DNSSEC issues: validation failure <dnssec-failed.org. A IN>: no keys have a DS with algorithm RSASHA1 from 2001:558:1014:c:68:87:76:228 for key dnssec-failed.org. while building chain of trust. Additionally, Cloudflare's 1.1.1.1 resolver reported: no SEP matching the DS found for dnssec-failed.org.
A fatal issue occurred during the DNS lookup process for dnssec-failed.org/AAAA.
DNS response for dnssec-failed.org had fatal DNSSEC issues: validation failure <dnssec-failed.org. AAAA IN>: no keys have a DS with algorithm RSASHA1 from 2001:558:100e:5:68:87:72:244 for key dnssec-failed.org. while building chain of trust. Additionally, Cloudflare's 1.1.1.1 resolver reported: no SEP matching the DS found for dnssec-failed.org.
A fatal issue occurred during the DNS lookup process for dnssec-failed.org/CAA.
DNS response for dnssec-failed.org had fatal DNSSEC issues: validation failure <dnssec-failed.org. CAA IN>: no keys have a DS with algorithm RSASHA1 from 2001:558:100e:5:68:87:72:244 for key dnssec-failed.org. while building chain of trust. Additionally, Cloudflare's 1.1.1.1 resolver reported: no SEP matching the DS found for dnssec-failed.org.
No valid A or AAAA records could be ultimately resolved for dnssec-failed.org. This means that Let's Encrypt would not be able to connect to your domain to perform HTTP validation, since it would not know where to connect to.
No A or AAAA records found.