hoevelmann.ag
Updated:
2020-11-30 18:56:59 UTC (1482 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- hoevelmann.ag/A
- hoevelmann.ag/AAAA
- hoevelmann.ag/MX
- hoevelmann.ag/NS
- hoevelmann.ag/SOA
Secure (1)
- ag/SOA
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26116)
- NSEC3 proving non-existence of hoevelmann.ag/DS
- ag/DNSKEY (alg 7, id 24316)
- ag/DNSKEY (alg 7, id 58865)
- ag/DNSKEY (alg 7, id 62820)
- ag/DNSKEY (alg 7, id 65384)
- ag/DS (alg 7, id 24316)
- ag/DS (alg 7, id 55656)
Non_existent (1)
- ag/DNSKEY (alg 7, id 55656)
Delegation status
Insecure (1)
- ag to hoevelmann.ag
Secure (1)
- . to ag
Notices
Errors (3)
- NSEC3 proving non-existence of hoevelmann.ag/DS: 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 hoevelmann.ag/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- hoevelmann.ag/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (18)
- NSEC3 proving non-existence of hoevelmann.ag/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of hoevelmann.ag/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- RRSIG NSEC3 proving non-existence of hoevelmann.ag/DS alg 7, id 65384: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG NSEC3 proving non-existence of hoevelmann.ag/DS alg 7, id 65384: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG ag/DNSKEY alg 7, id 24316: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG ag/DNSKEY alg 7, id 24316: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG ag/DNSKEY alg 7, id 24316: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG ag/DNSKEY alg 7, id 24316: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG ag/DNSKEY alg 7, id 62820: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG ag/DNSKEY alg 7, id 62820: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG ag/DNSKEY alg 7, id 62820: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG ag/DNSKEY alg 7, id 62820: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG ag/SOA alg 7, id 65384: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- ag/DS (alg 7, id 55656): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ag/DS (alg 7, id 55656): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- ag/DS (alg 7, id 55656): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- ag/DS (alg 7, id 55656): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- hoevelmann.ag/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
