View on GitHub

DNSViz: A DNS visualization tool

egbert.net

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

RRset statusRRset status

Bogus (5)
  • egbert.net/A (NODATA)
  • egbert.net/MX (NODATA)
  • egbert.net/NS
  • egbert.net/SOA
  • egbert.net/TXT (NODATA)
Secure (5)
  • egbert.net/A
  • egbert.net/MX
  • egbert.net/NS
  • egbert.net/SOA
  • egbert.net/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (13)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46594)
  • egbert.net/DNSKEY (alg 8, id 11770)
  • egbert.net/DNSKEY (alg 8, id 27955)
  • egbert.net/DNSKEY (alg 8, id 3330)
  • egbert.net/DNSKEY (alg 8, id 35199)
  • egbert.net/DS (alg 8, id 11770)
  • egbert.net/DS (alg 8, id 11770)
  • egbert.net/DS (alg 8, id 27955)
  • egbert.net/DS (alg 8, id 27955)
  • net/DNSKEY (alg 8, id 35886)
  • net/DNSKEY (alg 8, id 56519)
  • net/DS (alg 8, id 35886)

Delegation statusDelegation status

Secure (2)
  • . to net
  • net to egbert.net

NoticesNotices

Errors (24)
  • egbert.net zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (69.65.50.223, 2001:1850:1:5:800::6b)
  • egbert.net zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (69.65.50.223, 2001:1850:1:5:800::6b)
  • egbert.net/A (NODATA): 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. (216.66.1.2, 216.66.80.18, 216.218.130.2, 216.218.131.2, 216.218.132.2, 2001:470:100::2, 2001:470:200::2, 2001:470:300::2, 2001:470:400::2, 2001:470:500::2, UDP_-_EDNS0_4096_D_K)
  • egbert.net/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (69.65.50.223, 2001:1850:1:5:800::6b, UDP_-_NOEDNS_)
  • egbert.net/DNSKEY (alg 8, id 11770): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (216.66.1.2, 216.66.80.18, 216.218.130.2, 216.218.131.2, 216.218.132.2, 2001:470:100::2, 2001:470:200::2, 2001:470:300::2, 2001:470:400::2, 2001:470:500::2, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • egbert.net/DNSKEY (alg 8, id 27955): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (216.66.1.2, 216.66.80.18, 216.218.130.2, 216.218.131.2, 216.218.132.2, 2001:470:100::2, 2001:470:200::2, 2001:470:300::2, 2001:470:400::2, 2001:470:500::2, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • egbert.net/DNSKEY (alg 8, id 3330): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (216.66.1.2, 216.66.80.18, 216.218.130.2, 216.218.131.2, 216.218.132.2, 2001:470:100::2, 2001:470:200::2, 2001:470:300::2, 2001:470:400::2, 2001:470:500::2, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • egbert.net/DNSKEY (alg 8, id 35199): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (216.66.1.2, 216.66.80.18, 216.218.130.2, 216.218.131.2, 216.218.132.2, 2001:470:100::2, 2001:470:200::2, 2001:470:300::2, 2001:470:400::2, 2001:470:500::2, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • egbert.net/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (69.65.50.223, 2001:1850:1:5:800::6b, UDP_-_EDNS0_512_D_K, UDP_-_NOEDNS_)
  • egbert.net/MX (NODATA): 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. (216.66.1.2, 216.66.80.18, 216.218.130.2, 216.218.131.2, 216.218.132.2, 2001:470:100::2, 2001:470:200::2, 2001:470:300::2, 2001:470:400::2, 2001:470:500::2, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • egbert.net/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (69.65.50.223, 2001:1850:1:5:800::6b, UDP_-_EDNS0_512_D_K, UDP_-_NOEDNS_)
  • egbert.net/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (216.66.1.2, 216.66.80.18, 216.218.130.2, 216.218.131.2, 216.218.132.2, 2001:470:100::2, 2001:470:200::2, 2001:470:300::2, 2001:470:400::2, 2001:470:500::2, UDP_-_EDNS0_4096_D_K)
  • egbert.net/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (69.65.50.223, 2001:1850:1:5:800::6b, UDP_-_NOEDNS_)
  • egbert.net/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (216.66.1.2, 216.66.80.18, 216.218.130.2, 216.218.131.2, 216.218.132.2, 2001:470:100::2, 2001:470:200::2, 2001:470:300::2, 2001:470:400::2, 2001:470:500::2, UDP_-_EDNS0_4096_D_K)
  • egbert.net/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (69.65.50.223, 2001:1850:1:5:800::6b, TCP_-_NOEDNS_)
  • egbert.net/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (69.65.50.223, 2001:1850:1:5:800::6b, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • egbert.net/TXT (NODATA): 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. (216.66.1.2, 216.66.80.18, 216.218.130.2, 216.218.131.2, 216.218.132.2, 2001:470:100::2, 2001:470:200::2, 2001:470:300::2, 2001:470:400::2, 2001:470:500::2, UDP_-_EDNS0_4096_D_K)
  • egbert.net/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (69.65.50.223, 2001:1850:1:5:800::6b, UDP_-_NOEDNS_)
  • net to egbert.net: 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. (216.66.1.2, 216.66.80.18, 216.218.130.2, 216.218.131.2, 216.218.132.2, 2001:470:100::2, 2001:470:200::2, 2001:470:300::2, 2001:470:400::2, 2001:470:500::2, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • net to egbert.net: 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. (216.66.1.2, 216.66.80.18, 216.218.130.2, 216.218.131.2, 216.218.132.2, 2001:470:100::2, 2001:470:200::2, 2001:470:300::2, 2001:470:400::2, 2001:470:500::2, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • oi5ajhx6zs.egbert.net/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • egbert.net/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • egbert.net/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • egbert.net/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
  • egbert.net/DS (alg 8, id 11770): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • egbert.net/DS (alg 8, id 11770): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • egbert.net/DS (alg 8, id 11770): 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.
  • egbert.net/DS (alg 8, id 11770): 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.
  • egbert.net/DS (alg 8, id 27955): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • egbert.net/DS (alg 8, id 27955): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • egbert.net/DS (alg 8, id 27955): 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.
  • egbert.net/DS (alg 8, id 27955): 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.
  • net to egbert.net: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the net zone): ns3.he.net, ns4.he.net, ns5.he.net, ns1.he.net, ns2.he.net See RFC 1034, Sec. 4.2.2.
  • net to egbert.net: The following NS name(s) were found in the delegation NS RRset (i.e., in the net zone), but not in the authoritative NS RRset: ns2.afraid.org See RFC 1034, Sec. 4.2.2.

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