View on GitHub

DNSViz: A DNS visualization tool

nicbr.mil

Updated: 2021-08-26 19:53:41 UTC (972 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Bogus (3)
  • nicbr.mil/NS
  • nicbr.mil/NSEC3PARAM
  • nicbr.mil/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26838)
  • mil/DNSKEY (alg 8, id 39879)
  • mil/DNSKEY (alg 8, id 51349)
  • mil/DNSKEY (alg 8, id 9498)
  • mil/DS (alg 8, id 51349)
  • mil/DS (alg 8, id 51349)
  • nicbr.mil/DS (alg 8, id 50296)
Non_existent (2)
  • nicbr.mil/DNSKEY (alg 8, id 13710)
  • nicbr.mil/DNSKEY (alg 8, id 50296)

Delegation statusDelegation status

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

NoticesNotices

Errors (7)
  • mil to nicbr.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.
  • nicbr.mil/DNSKEY: No response was received from the server over UDP (tried 12 times). (140.153.43.44, 192.82.113.7, UDP_-_EDNS0_4096_D_KN)
  • nicbr.mil/DNSKEY: The response had an invalid RCODE (SERVFAIL). (130.114.200.6, TCP_-_NOEDNS_)
  • nicbr.mil/SOA: DNSSEC was effectively downgraded because the response had an invalid RCODE (SERVFAIL) with EDNS enabled. (140.153.43.44, UDP_-_NOEDNS_)
  • nicbr.mil/SOA: No response was received from the server over TCP (tried 3 times). (192.82.113.7, TCP_-_EDNS0_4096_D_N)
  • nicbr.mil/SOA: The DNSSEC records necessary to validate the response could not be retrieved from the server. (140.153.43.44, UDP_-_EDNS0_4096_D_KN)
  • nicbr.mil/SOA: The response had an invalid RCODE (SERVFAIL) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). (140.153.43.44, UDP_-_EDNS0_4096_D_KN)
Warnings (10)
  • mil to nicbr.mil: The following NS name(s) were found in the delegation NS RRset (i.e., in the mil zone), but not in the authoritative NS RRset: ns03.army.mil
  • mil/DS (alg 8, id 51349): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
  • mil/DS (alg 8, id 51349): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
  • mil/DS (alg 8, id 51349): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.
  • mil/DS (alg 8, id 51349): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.
  • nicbr.mil/DS (alg 8, id 50296): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
  • nicbr.mil/DS (alg 8, id 50296): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
  • nicbr.mil/DS (alg 8, id 50296): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.
  • nicbr.mil/DS (alg 8, id 50296): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.
  • nicbr.mil/SOA: 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. (192.82.113.7, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)

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