View on GitHub

DNSViz: A DNS visualization tool

bncr.fi.cr

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

RRset statusRRset status

Insecure (4)
  • bncr.fi.cr/MX
  • bncr.fi.cr/NS
  • bncr.fi.cr/SOA
  • bncr.fi.cr/TXT
Secure (1)
  • cr/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (7)
  • bncr.fi.cr/DNSKEY (alg 8, id 13921)
  • bncr.fi.cr/DNSKEY (alg 8, id 30790)
  • bncr.fi.cr/DNSKEY (alg 8, id 56985)
  • bncr.fi.cr/DNSKEY (alg 8, id 9847)
  • bncr.fi.cr/DS (alg 8, id 30790)
  • fi.cr/DNSKEY (alg 13, id 15493)
  • fi.cr/DNSKEY (alg 13, id 31253)
Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26116)
  • ./DNSKEY (alg 8, id 46594)
  • NSEC3 proving non-existence of fi.cr/DS
  • cr/DNSKEY (alg 13, id 11634)
  • cr/DNSKEY (alg 13, id 51625)
  • cr/DS (alg 13, id 51625)

Delegation statusDelegation status

Insecure (1)
  • cr to fi.cr
Secure (2)
  • . to cr
  • fi.cr to bncr.fi.cr

NoticesNotices

Errors (8)
  • NSEC3 proving non-existence of fi.cr/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 fi.cr/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • RRSIG fi.cr/DNSKEY alg 13, id 15493: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG fi.cr/DNSKEY alg 13, id 15493: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • gmupnzwl5c.bncr.fi.cr/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • bncr.fi.cr/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • bncr.fi.cr/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • bncr.fi.cr/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (6)
  • NSEC3 proving non-existence of fi.cr/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of fi.cr/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • gmupnzwl5c.bncr.fi.cr/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • bncr.fi.cr/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • bncr.fi.cr/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • bncr.fi.cr/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