View on GitHub

DNSViz: A DNS visualization tool

registry.in

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

RRset statusRRset status

Insecure (6)
  • registry.in/A
  • registry.in/AAAA
  • registry.in/MX
  • registry.in/NS
  • registry.in/SOA
  • registry.in/TXT
Secure (2)
  • in/SOA
  • in/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (14)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 33853)
  • ./DNSKEY (alg 8, id 48903)
  • NSEC3 proving non-existence of registry.in/DS
  • in/DNSKEY (alg 7, id 35373)
  • in/DNSKEY (alg 7, id 49359)
  • in/DNSKEY (alg 7, id 51365)
  • in/DNSKEY (alg 7, id 9182)
  • in/DNSKEY (alg 8, id 54739)
  • in/DNSKEY (alg 8, id 65169)
  • in/DS (alg 7, id 35373)
  • in/DS (alg 7, id 35373)
  • in/DS (alg 8, id 54739)
  • in/DS (alg 8, id 54739)

Delegation statusDelegation status

Insecure (1)
  • in to registry.in
Secure (1)
  • . to in

NoticesNotices

Errors (24)
  • . to in: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (37.209.192.12, 37.209.194.12, 37.209.196.12, 37.209.198.12, 156.154.100.20, 156.154.101.20, 2001:502:2eda::20, 2001:502:ad09::20, 2001:dcd:1::12, 2001:dcd:2::12, 2001:dcd:3::12, 2001:dcd:4::12, UDP_-_EDNS0_4096_D_K)
  • NSEC3 proving non-existence of registry.in/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of registry.in/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of registry.in/DS: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (37.209.192.12, 37.209.194.12, 37.209.196.12, 37.209.198.12, 156.154.100.20, 156.154.101.20, 2001:502:2eda::20, 2001:502:ad09::20, 2001:dcd:1::12, 2001:dcd:2::12, 2001:dcd:3::12, 2001:dcd:4::12, UDP_-_EDNS0_4096_D_K)
  • NSEC3 proving non-existence of registry.in/DS: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (37.209.192.12, 37.209.194.12, 37.209.196.12, 37.209.198.12, 156.154.100.20, 156.154.101.20, 2001:502:2eda::20, 2001:502:ad09::20, 2001:dcd:1::12, 2001:dcd:2::12, 2001:dcd:3::12, 2001:dcd:4::12, UDP_-_EDNS0_4096_D_K)
  • NSEC3 proving non-existence of registry.in/DS: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (37.209.192.12, 37.209.194.12, 37.209.196.12, 37.209.198.12, 156.154.100.20, 156.154.101.20, 2001:502:2eda::20, 2001:502:ad09::20, 2001:dcd:1::12, 2001:dcd:2::12, 2001:dcd:3::12, 2001:dcd:4::12, UDP_-_EDNS0_4096_D_K)
  • NSEC3 proving non-existence of registry.in/DS: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (37.209.192.12, 37.209.194.12, 37.209.196.12, 37.209.198.12, 156.154.100.20, 156.154.101.20, 2001:502:2eda::20, 2001:502:ad09::20, 2001:dcd:1::12, 2001:dcd:2::12, 2001:dcd:3::12, 2001:dcd:4::12, UDP_-_EDNS0_4096_D_K)
  • in/DNSKEY (alg 7, id 35373): The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (37.209.192.12, 37.209.194.12, 37.209.196.12, 37.209.198.12, 156.154.100.20, 156.154.101.20, 2001:502:2eda::20, 2001:502:ad09::20, 2001:dcd:1::12, 2001:dcd:2::12, 2001:dcd:3::12, 2001:dcd:4::12, UDP_-_EDNS0_4096_D_K)
  • in/DNSKEY (alg 7, id 35373): The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (37.209.192.12, 37.209.194.12, 37.209.196.12, 37.209.198.12, 156.154.100.20, 156.154.101.20, 2001:502:2eda::20, 2001:502:ad09::20, 2001:dcd:1::12, 2001:dcd:2::12, 2001:dcd:3::12, 2001:dcd:4::12, UDP_-_EDNS0_4096_D_K)
  • in/DNSKEY (alg 7, id 49359): The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (37.209.192.12, 37.209.194.12, 37.209.196.12, 37.209.198.12, 156.154.100.20, 156.154.101.20, 2001:502:2eda::20, 2001:502:ad09::20, 2001:dcd:1::12, 2001:dcd:2::12, 2001:dcd:3::12, 2001:dcd:4::12, UDP_-_EDNS0_4096_D_K)
  • in/DNSKEY (alg 7, id 49359): The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (37.209.192.12, 37.209.194.12, 37.209.196.12, 37.209.198.12, 156.154.100.20, 156.154.101.20, 2001:502:2eda::20, 2001:502:ad09::20, 2001:dcd:1::12, 2001:dcd:2::12, 2001:dcd:3::12, 2001:dcd:4::12, UDP_-_EDNS0_4096_D_K)
  • in/DNSKEY (alg 7, id 51365): The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (37.209.192.12, 37.209.194.12, 37.209.196.12, 37.209.198.12, 156.154.100.20, 156.154.101.20, 2001:502:2eda::20, 2001:502:ad09::20, 2001:dcd:1::12, 2001:dcd:2::12, 2001:dcd:3::12, 2001:dcd:4::12, UDP_-_EDNS0_4096_D_K)
  • in/DNSKEY (alg 7, id 51365): The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (37.209.192.12, 37.209.194.12, 37.209.196.12, 37.209.198.12, 156.154.100.20, 156.154.101.20, 2001:502:2eda::20, 2001:502:ad09::20, 2001:dcd:1::12, 2001:dcd:2::12, 2001:dcd:3::12, 2001:dcd:4::12, UDP_-_EDNS0_4096_D_K)
  • in/DNSKEY (alg 7, id 9182): The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (37.209.192.12, 37.209.194.12, 37.209.196.12, 37.209.198.12, 156.154.100.20, 156.154.101.20, 2001:502:2eda::20, 2001:502:ad09::20, 2001:dcd:1::12, 2001:dcd:2::12, 2001:dcd:3::12, 2001:dcd:4::12, UDP_-_EDNS0_4096_D_K)
  • in/DNSKEY (alg 7, id 9182): The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (37.209.192.12, 37.209.194.12, 37.209.196.12, 37.209.198.12, 156.154.100.20, 156.154.101.20, 2001:502:2eda::20, 2001:502:ad09::20, 2001:dcd:1::12, 2001:dcd:2::12, 2001:dcd:3::12, 2001:dcd:4::12, UDP_-_EDNS0_4096_D_K)
  • in/DNSKEY (alg 8, id 54739): The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (37.209.192.12, 37.209.194.12, 37.209.196.12, 37.209.198.12, 156.154.100.20, 156.154.101.20, 2001:502:2eda::20, 2001:502:ad09::20, 2001:dcd:1::12, 2001:dcd:2::12, 2001:dcd:3::12, 2001:dcd:4::12, UDP_-_EDNS0_4096_D_K)
  • in/DNSKEY (alg 8, id 54739): The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (37.209.192.12, 37.209.194.12, 37.209.196.12, 37.209.198.12, 156.154.100.20, 156.154.101.20, 2001:502:2eda::20, 2001:502:ad09::20, 2001:dcd:1::12, 2001:dcd:2::12, 2001:dcd:3::12, 2001:dcd:4::12, UDP_-_EDNS0_4096_D_K)
  • in/DNSKEY (alg 8, id 65169): The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (37.209.192.12, 37.209.194.12, 37.209.196.12, 37.209.198.12, 156.154.100.20, 156.154.101.20, 2001:502:2eda::20, 2001:502:ad09::20, 2001:dcd:1::12, 2001:dcd:2::12, 2001:dcd:3::12, 2001:dcd:4::12, UDP_-_EDNS0_4096_D_K)
  • in/DNSKEY (alg 8, id 65169): The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (37.209.192.12, 37.209.194.12, 37.209.196.12, 37.209.198.12, 156.154.100.20, 156.154.101.20, 2001:502:2eda::20, 2001:502:ad09::20, 2001:dcd:1::12, 2001:dcd:2::12, 2001:dcd:3::12, 2001:dcd:4::12, UDP_-_EDNS0_4096_D_K)
  • in/SOA: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (156.154.100.20, 156.154.101.20, 2001:502:2eda::20, 2001:502:ad09::20, UDP_-_EDNS0_4096_D_K)
  • in/SOA: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (37.209.192.12, 37.209.194.12, 37.209.196.12, 37.209.198.12, 2001:dcd:1::12, 2001:dcd:2::12, 2001:dcd:3::12, 2001:dcd:4::12, UDP_-_EDNS0_4096_D_K)
  • in/SOA: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (156.154.100.20, 156.154.101.20, 2001:502:2eda::20, 2001:502:ad09::20, UDP_-_EDNS0_4096_D_K)
  • in/SOA: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (37.209.192.12, 37.209.194.12, 37.209.196.12, 37.209.198.12, 2001:dcd:1::12, 2001:dcd:2::12, 2001:dcd:3::12, 2001:dcd:4::12, UDP_-_EDNS0_4096_D_K)
  • registry.in/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (29)
  • NSEC3 proving non-existence of registry.in/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of registry.in/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of registry.in/DS alg 7, id 9182: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of registry.in/DS alg 7, id 9182: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG in/DNSKEY alg 7, id 35373: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG in/DNSKEY alg 7, id 35373: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG in/DNSKEY alg 7, id 35373: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG in/DNSKEY alg 7, id 35373: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG in/DNSKEY alg 7, id 35373: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG in/DNSKEY alg 7, id 35373: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG in/DNSKEY alg 7, id 9182: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG in/DNSKEY alg 7, id 9182: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG in/DNSKEY alg 7, id 9182: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG in/DNSKEY alg 7, id 9182: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG in/DNSKEY alg 7, id 9182: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG in/DNSKEY alg 7, id 9182: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG in/SOA alg 7, id 9182: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG in/SOA alg 7, id 9182: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • in/DS (alg 7, id 35373): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • in/DS (alg 7, id 35373): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • in/DS (alg 7, id 35373): 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 7, id 35373): 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): 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.
  • registry.in/A: The response had an invalid RCODE (SERVFAIL) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (156.154.69.196, UDP_-_EDNS0_4096_D_K)
  • registry.in/AAAA: The response had an invalid RCODE (SERVFAIL) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (156.154.64.196, UDP_-_EDNS0_4096_D_K)
  • registry.in/DS 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