View on GitHub

DNSViz: A DNS visualization tool

uscg.mil

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

RRset statusRRset status

Bogus (2)
  • uscg.mil/SOA
  • uscg.mil/SOA
Secure (5)
  • uscg.mil/A
  • uscg.mil/MX
  • uscg.mil/NS
  • uscg.mil/SOA
  • uscg.mil/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26116)
  • ./DNSKEY (alg 8, id 42351)
  • mil/DNSKEY (alg 8, id 24363)
  • mil/DNSKEY (alg 8, id 35118)
  • mil/DNSKEY (alg 8, id 51349)
  • mil/DS (alg 8, id 51349)
  • mil/DS (alg 8, id 51349)
  • uscg.mil/DNSKEY (alg 7, id 27228)
  • uscg.mil/DNSKEY (alg 7, id 4892)
  • uscg.mil/DS (alg 7, id 27228)
  • uscg.mil/DS (alg 7, id 27228)

Delegation statusDelegation status

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

NoticesNotices

Errors (10)
  • RRSIG uscg.mil/SOA alg 7, id 4892: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • RRSIG uscg.mil/SOA alg 7, id 4892: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
  • uscg.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • j4vwmlr9ou.uscg.mil/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • uscg.mil/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • uscg.mil/NAPTR has errors; select the "Denial of existence" DNSSEC option to see them.
  • uscg.mil/TLSA has errors; select the "Denial of existence" DNSSEC option to see them.
  • uscg.mil/CAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • uscg.mil/SRV has errors; select the "Denial of existence" DNSSEC option to see them.
  • uscg.mil/PTR has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (37)
  • RRSIG uscg.mil/A alg 7, id 4892: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uscg.mil/DNSKEY alg 7, id 27228: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uscg.mil/DNSKEY alg 7, id 27228: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uscg.mil/DNSKEY alg 7, id 27228: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uscg.mil/DNSKEY alg 7, id 27228: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uscg.mil/DNSKEY alg 7, id 4892: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uscg.mil/DNSKEY alg 7, id 4892: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uscg.mil/DNSKEY alg 7, id 4892: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uscg.mil/DNSKEY alg 7, id 4892: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uscg.mil/MX alg 7, id 4892: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uscg.mil/NS alg 7, id 4892: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uscg.mil/NS alg 7, id 4892: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uscg.mil/SOA alg 7, id 4892: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uscg.mil/SOA alg 7, id 4892: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uscg.mil/SOA alg 7, id 4892: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uscg.mil/TXT alg 7, id 4892: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • mil/DS (alg 8, id 51349): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • mil/DS (alg 8, id 51349): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • 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. See RFC 4509, Sec. 3.
  • 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. See RFC 4509, Sec. 3.
  • uscg.mil/DNSKEY (alg 7, id 27228): 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. (199.211.215.69, UDP_-_EDNS0_4096_D_KN)
  • uscg.mil/DNSKEY (alg 7, id 4892): 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. (199.211.215.69, UDP_-_EDNS0_4096_D_KN)
  • uscg.mil/DS (alg 7, id 27228): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • uscg.mil/DS (alg 7, id 27228): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • uscg.mil/DS (alg 7, id 27228): 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.
  • uscg.mil/DS (alg 7, id 27228): 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.
  • uscg.mil/SOA: No response was received from the server over UDP (tried 4 times) until the 100 EDNS option was removed. See RFC 6891, Sec. 6.1.2. (199.211.216.7, UDP_-_EDNS0_512__O(100)KN)
  • uscg.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. See RFC 6891, Sec. 6.2.6. (199.211.216.7, UDP_-_EDNS0_4096_D_KN)
  • uscg.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • uscg.mil/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • uscg.mil/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • j4vwmlr9ou.uscg.mil/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • uscg.mil/NAPTR has warnings; select the "Denial of existence" DNSSEC option to see them.
  • uscg.mil/TLSA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • uscg.mil/SRV has warnings; select the "Denial of existence" DNSSEC option to see them.
  • uscg.mil/CAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • uscg.mil/PTR 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