View on GitHub

DNSViz: A DNS visualization tool

prs.mil

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

RRset statusRRset status

Insecure (3)
  • prs.mil/NS
  • prs.mil/SOA
  • prs.mil/TXT
Secure (1)
  • mil/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (4)
  • prs.mil/DNSKEY (alg 8, id 22819)
  • prs.mil/DNSKEY (alg 8, id 30813)
  • prs.mil/DNSKEY (alg 8, id 33645)
  • prs.mil/DNSKEY (alg 8, id 42174)
Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 48903)
  • NSEC3 proving non-existence of prs.mil/DS
  • mil/DNSKEY (alg 8, id 47763)
  • mil/DNSKEY (alg 8, id 48726)
  • mil/DNSKEY (alg 8, id 7765)
  • mil/DS (alg 8, id 7765)
  • mil/DS (alg 8, id 7765)

Delegation statusDelegation status

Insecure (1)
  • mil to prs.mil
Secure (1)
  • . to mil

NoticesNotices

Errors (9)
  • NSEC3 proving non-existence of prs.mil/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 prs.mil/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • mil/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (199.252.155.234, UDP_-_EDNS0_512_D_K)
  • prs.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • prs.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • prs.mil/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • prs.mil/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • prs.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • ujl27y5gz6.prs.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (12)
  • NSEC3 proving non-existence of prs.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of prs.mil/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • 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.
  • prs.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • prs.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • prs.mil/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • prs.mil/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • prs.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ujl27y5gz6.prs.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