View on GitHub

DNSViz: A DNS visualization tool

nro.mil

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

RRset statusRRset status

Secure (5)
  • nro.mil/MX
  • nro.mil/NS
  • nro.mil/NSEC3PARAM
  • nro.mil/SOA
  • nro.mil/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 20826)
  • mil/DNSKEY (alg 8, id 50350)
  • mil/DNSKEY (alg 8, id 51621)
  • mil/DNSKEY (alg 8, id 56347)
  • mil/DS (alg 8, id 56347)
  • nro.mil/DNSKEY (alg 8, id 10330)
  • nro.mil/DNSKEY (alg 8, id 31515)
  • nro.mil/DNSKEY (alg 8, id 53985)
  • nro.mil/DS (alg 8, id 10330)
  • nro.mil/DS (alg 8, id 10330)

Delegation statusDelegation status

Secure (2)
  • . to mil
  • mil to nro.mil

NoticesNotices

Errors (14)
  • RRSIG nro.mil/DNSKEY alg 8, id 10330: With a TTL of 148144 the RRSIG RR can be in the cache of a non-validating resolver until 19 minutes after it expires at 2022-07-22 13:24:54+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG nro.mil/DNSKEY alg 8, id 10330: With a TTL of 148144 the RRSIG RR can be in the cache of a non-validating resolver until 19 minutes after it expires at 2022-07-22 13:24:54+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG nro.mil/DNSKEY alg 8, id 10330: With a TTL of 148144 the RRSIG RR can be in the cache of a non-validating resolver until 19 minutes after it expires at 2022-07-22 13:24:54+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG nro.mil/DNSKEY alg 8, id 31515: With a TTL of 148144 the RRSIG RR can be in the cache of a non-validating resolver until 19 minutes after it expires at 2022-07-22 13:24:54+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG nro.mil/DNSKEY alg 8, id 31515: With a TTL of 148144 the RRSIG RR can be in the cache of a non-validating resolver until 19 minutes after it expires at 2022-07-22 13:24:54+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG nro.mil/DNSKEY alg 8, id 31515: With a TTL of 148144 the RRSIG RR can be in the cache of a non-validating resolver until 19 minutes after it expires at 2022-07-22 13:24:54+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG nro.mil/DNSKEY alg 8, id 53985: With a TTL of 148144 the RRSIG RR can be in the cache of a non-validating resolver until 19 minutes after it expires at 2022-07-22 13:24:54+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG nro.mil/DNSKEY alg 8, id 53985: With a TTL of 148144 the RRSIG RR can be in the cache of a non-validating resolver until 19 minutes after it expires at 2022-07-22 13:24:54+00:00. See RFC 4035, Sec. 5.3.3.
  • RRSIG nro.mil/DNSKEY alg 8, id 53985: With a TTL of 148144 the RRSIG RR can be in the cache of a non-validating resolver until 19 minutes after it expires at 2022-07-22 13:24:54+00:00. See RFC 4035, Sec. 5.3.3.
  • nro.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • nro.mil/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • pmhajgzvcs.nro.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • nro.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • nro.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (11)
  • mil/DNSKEY (alg 8, id 50350): 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. (2608:120:c:162::234, 2608:c184:1:180::234, UDP_-_EDNS0_4096_D_KN)
  • mil/DNSKEY (alg 8, id 51621): 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. (2608:120:c:162::234, 2608:c184:1:180::234, UDP_-_EDNS0_4096_D_KN)
  • mil/DNSKEY (alg 8, id 56347): 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. (2608:120:c:162::234, 2608:c184:1:180::234, UDP_-_EDNS0_4096_D_KN)
  • nro.mil/DS (alg 8, id 10330): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • nro.mil/DS (alg 8, id 10330): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • nro.mil/DS (alg 8, id 10330): 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.
  • nro.mil/DS (alg 8, id 10330): 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.
  • nro.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • pmhajgzvcs.nro.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • nro.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • nro.mil/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