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

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 (16)
  • 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 zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (216.218.133.2, 2001:470:600::2)
  • egbert.net/A: The UDP connection was refused (ECONNREFUSED). See RFC 1035, Sec. 4.2. (216.218.133.2, 2001:470:600::2, UDP_-_EDNS0_4096_D_K)
  • egbert.net/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (69.65.50.223, 2001:1850:1:5:800::6b, UDP_-_EDNS0_4096_D_K)
  • egbert.net/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (69.65.50.223, 2001:1850:1:5:800::6b, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • egbert.net/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (69.65.50.223, 2001:1850:1:5:800::6b, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • egbert.net/NS: The UDP connection was refused (ECONNREFUSED). See RFC 1035, Sec. 4.2. (216.218.133.2, 2001:470:600::2, UDP_-_EDNS0_4096_D_K)
  • egbert.net/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (69.65.50.223, 2001:1850:1:5:800::6b, UDP_-_EDNS0_4096_D_K)
  • egbert.net/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (69.65.50.223, 2001:1850:1:5:800::6b, TCP_-_EDNS0_4096_D)
  • egbert.net/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (69.65.50.223, 2001:1850:1:5:800::6b, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • egbert.net/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (69.65.50.223, 2001:1850:1:5:800::6b, UDP_-_EDNS0_4096_D_K)
  • lk9bxp5i8u.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): slave.dns.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