View on GitHub

DNSViz: A DNS visualization tool

pmi.gov

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

RRset statusRRset status

Bogus (3)
  • pmi.gov/A (NODATA)
  • pmi.gov/SOA (NODATA)
  • pmi.gov/TXT (NODATA)
Secure (4)
  • pmi.gov/A
  • pmi.gov/NS
  • pmi.gov/SOA
  • pmi.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 20038)
  • ./DNSKEY (alg 8, id 20326)
  • gov/DNSKEY (alg 13, id 2536)
  • gov/DNSKEY (alg 13, id 35496)
  • gov/DS (alg 13, id 2536)
  • pmi.gov/DNSKEY (alg 8, id 44055)
  • pmi.gov/DNSKEY (alg 8, id 53416)
  • pmi.gov/DNSKEY (alg 8, id 5766)
  • pmi.gov/DNSKEY (alg 8, id 59422)
  • pmi.gov/DS (alg 8, id 53416)
  • pmi.gov/DS (alg 8, id 59422)

Delegation statusDelegation status

Secure (2)
  • . to gov
  • gov to pmi.gov

NoticesNotices

Errors (17)
  • gov to pmi.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. (12.96.42.221, UDP_-_EDNS0_512_D_KN)
  • gov to pmi.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. (12.96.42.221, UDP_-_EDNS0_512_D_KN)
  • pmi.gov/A (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. (12.96.42.221, UDP_-_EDNS0_4096_D_KN)
  • pmi.gov/A (NODATA): The response was an upward referral. See https://www.dns-oarc.net/oarc/articles/upward-referrals-considered-harmful. (12.96.42.221, UDP_-_EDNS0_4096_D_KN)
  • pmi.gov/DNSKEY (alg 8, id 44055): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (12.96.42.221, UDP_-_EDNS0_512_D_KN)
  • pmi.gov/DNSKEY (alg 8, id 53416): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (12.96.42.221, UDP_-_EDNS0_512_D_KN)
  • pmi.gov/DNSKEY (alg 8, id 5766): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (12.96.42.221, UDP_-_EDNS0_512_D_KN)
  • pmi.gov/DNSKEY (alg 8, id 59422): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (12.96.42.221, UDP_-_EDNS0_512_D_KN)
  • pmi.gov/SOA (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. (12.96.42.221, UDP_-_EDNS0_4096_D_KN_0x20)
  • pmi.gov/SOA (NODATA): The response was an upward referral. See https://www.dns-oarc.net/oarc/articles/upward-referrals-considered-harmful. (12.96.42.221, UDP_-_EDNS0_4096_D_KN_0x20)
  • pmi.gov/TXT (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. (12.96.42.221, UDP_-_EDNS0_4096_D_KN)
  • pmi.gov/TXT (NODATA): The response was an upward referral. See https://www.dns-oarc.net/oarc/articles/upward-referrals-considered-harmful. (12.96.42.221, UDP_-_EDNS0_4096_D_KN)
  • pmi.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • pmi.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • pmi.gov/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
  • pmi.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • pmi.gov/CDNSKEY has errors; 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