View on GitHub

DNSViz: A DNS visualization tool

uscg.gov

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

RRset statusRRset status

Bogus (5)
  • uscg.gov/MX
  • uscg.gov/NS
  • uscg.gov/NSEC3PARAM
  • uscg.gov/SOA
  • uscg.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Bogus (2)
  • uscg.gov/DNSKEY (alg 7, id 27249)
  • uscg.gov/DNSKEY (alg 7, id 58685)
Secure (6)
  • ./DNSKEY (alg 8, id 20038)
  • ./DNSKEY (alg 8, id 20326)
  • gov/DNSKEY (alg 13, id 2536)
  • gov/DNSKEY (alg 13, id 35496)
  • gov/DS (alg 13, id 2536)
  • uscg.gov/DS (alg 7, id 40854)
Non_existent (1)
  • uscg.gov/DNSKEY (alg 7, id 40854)

Delegation statusDelegation status

Bogus (1)
  • gov to uscg.gov
Secure (1)
  • . to gov

NoticesNotices

Errors (8)
  • gov to uscg.gov: 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. (152.121.2.19, 152.121.33.3, 152.121.50.3, UDP_-_EDNS0_4096_D_KN)
  • gov to uscg.gov: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no DS RR matched a DNSKEY with algorithm 7 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (152.121.2.19, 152.121.33.3, 152.121.50.3, UDP_-_EDNS0_4096_D_KN)
  • uscg.gov/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
  • uscg.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • uscg.gov/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • uscg.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • uscg.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • gw9su.sie7f.uscg.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (21)
  • RRSIG uscg.gov/DNSKEY alg 7, id 27249: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uscg.gov/DNSKEY alg 7, id 27249: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uscg.gov/DNSKEY alg 7, id 27249: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uscg.gov/DNSKEY alg 7, id 27249: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uscg.gov/DNSKEY alg 7, id 58685: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uscg.gov/DNSKEY alg 7, id 58685: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uscg.gov/DNSKEY alg 7, id 58685: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uscg.gov/DNSKEY alg 7, id 58685: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uscg.gov/MX alg 7, id 58685: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uscg.gov/NS alg 7, id 58685: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uscg.gov/NSEC3PARAM alg 7, id 58685: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uscg.gov/SOA alg 7, id 58685: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG uscg.gov/TXT alg 7, id 58685: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • uscg.gov/TXT: 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. (152.121.50.3, UDP_-_EDNS0_4096_D_KN)
  • uscg.gov/CDS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • uscg.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • uscg.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • uscg.gov/CDNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • uscg.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • uscg.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gw9su.sie7f.uscg.gov/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