nkn.in
Updated:
2023-01-15 08:11:09 UTC (623 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- nkn.in/A
- nkn.in/MX
- nkn.in/NS
- nkn.in/NS
- nkn.in/SOA
- nkn.in/TXT
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 951)
- in/DNSKEY (alg 8, id 54739)
- in/DNSKEY (alg 8, id 65169)
- in/DS (alg 8, id 54739)
- 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 status
Secure (2)
- . to in
- in to nkn.in
Notices
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 (21)
- 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.
- in/DS (alg 8, id 54739): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- in/DS (alg 8, id 54739): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- in/DS (alg 8, id 54739): 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.
- in/DS (alg 8, id 54739): 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.
- 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.
- dfhst0768v.nkn.in/A 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.
- nkn.in/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
