View on GitHub

DNSViz: A DNS visualization tool

repi.mil

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

RRset statusRRset status

Bogus (3)
  • repi.mil/NS
  • repi.mil/SOA
  • repi.mil/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (4)
  • repi.mil/DNSKEY (alg 8, id 15807)
  • repi.mil/DNSKEY (alg 8, id 30691)
  • repi.mil/DNSKEY (alg 8, id 45109)
  • repi.mil/DNSKEY (alg 8, id 54560)
Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 48903)
  • mil/DNSKEY (alg 8, id 27843)
  • mil/DNSKEY (alg 8, id 47763)
  • mil/DNSKEY (alg 8, id 7765)
  • mil/DS (alg 8, id 7765)
  • mil/DS (alg 8, id 7765)
  • repi.mil/DS (alg 8, id 49309)
Non_existent (1)
  • repi.mil/DNSKEY (alg 8, id 49309)

Delegation statusDelegation status

Bogus (1)
  • mil to repi.mil
Secure (1)
  • . to mil

NoticesNotices

Errors (7)
  • mil to repi.mil: 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. (155.7.145.112, 155.7.145.113, 155.7.208.112, 155.7.208.113, UDP_-_EDNS0_4096_D_K)
  • mil to repi.mil: 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. (155.7.145.112, 155.7.145.113, 155.7.208.112, 155.7.208.113, UDP_-_EDNS0_4096_D_K)
  • repi.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • repi.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • aypvt9n03s.repi.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • repi.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • repi.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (11)
  • ./DNSKEY (alg 8, id 20326): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (192.112.36.4, UDP_-_EDNS0_4096_D_K)
  • ./DNSKEY (alg 8, id 48903): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (192.112.36.4, UDP_-_EDNS0_4096_D_K)
  • mil/DS (alg 8, id 7765): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • mil/DS (alg 8, id 7765): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • mil/DS (alg 8, id 7765): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • mil/DS (alg 8, id 7765): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • repi.mil/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • repi.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • aypvt9n03s.repi.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • repi.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • repi.mil/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