View on GitHub

DNSViz: A DNS visualization tool

org.gl

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

RRset statusRRset status

Insecure (6)
  • org.gl/NS
  • org.gl/NS (NXDOMAIN)
  • org.gl/NSEC3PARAM
  • org.gl/NSEC3PARAM (NXDOMAIN)
  • org.gl/SOA
  • org.gl/SOA (NXDOMAIN)
Secure (1)
  • gl/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (5)
  • NSEC3 proving non-existence of org.gl/NS
  • NSEC3 proving non-existence of org.gl/NSEC3PARAM
  • NSEC3 proving non-existence of org.gl/SOA
  • org.gl/DNSKEY (alg 8, id 14940)
  • org.gl/DNSKEY (alg 8, id 57292)
Secure (6)
  • ./DNSKEY (alg 8, id 18733)
  • ./DNSKEY (alg 8, id 20326)
  • NSEC3 proving non-existence of org.gl/DS
  • gl/DNSKEY (alg 8, id 11560)
  • gl/DNSKEY (alg 8, id 42900)
  • gl/DS (alg 8, id 11560)

Delegation statusDelegation status

Incomplete (1)
  • gl to org.gl
Secure (1)
  • . to gl

NoticesNotices

Errors (31)
  • NSEC3 proving non-existence of org.gl/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 org.gl/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 org.gl/NS: 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 org.gl/NS: 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 org.gl/NSEC3PARAM: 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 org.gl/NSEC3PARAM: 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 org.gl/SOA: 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 org.gl/SOA: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of org.gl/NS alg 8, id 42900: The Signer's Name field of the RRSIG RR (gl) does not match the name of the zone containing the RRset (org.gl). See RFC 4035, Sec. 5.3.1.
  • RRSIG NSEC3 proving non-existence of org.gl/NS alg 8, id 42900: The Signer's Name field of the RRSIG RR (gl) does not match the name of the zone containing the RRset (org.gl). See RFC 4035, Sec. 5.3.1.
  • RRSIG NSEC3 proving non-existence of org.gl/NS alg 8, id 42900: The Signer's Name field of the RRSIG RR (gl) does not match the name of the zone containing the RRset (org.gl). See RFC 4035, Sec. 5.3.1.
  • RRSIG NSEC3 proving non-existence of org.gl/NSEC3PARAM alg 8, id 42900: The Signer's Name field of the RRSIG RR (gl) does not match the name of the zone containing the RRset (org.gl). See RFC 4035, Sec. 5.3.1.
  • RRSIG NSEC3 proving non-existence of org.gl/NSEC3PARAM alg 8, id 42900: The Signer's Name field of the RRSIG RR (gl) does not match the name of the zone containing the RRset (org.gl). See RFC 4035, Sec. 5.3.1.
  • RRSIG NSEC3 proving non-existence of org.gl/NSEC3PARAM alg 8, id 42900: The Signer's Name field of the RRSIG RR (gl) does not match the name of the zone containing the RRset (org.gl). See RFC 4035, Sec. 5.3.1.
  • RRSIG NSEC3 proving non-existence of org.gl/SOA alg 8, id 42900: The Signer's Name field of the RRSIG RR (gl) does not match the name of the zone containing the RRset (org.gl). See RFC 4035, Sec. 5.3.1.
  • RRSIG NSEC3 proving non-existence of org.gl/SOA alg 8, id 42900: The Signer's Name field of the RRSIG RR (gl) does not match the name of the zone containing the RRset (org.gl). See RFC 4035, Sec. 5.3.1.
  • RRSIG NSEC3 proving non-existence of org.gl/SOA alg 8, id 42900: The Signer's Name field of the RRSIG RR (gl) does not match the name of the zone containing the RRset (org.gl). See RFC 4035, Sec. 5.3.1.
  • gl to org.gl: No delegation NS records were detected in the parent zone (gl). This results in an NXDOMAIN response to a DS query (for DNSSEC), even if the parent servers are authoritative for the child. See RFC 1034, Sec. 4.2.2. (204.61.216.49, 2001:500:14:6049:ad::1, UDP_-_EDNS0_4096_D_KN)
  • org.gl zone: The server(s) did not respond authoritatively for the namespace. See RFC 1035, Sec. 4.1.1. (185.28.194.194, 185.38.108.108, 194.177.224.13, 2a00:fea0:dead::beef)
  • org.gl/DNSKEY (alg 8, id 14940): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (185.28.194.194, 185.38.108.108, 194.177.224.13, 2a00:fea0:dead::beef, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
  • org.gl/NS (NXDOMAIN): An SOA RR with owner name (gl) not matching the zone name (org.gl) was returned with the NXDOMAIN response. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.1. (185.28.194.194, 185.38.108.108, 194.177.224.13, 2a00:fea0:dead::beef, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
  • org.gl/NSEC3PARAM (NXDOMAIN): An SOA RR with owner name (gl) not matching the zone name (org.gl) was returned with the NXDOMAIN response. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.1. (185.28.194.194, 185.38.108.108, 194.177.224.13, 2a00:fea0:dead::beef, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
  • org.gl/SOA (NXDOMAIN): An SOA RR with owner name (gl) not matching the zone name (org.gl) was returned with the NXDOMAIN response. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.1. (185.28.194.194, 185.38.108.108, 194.177.224.13, 2a00:fea0:dead::beef, TCP_-_EDNS0_4096_D_KN, TCP_-_EDNS0_4096_D_KN_0x20, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • org.gl/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • org.gl/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • org.gl/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • org.gl/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
  • org.gl/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • org.gl/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • r0wkoeq1ln.org.gl/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • org.gl/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (17)
  • NSEC3 proving non-existence of org.gl/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of org.gl/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of org.gl/NS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of org.gl/NS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of org.gl/NSEC3PARAM: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of org.gl/NSEC3PARAM: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of org.gl/SOA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of org.gl/SOA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • org.gl/DNSKEY (alg 8, id 57292): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (185.28.194.194, 185.38.108.108, 194.177.224.13, 2a00:fea0:dead::beef, TCP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN)
  • r0wkoeq1ln.org.gl/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • org.gl/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • org.gl/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • org.gl/TXT has warnings; select the "Denial of existence" DNSSEC option to see them.
  • org.gl/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • org.gl/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • org.gl/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • org.gl/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