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

Bogus (6)
  • org.gl/NS
  • org.gl/NS (NODATA)
  • org.gl/SOA
  • org.gl/SOA (NODATA)
  • org.gl/TXT
  • org.gl/TXT
Secure (1)
  • gl/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (4)
  • NSEC3 proving non-existence of org.gl/NS
  • NSEC3 proving non-existence of org.gl/SOA
  • org.gl/DNSKEY (alg 8, id 41541)
  • org.gl/DNSKEY (alg 8, id 57292)
Secure (6)
  • ./DNSKEY (alg 8, id 14631)
  • ./DNSKEY (alg 8, id 20326)
  • NSEC3 proving non-existence of org.gl/DS
  • gl/DNSKEY (alg 8, id 11560)
  • gl/DNSKEY (alg 8, id 25639)
  • gl/DS (alg 8, id 11560)

Delegation statusDelegation status

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

NoticesNotices

Errors (25)
  • 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/DS: The NS bit was not set in the bitmap of the NSEC3 RR corresponding to the delegated name (org.gl). See RFC 5155, Sec. 8.9.
  • NSEC3 proving non-existence of org.gl/DS: The NS bit was not set in the bitmap of the NSEC3 RR corresponding to the delegated name (org.gl). See RFC 5155, Sec. 8.9.
  • 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/NS: The following queries resulted in an answer response, even though the bitmap in the NSEC3 RR indicates that the queried records don't exist: org.gl/DNSKEY, org.gl/NS, org.gl/SOA See RFC 5155, Sec. 8.5.
  • NSEC3 proving non-existence of org.gl/NS: The following queries resulted in an answer response, even though the bitmap in the NSEC3 RR indicates that the queried records don't exist: org.gl/DNSKEY, org.gl/NS, org.gl/SOA See RFC 5155, Sec. 8.5.
  • 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.
  • NSEC3 proving non-existence of org.gl/SOA: The following queries resulted in an answer response, even though the bitmap in the NSEC3 RR indicates that the queried records don't exist: org.gl/DNSKEY, org.gl/NS, org.gl/SOA See RFC 5155, Sec. 8.5.
  • NSEC3 proving non-existence of org.gl/SOA: The following queries resulted in an answer response, even though the bitmap in the NSEC3 RR indicates that the queried records don't exist: org.gl/DNSKEY, org.gl/NS, org.gl/SOA See RFC 5155, Sec. 8.5.
  • RRSIG NSEC3 proving non-existence of org.gl/NS alg 8, id 25639: 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 25639: 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 org.gl/TXT alg 8, id 25639: 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.
  • org.gl/DNSKEY (alg 8, id 41541): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (185.28.194.194, 185.38.108.108, 204.61.216.49, 2001:500:14:6049:ad::1, 2a00:fea0:dead::beef, UDP_-_EDNS0_4096_D_KN)
  • org.gl/NS (NODATA): An SOA RR with owner name (gl) not matching the zone name (org.gl) was returned with the NODATA response. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (185.28.194.194, 185.38.108.108, 204.61.216.49, 2001:500:14:6049:ad::1, 2a00:fea0:dead::beef, UDP_-_EDNS0_4096_D_KN)
  • org.gl/SOA (NODATA): An SOA RR with owner name (gl) not matching the zone name (org.gl) was returned with the NODATA response. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (185.28.194.194, 185.38.108.108, 204.61.216.49, 2001:500:14:6049:ad::1, 2a00:fea0:dead::beef, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • org.gl/AAAA 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.
  • org.gl/CNAME 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/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.
  • u17tadxrlh.org.gl/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (14)
  • 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/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, 204.61.216.49, 2001:500:14:6049:ad::1, 2a00:fea0:dead::beef, UDP_-_EDNS0_4096_D_KN)
  • org.gl/AAAA 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/CNAME 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/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.
  • u17tadxrlh.org.gl/A 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