You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For research purposes it would be nice to see when a domain fails for DNSSEC, but does provide DNSSEC signatures and has a DNSKEY.
Forged example (via direct URL entry, since the domain does not provide an A-record so doesn't pass the initial qualification to be checked) is randstad380kv-noordring.nl, see the current test report which obviously fails because of a missing DS-record:
For research purposes it would be nice to see when a domain fails for DNSSEC, but does provide DNSSEC signatures and has a DNSKEY.
Forged example (via direct URL entry, since the domain does not provide an A-record so doesn't pass the initial qualification to be checked) is randstad380kv-noordring.nl, see the current test report which obviously fails because of a missing DS-record:
It would be nice to know it's failing because the DS records are not set up.
Other linked relevant issues that could bring more DNSSEC info to the API: #188, #976 and #978.
The text was updated successfully, but these errors were encountered: