View on GitHub

DNSViz: A DNS visualization tool

postar.tim.rs

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

RRset statusRRset status

Insecure (1)
  • postar.tim.rs/A
Secure (1)
  • rs/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (8)
  • ./DNSKEY (alg 8, id 20038)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 5613)
  • NSEC3 proving non-existence of tim.rs/DS
  • rs/DNSKEY (alg 13, id 23736)
  • rs/DNSKEY (alg 13, id 29729)
  • rs/DNSKEY (alg 13, id 57382)
  • rs/DS (alg 13, id 57382)

Delegation statusDelegation status

Insecure (1)
  • rs to tim.rs
Secure (1)
  • . to rs

NoticesNotices

Errors (5)
  • NSEC3 proving non-existence of tim.rs/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 tim.rs/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • tim.rs zone: The server(s) did not respond authoritatively for the namespace. See RFC 1035, Sec. 4.1.1. (80.93.224.2)
  • tim.rs zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (185.22.144.58)
  • tim.rs/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (2)
  • NSEC3 proving non-existence of tim.rs/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of tim.rs/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.

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