View on GitHub

DNSViz: A DNS visualization tool

4gjn.com

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

RRset statusRRset status

Secure (6)
  • 4gjn.com/A
  • 4gjn.com/AAAA
  • 4gjn.com/MX
  • 4gjn.com/NS
  • 4gjn.com/SOA
  • 4gjn.com/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (9)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 42351)
  • 4gjn.com/DNSKEY (alg 10, id 39996)
  • 4gjn.com/DNSKEY (alg 10, id 50030)
  • 4gjn.com/DS (alg 10, id 39996)
  • 4gjn.com/DS (alg 10, id 39996)
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 58540)
  • com/DS (alg 8, id 30909)

Delegation statusDelegation status

Secure (2)
  • . to com
  • com to 4gjn.com

NoticesNotices

Warnings (17)
  • 4gjn.com/DS (alg 10, id 39996): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • 4gjn.com/DS (alg 10, id 39996): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • 4gjn.com/DS (alg 10, id 39996): 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.
  • 4gjn.com/DS (alg 10, id 39996): 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.
  • RRSIG 4gjn.com/A alg 10, id 50030: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG 4gjn.com/AAAA alg 10, id 50030: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG 4gjn.com/DNSKEY alg 10, id 39996: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG 4gjn.com/DNSKEY alg 10, id 39996: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG 4gjn.com/DNSKEY alg 10, id 50030: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG 4gjn.com/DNSKEY alg 10, id 50030: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG 4gjn.com/MX alg 10, id 50030: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG 4gjn.com/NS alg 10, id 50030: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG 4gjn.com/SOA alg 10, id 50030: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG 4gjn.com/TXT alg 10, id 50030: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • 4gjn.com/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 2ejub7so0c.4gjn.com/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 4gjn.com/CNAME 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