View on GitHub

DNSViz: A DNS visualization tool

hrsa.gov

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

RRset statusRRset status

Secure (6)
  • hrsa.gov/A
  • hrsa.gov/AAAA
  • hrsa.gov/MX
  • hrsa.gov/NS
  • hrsa.gov/SOA
  • hrsa.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 42351)
  • gov/DNSKEY (alg 8, id 27306)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • hrsa.gov/DNSKEY (alg 7, id 22563)
  • hrsa.gov/DNSKEY (alg 7, id 842)
  • hrsa.gov/DS (alg 7, id 22563)
  • hrsa.gov/DS (alg 7, id 22563)

Delegation statusDelegation status

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

NoticesNotices

Errors (18)
  • hrsa.gov zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (165.112.4.230, 2607:f220:402:1801::a570:4e6)
  • hrsa.gov zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (165.112.4.230, 2607:f220:402:1801::a570:4e6)
  • hrsa.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2607:f220:410:400::ef0, 2607:f220:41c:400::250)
  • hrsa.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2607:f220:410:400::ef0, 2607:f220:41c:400::250, UDP_-_NOEDNS_)
  • hrsa.gov/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (165.112.4.230, 2607:f220:402:1801::a570:4e6, UDP_-_EDNS0_4096_D_KN)
  • hrsa.gov/AAAA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (165.112.4.230, 2607:f220:402:1801::a570:4e6, UDP_-_EDNS0_4096_D_KN)
  • hrsa.gov/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (162.99.248.37, 165.112.137.239, UDP_-_NOEDNS_)
  • hrsa.gov/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (162.99.248.37, 165.112.137.239, UDP_-_EDNS0_512_D_KN)
  • hrsa.gov/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (165.112.4.230, 2607:f220:402:1801::a570:4e6, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • hrsa.gov/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (165.112.4.230, 2607:f220:402:1801::a570:4e6, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • hrsa.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (162.99.248.37, 165.112.137.239, 2607:f220:410:400::ef0, 2607:f220:41c:400::250, UDP_-_NOEDNS_)
  • hrsa.gov/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (165.112.4.230, 2607:f220:402:1801::a570:4e6, UDP_-_EDNS0_4096_D_KN)
  • hrsa.gov/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (165.112.4.230, 2607:f220:402:1801::a570:4e6, TCP_-_EDNS0_4096_D_N)
  • hrsa.gov/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (165.112.4.230, 2607:f220:402:1801::a570:4e6, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • hrsa.gov/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (165.112.4.230, 2607:f220:402:1801::a570:4e6, UDP_-_EDNS0_4096_D_KN)
  • hrsa.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • hrsa.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • 3vqg9jaote.hrsa.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (22)
  • RRSIG hrsa.gov/A alg 7, id 842: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hrsa.gov/AAAA alg 7, id 842: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hrsa.gov/DNSKEY alg 7, id 22563: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hrsa.gov/DNSKEY alg 7, id 22563: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hrsa.gov/DNSKEY alg 7, id 842: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hrsa.gov/DNSKEY alg 7, id 842: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hrsa.gov/MX alg 7, id 842: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hrsa.gov/NS alg 7, id 842: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hrsa.gov/SOA alg 7, id 842: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG hrsa.gov/TXT alg 7, id 842: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • gov to hrsa.gov: The following NS name(s) were found in the delegation NS RRset (i.e., in the gov zone), but not in the authoritative NS RRset: ns3.nih.gov See RFC 1034, Sec. 4.2.2.
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gov/DS (alg 8, id 7698): 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.
  • gov/DS (alg 8, id 7698): 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.
  • hrsa.gov/DS (alg 7, id 22563): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • hrsa.gov/DS (alg 7, id 22563): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • hrsa.gov/DS (alg 7, id 22563): 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.
  • hrsa.gov/DS (alg 7, id 22563): 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.
  • hrsa.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • hrsa.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 3vqg9jaote.hrsa.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