View on GitHub

DNSViz: A DNS visualization tool

nkn.in

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

RRset statusRRset status

Secure (6)
  • nkn.in/A
  • nkn.in/MX
  • nkn.in/NS
  • nkn.in/NS
  • nkn.in/SOA
  • nkn.in/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • in/DNSKEY (alg 8, id 54739)
  • in/DNSKEY (alg 8, id 65169)
  • in/DS (alg 8, id 54739)
  • nkn.in/DNSKEY (alg 5, id 27817)
  • nkn.in/DNSKEY (alg 5, id 44460)
  • nkn.in/DS (alg 5, id 27817)

Delegation statusDelegation status

Secure (2)
  • . to in
  • in to nkn.in

NoticesNotices

Errors (3)
  • nkn.in zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2405:8a00:aa::aa)
  • nkn.in/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2405:8a00:aa::aa, UDP_-_NOEDNS_)
  • nkn.in/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2405:8a00:aa::aa, UDP_-_NOEDNS_)
Warnings (17)
  • RRSIG nkn.in/A alg 5, id 44460: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nkn.in/DNSKEY alg 5, id 27817: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nkn.in/DNSKEY alg 5, id 27817: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nkn.in/DNSKEY alg 5, id 44460: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nkn.in/DNSKEY alg 5, id 44460: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nkn.in/MX alg 5, id 44460: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nkn.in/NS alg 5, id 44460: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nkn.in/NS alg 5, id 44460: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nkn.in/SOA alg 5, id 44460: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG nkn.in/TXT alg 5, id 44460: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • nkn.in/DS (alg 5, id 27817): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • nkn.in/DS (alg 5, id 27817): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • nkn.in/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
  • nkn.in/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • l3ravgn0d4.nkn.in/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • nkn.in/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • nkn.in/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