_acme-challenge.fw-1b.fast.za.net
Updated:
2024-10-04 12:16:27 UTC (231 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (4)
- _acme-challenge.fw-1b.fast.za.net/A (NODATA)
- _acme-challenge.fw-1b.fast.za.net/AAAA (NODATA)
- fast.za.net/SOA
- za.net/SOA
Secure (2)
- net/SOA
- net/SOA
DNSKEY/DS/NSEC status
Insecure (6)
- NSEC3 proving non-existence of _acme-challenge.fw-1b.fast.za.net/A
- NSEC3 proving non-existence of _acme-challenge.fw-1b.fast.za.net/AAAA
- fast.za.net/DNSKEY (alg 13, id 19923)
- fast.za.net/DNSKEY (alg 13, id 39039)
- fast.za.net/DNSKEY (alg 8, id 2103)
- fast.za.net/DNSKEY (alg 8, id 41471)
Secure (7)
- ./DNSKEY (alg 8, id 20038)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 61050)
- NSEC3 proving non-existence of za.net/DS
- net/DNSKEY (alg 13, id 37331)
- net/DNSKEY (alg 13, id 42924)
- net/DS (alg 13, id 37331)
Delegation status
Insecure (2)
- net to za.net
- za.net to fast.za.net
Secure (1)
- . to net
Notices
Errors (6)
- NSEC3 proving non-existence of _acme-challenge.fw-1b.fast.za.net/A: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of _acme-challenge.fw-1b.fast.za.net/A: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of _acme-challenge.fw-1b.fast.za.net/AAAA: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of _acme-challenge.fw-1b.fast.za.net/AAAA: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- za.net zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2c0e:2001:4000:1::c419:101)
- fast.za.net/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
