View on GitHub

DNSViz: A DNS visualization tool

dnssec-test.balug.org

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

RRset statusRRset status

Secure (7)
  • dnssec-test.balug.org/A
  • dnssec-test.balug.org/AAAA
  • dnssec-test.balug.org/CDNSKEY
  • dnssec-test.balug.org/CDS
  • dnssec-test.balug.org/NS
  • dnssec-test.balug.org/NSEC3PARAM
  • dnssec-test.balug.org/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (14)
  • ./DNSKEY (alg 8, id 20038)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 61050)
  • balug.org/DNSKEY (alg 8, id 17095)
  • balug.org/DNSKEY (alg 8, id 47448)
  • balug.org/DS (alg 8, id 17095)
  • dnssec-test.balug.org/DNSKEY (alg 8, id 26836)
  • dnssec-test.balug.org/DNSKEY (alg 8, id 52051)
  • dnssec-test.balug.org/DNSKEY (alg 8, id 53986)
  • dnssec-test.balug.org/DS (alg 8, id 53986)
  • org/DNSKEY (alg 8, id 15678)
  • org/DNSKEY (alg 8, id 23064)
  • org/DNSKEY (alg 8, id 26974)
  • org/DS (alg 8, id 26974)

Delegation statusDelegation status

Secure (3)
  • . to org
  • balug.org to dnssec-test.balug.org
  • org to balug.org

NoticesNotices

Errors (18)
  • RRSIG dnssec-test.balug.org/A alg 8, id 26836: With a TTL of 300 the RRSIG RR can be in the cache of a non-validating resolver until 4 seconds after it expires at 2024-09-29 16:47:33+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG dnssec-test.balug.org/AAAA alg 8, id 26836: With a TTL of 300 the RRSIG RR can be in the cache of a non-validating resolver until 4 seconds after it expires at 2024-09-29 16:47:33+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG dnssec-test.balug.org/CDNSKEY alg 8, id 52051: With a TTL of 300 the RRSIG RR can be in the cache of a non-validating resolver until 4 seconds after it expires at 2024-09-29 16:47:33+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG dnssec-test.balug.org/CDNSKEY alg 8, id 53986: With a TTL of 300 the RRSIG RR can be in the cache of a non-validating resolver until 4 seconds after it expires at 2024-09-29 16:47:33+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG dnssec-test.balug.org/CDS alg 8, id 52051: With a TTL of 300 the RRSIG RR can be in the cache of a non-validating resolver until 4 seconds after it expires at 2024-09-29 16:47:33+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG dnssec-test.balug.org/CDS alg 8, id 53986: With a TTL of 300 the RRSIG RR can be in the cache of a non-validating resolver until 4 seconds after it expires at 2024-09-29 16:47:33+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG dnssec-test.balug.org/DNSKEY alg 8, id 52051: With a TTL of 300 the RRSIG RR can be in the cache of a non-validating resolver until 4 seconds after it expires at 2024-09-29 16:47:33+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG dnssec-test.balug.org/DNSKEY alg 8, id 52051: With a TTL of 300 the RRSIG RR can be in the cache of a non-validating resolver until 4 seconds after it expires at 2024-09-29 16:47:33+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG dnssec-test.balug.org/DNSKEY alg 8, id 52051: With a TTL of 300 the RRSIG RR can be in the cache of a non-validating resolver until 4 seconds after it expires at 2024-09-29 16:47:33+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG dnssec-test.balug.org/DNSKEY alg 8, id 53986: With a TTL of 300 the RRSIG RR can be in the cache of a non-validating resolver until 4 seconds after it expires at 2024-09-29 16:47:33+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG dnssec-test.balug.org/DNSKEY alg 8, id 53986: With a TTL of 300 the RRSIG RR can be in the cache of a non-validating resolver until 4 seconds after it expires at 2024-09-29 16:47:33+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG dnssec-test.balug.org/DNSKEY alg 8, id 53986: With a TTL of 300 the RRSIG RR can be in the cache of a non-validating resolver until 4 seconds after it expires at 2024-09-29 16:47:33+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG dnssec-test.balug.org/NS alg 8, id 26836: With a TTL of 300 the RRSIG RR can be in the cache of a non-validating resolver until 4 seconds after it expires at 2024-09-29 16:47:33+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG dnssec-test.balug.org/SOA alg 8, id 26836: With a TTL of 3600 the RRSIG RR can be in the cache of a non-validating resolver until 55 minutes after it expires at 2024-09-29 16:47:34+00:00. See RFC 4035, Sec. 5.3.3.
  • dnssec-test.balug.org/DS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (96.95.217.99, UDP_-_NOEDNS_)
  • dnssec-test.balug.org/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (96.95.217.99, UDP_-_NOEDNS_)
  • dnssec-test.balug.org/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • dnssec-test.balug.org/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
  • RRSIG dnssec-test.balug.org/NSEC3PARAM alg 8, id 26836: The value of the Signature Expiration field of the RRSIG RR (2024-09-29 16:47:25+00:00) is within possible clock skew range (4 minutes) of the current time (2024-09-29 16:42:37+00:00). See RFC 4035, Sec. 5.3.1.
  • dnssec-test.balug.org/CDNSKEY: The contents of the DS RRset are inconsistent with those of the CDNSKEY RRset. See RFC 7344, Sec. 3, RFC 7344, Sec. 5.
  • dnssec-test.balug.org/CDS: The contents of the DS RRset are inconsistent with those of the CDS RRset. See RFC 7344, Sec. 3, RFC 7344, Sec. 5.
  • dnssec-test.balug.org/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • dnssec-test.balug.org/TXT has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gjznw.5k3x4.dnssec-test.balug.org/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • dnssec-test.balug.org/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