View on GitHub

DNSViz: A DNS visualization tool

sflug.org

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

RRset statusRRset status

Secure (5)
  • sflug.org/A
  • sflug.org/AAAA
  • sflug.org/NS
  • sflug.org/SOA
  • sflug.org/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 48903)
  • org/DNSKEY (alg 7, id 17883)
  • org/DNSKEY (alg 7, id 27074)
  • org/DNSKEY (alg 7, id 37022)
  • org/DS (alg 7, id 17883)
  • org/DS (alg 7, id 17883)
  • org/DS (alg 7, id 9795)
  • sflug.org/DNSKEY (alg 8, id 36426)
  • sflug.org/DNSKEY (alg 8, id 55585)
  • sflug.org/DS (alg 8, id 55585)
  • sflug.org/DS (alg 8, id 55585)
Non_existent (1)
  • org/DNSKEY (alg 7, id 9795)

Delegation statusDelegation status

Secure (2)
  • . to org
  • org to sflug.org

NoticesNotices

Errors (6)
  • sflug.org zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (198.144.194.238)
  • sflug.org/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (198.144.194.238, UDP_-_NOEDNS_)
  • sflug.org/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (198.144.194.238, UDP_-_NOEDNS_)
  • sflug.org/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • wnzal0vh34.sflug.org/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • sflug.org/MX has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (26)
  • RRSIG org/DNSKEY alg 7, id 17883: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 17883: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 17883: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 37022: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 37022: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG org/DNSKEY alg 7, id 37022: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sflug.org/DS alg 7, id 37022: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG sflug.org/DS alg 7, id 37022: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • org to sflug.org: The glue address(es) for ns1.sf-lug.org (198.144.194.238) differed from its authoritative address(es) (96.86.170.229). See RFC 1034, Sec. 4.2.2.
  • org to sflug.org: The glue address(es) for ns1.sf-lug.org (2001:470:1f04:19e::2) differed from its authoritative address(es) (2001:470:1f05:19e::3). See RFC 1034, Sec. 4.2.2.
  • org/DS (alg 7, id 17883): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • org/DS (alg 7, id 17883): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • org/DS (alg 7, id 17883): 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.
  • org/DS (alg 7, id 17883): 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.
  • org/DS (alg 7, id 9795): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • org/DS (alg 7, id 9795): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • org/DS (alg 7, id 9795): 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.
  • org/DS (alg 7, id 9795): 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.
  • sflug.org/DS (alg 8, id 55585): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • sflug.org/DS (alg 8, id 55585): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • sflug.org/DS (alg 8, id 55585): 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.
  • sflug.org/DS (alg 8, id 55585): 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.
  • sflug.org/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • sflug.org/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • wnzal0vh34.sflug.org/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • sflug.org/MX 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