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

Secure (3)
  • uscg.gov/NS
  • uscg.gov/SOA
  • uscg.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (13)
  • ./DNSKEY (alg 8, id 14631)
  • ./DNSKEY (alg 8, id 20326)
  • gov/DNSKEY (alg 8, id 48498)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • uscg.gov/DNSKEY (alg 7, id 32270)
  • uscg.gov/DNSKEY (alg 7, id 32582)
  • uscg.gov/DNSKEY (alg 7, id 64494)
  • uscg.gov/DNSKEY (alg 7, id 8508)
  • uscg.gov/DS (alg 7, id 64494)
  • uscg.gov/DS (alg 7, id 64494)
  • uscg.gov/DS (alg 7, id 8508)
  • uscg.gov/DS (alg 7, id 8508)

Delegation statusDelegation status

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

NoticesNotices

Errors (11)
  • uscg.gov/DNSKEY: No response was received from the server over TCP (tried 6 times). See RFC 1035, Sec. 4.2. (152.121.33.3, TCP_-_EDNS0_4096_D_KN)
  • uscg.gov/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (152.121.50.3, UDP_-_EDNS0_4096_D_KN)
  • uscg.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (152.121.33.3, UDP_-_NOEDNS_)
  • uscg.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (152.121.2.19, TCP_-_EDNS0_4096_D_N)
  • uscg.gov/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (152.121.33.3, UDP_-_NOEDNS__0x20)
  • fs268palez.uscg.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • uscg.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • uscg.gov/DNSKEY 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/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.
Warnings (35)
  • RRSIG uscg.gov/DNSKEY alg 7, id 32270: 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 32270: 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 32270: 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 32270: 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 32582: 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 32582: 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 32582: 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 32582: 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 64494: 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 64494: 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 64494: 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 64494: 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 8508: 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 8508: 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 8508: 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 8508: 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 32270: 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 32582: 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 32270: 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 32582: 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 32270: 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 32582: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • uscg.gov/DS (alg 7, id 64494): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • uscg.gov/DS (alg 7, id 64494): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • uscg.gov/DS (alg 7, id 64494): 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.gov/DS (alg 7, id 64494): 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.gov/DS (alg 7, id 8508): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • uscg.gov/DS (alg 7, id 8508): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • uscg.gov/DS (alg 7, id 8508): 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.gov/DS (alg 7, id 8508): 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.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.
  • uscg.gov/MX 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.

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