View on GitHub

DNSViz: A DNS visualization tool

gpodev.gov

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

RRset statusRRset status

Bogus (5)
  • gpodev.gov/NS
  • gpodev.gov/NSEC3PARAM
  • gpodev.gov/NSEC3PARAM (NODATA)
  • gpodev.gov/SOA
  • gpodev.gov/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (6)
  • gpodev.gov/DNSKEY (alg 13, id 51138)
  • gpodev.gov/DNSKEY (alg 13, id 5802)
  • gpodev.gov/DNSKEY (alg 13, id 61439)
  • gpodev.gov/DNSKEY (alg 7, id 20433)
  • gpodev.gov/DNSKEY (alg 7, id 35930)
  • gpodev.gov/DNSKEY (alg 7, id 62582)
Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 20826)
  • gov/DNSKEY (alg 8, id 261)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gpodev.gov/DS (alg 8, id 52006)
Non_existent (1)
  • gpodev.gov/DNSKEY (alg 8, id 52006)

Delegation statusDelegation status

Bogus (1)
  • gov to gpodev.gov
Secure (1)
  • . to gov

NoticesNotices

Errors (23)
  • gov to gpodev.gov: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.140.15.100, 162.140.254.200, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • gov to gpodev.gov: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.140.15.100, 162.140.254.200, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • gpodev.gov/DNSKEY (alg 13, id 51138): The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.140.254.200, UDP_-_EDNS0_4096_D_KN)
  • gpodev.gov/DNSKEY (alg 13, id 5802): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (162.140.15.100, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • gpodev.gov/DNSKEY (alg 13, id 5802): The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.140.254.200, UDP_-_EDNS0_4096_D_KN)
  • gpodev.gov/DNSKEY (alg 13, id 61439): The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.140.254.200, UDP_-_EDNS0_4096_D_KN)
  • gpodev.gov/DNSKEY (alg 7, id 20433): The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.140.254.200, UDP_-_EDNS0_4096_D_KN)
  • gpodev.gov/DNSKEY (alg 7, id 35930): The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.140.254.200, UDP_-_EDNS0_4096_D_KN)
  • gpodev.gov/DNSKEY (alg 7, id 62582): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (162.140.15.100, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • gpodev.gov/DNSKEY (alg 7, id 62582): The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.140.254.200, UDP_-_EDNS0_4096_D_KN)
  • gpodev.gov/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (162.140.15.100, UDP_-_EDNS0_4096_D_KN)
  • gpodev.gov/NS: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.140.254.200, UDP_-_EDNS0_4096_D_KN)
  • gpodev.gov/NSEC3PARAM (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (162.140.15.100, UDP_-_EDNS0_4096_D_KN)
  • gpodev.gov/NSEC3PARAM: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.140.254.200, UDP_-_EDNS0_4096_D_KN)
  • gpodev.gov/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (162.140.15.100, UDP_-_EDNS0_4096_D_KN)
  • gpodev.gov/SOA: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (162.140.254.200, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • gpodev.gov/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
  • gpodev.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • gpodev.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • gpodev.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • gpodev.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • 2o5v4p13sm.gpodev.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • gpodev.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (26)
  • RRSIG gpodev.gov/DNSKEY alg 7, id 20433: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gpodev.gov/DNSKEY alg 7, id 20433: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gpodev.gov/DNSKEY alg 7, id 20433: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gpodev.gov/DNSKEY alg 7, id 20433: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gpodev.gov/DNSKEY alg 7, id 20433: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gpodev.gov/DNSKEY alg 7, id 20433: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gpodev.gov/DNSKEY alg 7, id 62582: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gpodev.gov/DNSKEY alg 7, id 62582: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gpodev.gov/DNSKEY alg 7, id 62582: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gpodev.gov/DNSKEY alg 7, id 62582: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gpodev.gov/DNSKEY alg 7, id 62582: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gpodev.gov/DNSKEY alg 7, id 62582: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gpodev.gov/NS alg 7, id 62582: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gpodev.gov/NSEC3PARAM alg 7, id 62582: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG gpodev.gov/SOA alg 7, id 62582: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • gpodev.gov/DNSKEY (alg 13, id 51138): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (162.140.15.100, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • gpodev.gov/DNSKEY (alg 13, id 61439): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (162.140.15.100, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • gpodev.gov/DNSKEY (alg 7, id 20433): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (162.140.15.100, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • gpodev.gov/DNSKEY (alg 7, id 35930): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (162.140.15.100, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • gpodev.gov/TXT has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gpodev.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gpodev.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gpodev.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gpodev.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 2o5v4p13sm.gpodev.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gpodev.gov/AAAA 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