balug.org
Updated:
2024-09-30 02:42:42 UTC (54 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (9)
- balug.org/A
- balug.org/AAAA
- balug.org/CDNSKEY
- balug.org/CDS
- balug.org/MX
- balug.org/NS
- balug.org/NSEC3PARAM
- balug.org/SOA
- balug.org/TXT
DNSKEY/DS/NSEC status
Bogus (3)
- balug.org/DNSKEY (alg 8, id 17095)
- balug.org/DNSKEY (alg 8, id 46252)
- balug.org/DNSKEY (alg 8, id 47448)
Secure (8)
- ./DNSKEY (alg 8, id 20038)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 61050)
- balug.org/DS (alg 8, id 17095)
- org/DNSKEY (alg 8, id 15678)
- org/DNSKEY (alg 8, id 23064)
- org/DNSKEY (alg 8, id 26974)
- org/DS (alg 8, id 26974)
Delegation status
Bogus (1)
- org to balug.org
Secure (1)
- . to org
Notices
Errors (8)
- balug.org/CDNSKEY: No valid RRSIGs made by a key corresponding to a CDNSKEY RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11, RFC 7344, Sec. 3, RFC 7344, Sec. 5. (50.18.139.240, 50.242.105.52, 96.86.170.229, 96.95.217.99, 2001:470:1f05:19e::2, 2600:1f1c:528:c500:5e0b:8a37:6598:356c, 2603:3024:180d:f100:50:242:105:34, UDP_-_EDNS0_4096_D_KN)
- balug.org/CDNSKEY: The CDNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no CDNSKEY RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11, RFC 7344, Sec. 3, RFC 7344, Sec. 5. (50.18.139.240, 50.242.105.52, 96.86.170.229, 96.95.217.99, 2001:470:1f05:19e::2, 2600:1f1c:528:c500:5e0b:8a37:6598:356c, 2603:3024:180d:f100:50:242:105:34, UDP_-_EDNS0_4096_D_KN)
- balug.org/CDNSKEY: The CDNSKEY RRset must be signed with a key that is represented in both the current DNSKEY and the current DS RRset. See RFC 7344, Sec. 4.1.
- balug.org/CDS: No valid RRSIGs made by a key corresponding to a CDS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11, RFC 7344, Sec. 3, RFC 7344, Sec. 5. (50.18.139.240, 50.242.105.52, 96.86.170.229, 96.95.217.99, 2001:470:1f05:19e::2, 2600:1f1c:528:c500:5e0b:8a37:6598:356c, 2603:3024:180d:f100:50:242:105:34, UDP_-_EDNS0_4096_D_KN)
- balug.org/CDS: The CDS RRset for the zone included algorithm 8 (RSASHA256), but no CDS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11, RFC 7344, Sec. 3, RFC 7344, Sec. 5. (50.18.139.240, 50.242.105.52, 96.86.170.229, 96.95.217.99, 2001:470:1f05:19e::2, 2600:1f1c:528:c500:5e0b:8a37:6598:356c, 2603:3024:180d:f100:50:242:105:34, UDP_-_EDNS0_4096_D_KN)
- balug.org/CDS: The CDS RRset must be signed with a key that is represented in both the current DNSKEY and the current DS RRset. See RFC 7344, Sec. 4.1.
- org to balug.org: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (50.18.139.240, 50.242.105.52, 96.86.170.229, 96.95.217.99, 2001:470:1f05:19e::2, 2600:1f1c:528:c500:5e0b:8a37:6598:356c, 2603:3024:180d:f100:50:242:105:34, UDP_-_EDNS0_4096_D_KN)
- org to balug.org: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (50.18.139.240, 50.242.105.52, 96.86.170.229, 96.95.217.99, 2001:470:1f05:19e::2, 2600:1f1c:528:c500:5e0b:8a37:6598:356c, 2603:3024:180d:f100:50:242:105:34, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
