View on GitHub

DNSViz: A DNS visualization tool

225.41.196.in-addr.arpa

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

RRset statusRRset status

Bogus (2)
  • 225.41.196.in-addr.arpa/NS
  • 225.41.196.in-addr.arpa/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (2)
  • 225.41.196.in-addr.arpa/DNSKEY (alg 5, id 1797)
  • 225.41.196.in-addr.arpa/DNSKEY (alg 5, id 57448)
Secure (20)
  • ./DNSKEY (alg 8, id 14631)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 42351)
  • 196.in-addr.arpa/DNSKEY (alg 8, id 18977)
  • 196.in-addr.arpa/DNSKEY (alg 8, id 42954)
  • 196.in-addr.arpa/DS (alg 8, id 18872)
  • 196.in-addr.arpa/DS (alg 8, id 18977)
  • 196.in-addr.arpa/DS (alg 8, id 18977)
  • 225.41.196.in-addr.arpa/DS (alg 5, id 57448)
  • arpa/DNSKEY (alg 8, id 41685)
  • arpa/DNSKEY (alg 8, id 42581)
  • arpa/DNSKEY (alg 8, id 6795)
  • arpa/DS (alg 8, id 42581)
  • arpa/DS (alg 8, id 42581)
  • in-addr.arpa/DNSKEY (alg 8, id 34704)
  • in-addr.arpa/DNSKEY (alg 8, id 47054)
  • in-addr.arpa/DNSKEY (alg 8, id 54956)
  • in-addr.arpa/DS (alg 8, id 47054)
  • in-addr.arpa/DS (alg 8, id 53696)
  • in-addr.arpa/DS (alg 8, id 63982)
Non_existent (3)
  • 196.in-addr.arpa/DNSKEY (alg 8, id 18872)
  • in-addr.arpa/DNSKEY (alg 8, id 53696)
  • in-addr.arpa/DNSKEY (alg 8, id 63982)

Delegation statusDelegation status

Bogus (1)
  • 196.in-addr.arpa to 225.41.196.in-addr.arpa
Secure (3)
  • . to arpa
  • arpa to in-addr.arpa
  • in-addr.arpa to 196.in-addr.arpa

NoticesNotices

Errors (25)
  • 196.in-addr.arpa to 225.41.196.in-addr.arpa: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (196.41.225.10, UDP_-_EDNS0_4096_D)
  • 225.41.196.in-addr.arpa zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (196.41.225.11)
  • 225.41.196.in-addr.arpa/DNSKEY (alg 5, id 1797): DNSSEC was effectively downgraded because the response had an invalid RCODE (FORMERR) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (196.41.225.10, UDP_-_EDNS0_4096_D)
  • 225.41.196.in-addr.arpa/DNSKEY (alg 5, id 1797): The response had an invalid RCODE (FORMERR) until the NSID EDNS option was removed. See RFC 6891, Sec. 6.1.2. (196.41.225.10, UDP_-_EDNS0_4096_D_KN)
  • 225.41.196.in-addr.arpa/DNSKEY (alg 5, id 57448): DNSSEC was effectively downgraded because the response had an invalid RCODE (FORMERR) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (196.41.225.10, UDP_-_EDNS0_4096_D)
  • 225.41.196.in-addr.arpa/DNSKEY (alg 5, id 57448): The response had an invalid RCODE (FORMERR) until the NSID EDNS option was removed. See RFC 6891, Sec. 6.1.2. (196.41.225.10, UDP_-_EDNS0_4096_D_KN)
  • 225.41.196.in-addr.arpa/DNSKEY: The response had an invalid RCODE (FORMERR). See RFC 1035, Sec. 4.1.1. (196.41.225.10, UDP_-_EDNS0_512_D_KN)
  • 225.41.196.in-addr.arpa/DS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (196.216.2.1, 196.216.168.10, 2001:42d0::200:2:1, 2001:43f8:120::10, UDP_-_NOEDNS_)
  • 225.41.196.in-addr.arpa/NS: DNSSEC was effectively downgraded because the response had an invalid RCODE (FORMERR) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (196.41.225.10, UDP_-_EDNS0_4096_D)
  • 225.41.196.in-addr.arpa/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (196.41.225.11, 196.216.2.1, 196.216.168.10, 2001:42d0::200:2:1, 2001:43f8:120::10, UDP_-_NOEDNS_)
  • 225.41.196.in-addr.arpa/NS: The response had an invalid RCODE (FORMERR) until the NSID EDNS option was removed. See RFC 6891, Sec. 6.1.2. (196.41.225.10, UDP_-_EDNS0_4096_D_KN)
  • 225.41.196.in-addr.arpa/SOA: DNSSEC was effectively downgraded because the response had an invalid RCODE (FORMERR) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (196.41.225.10, TCP_-_EDNS0_4096_D)
  • 225.41.196.in-addr.arpa/SOA: DNSSEC was effectively downgraded because the response had an invalid RCODE (FORMERR) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (196.41.225.10, UDP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_0x20)
  • 225.41.196.in-addr.arpa/SOA: The response had an invalid RCODE (FORMERR) until the NSID EDNS option was removed. See RFC 6891, Sec. 6.1.2. (196.41.225.10, TCP_-_EDNS0_4096_D_N)
  • 225.41.196.in-addr.arpa/SOA: The response had an invalid RCODE (FORMERR) until the NSID EDNS option was removed. See RFC 6891, Sec. 6.1.2. (196.41.225.10, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • RRSIG 225.41.196.in-addr.arpa/DNSKEY alg 5, id 57448: The Signature Expiration field of the RRSIG RR (2020-05-02 16:42:51+00:00) is 324 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG 225.41.196.in-addr.arpa/DNSKEY alg 5, id 57448: The Signature Expiration field of the RRSIG RR (2020-05-02 16:42:51+00:00) is 324 days in the past. See RFC 4035, Sec. 5.3.1.
  • RRSIG 225.41.196.in-addr.arpa/SOA alg 5, id 1797: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • in-addr.arpa zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:13c7:7010::53)
  • 225.41.196.in-addr.arpa/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • 225.41.196.in-addr.arpa/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • 225.41.196.in-addr.arpa/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
  • 225.41.196.in-addr.arpa/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • b2fm4k7dx9.225.41.196.in-addr.arpa/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • 225.41.196.in-addr.arpa/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (19)
  • 196.in-addr.arpa/DS (alg 8, id 18977): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • 196.in-addr.arpa/DS (alg 8, id 18977): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • 196.in-addr.arpa/DS (alg 8, id 18977): 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.
  • 196.in-addr.arpa/DS (alg 8, id 18977): 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 225.41.196.in-addr.arpa/DNSKEY alg 5, id 1797: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG 225.41.196.in-addr.arpa/DNSKEY alg 5, id 1797: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG 225.41.196.in-addr.arpa/DNSKEY alg 5, id 57448: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG 225.41.196.in-addr.arpa/DNSKEY alg 5, id 57448: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG 225.41.196.in-addr.arpa/NS alg 5, id 1797: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG 225.41.196.in-addr.arpa/SOA alg 5, id 1797: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • arpa/DS (alg 8, id 42581): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • arpa/DS (alg 8, id 42581): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • arpa/DS (alg 8, id 42581): 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.
  • arpa/DS (alg 8, id 42581): 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.
  • b2fm4k7dx9.225.41.196.in-addr.arpa/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 225.41.196.in-addr.arpa/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 225.41.196.in-addr.arpa/TXT has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 225.41.196.in-addr.arpa/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 225.41.196.in-addr.arpa/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