View on GitHub

DNSViz: A DNS visualization tool

hoevelmann.ag

« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Bogus (6)
  • ag/SOA
  • hoevelmann.ag/A
  • hoevelmann.ag/AAAA
  • hoevelmann.ag/MX
  • hoevelmann.ag/NS
  • hoevelmann.ag/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (1)
  • NSEC3 proving non-existence of hoevelmann.ag/DS
Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26116)
  • ag/DNSKEY (alg 7, id 24316)
  • ag/DNSKEY (alg 7, id 58865)
  • 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 statusDelegation status

Insecure (1)
  • ag to hoevelmann.ag
Secure (1)
  • . to ag

NoticesNotices

Errors (12)
  • . to ag: 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. (199.249.124.1, 2001:500:44::1, UDP_-_EDNS0_4096_D_K)
  • . to ag: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no DS RR matched a DNSKEY with algorithm 7 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (199.249.124.1, 2001:500:44::1, UDP_-_EDNS0_4096_D_K)
  • 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.
  • NSEC3 proving non-existence of hoevelmann.ag/DS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.254.59.1, 199.254.60.1, 199.254.61.1, 199.254.62.1, 2001:500:25::1, 2001:500:26::1, 2001:500:27::1, 2001:500:28::1, 2001:500:4c::1, UDP_-_EDNS0_4096_D_K)
  • NSEC3 proving non-existence of hoevelmann.ag/DS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.254.59.1, 199.254.60.1, 199.254.61.1, 199.254.62.1, 2001:500:25::1, 2001:500:26::1, 2001:500:27::1, 2001:500:28::1, 2001:500:4c::1, UDP_-_EDNS0_4096_D_K)
  • ag to hoevelmann.ag: No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (199.249.116.1, 199.249.124.1, 2001:500:44::1, UDP_-_EDNS0_4096_D_K)
  • ag/DNSKEY (alg 7, id 24316): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.249.124.1, 2001:500:44::1, UDP_-_EDNS0_4096_D_K)
  • ag/DNSKEY (alg 7, id 58865): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.249.124.1, 2001:500:44::1, UDP_-_EDNS0_4096_D_K)
  • ag/DNSKEY (alg 7, id 65384): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.249.124.1, 2001:500:44::1, UDP_-_EDNS0_4096_D_K)
  • ag/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (199.249.116.1, 199.249.124.1, 199.254.59.1, 199.254.60.1, 199.254.61.1, 199.254.62.1, 2001:500:25::1, 2001:500:26::1, 2001:500:27::1, 2001:500:28::1, 2001:500:44::1, 2001:500:4c::1, UDP_-_EDNS0_4096_D_K)
  • hoevelmann.ag/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (11)
  • 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 58865: 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.
  • 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.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph