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 46594)
  • gov/DNSKEY (alg 8, id 26665)
  • 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 (4)
  • 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:418:4101::80e7:401, 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: No response was received from the server over UDP (tried 14 times). See RFC 1035, Sec. 4.2. (2607:f220:418:4101::80e7:401, UDP_-_NOEDNS_)
  • hrsa.gov/NS: 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:418:4101::80e7:401, 2607:f220:41c:400::250, UDP_-_NOEDNS_)
Warnings (24)
  • 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/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/DNSKEY (alg 7, id 22563): 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. (128.231.64.1, UDP_-_EDNS0_4096_D_K)
  • hrsa.gov/DNSKEY (alg 7, id 842): 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. (128.231.64.1, UDP_-_EDNS0_4096_D_K)
  • 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/MX: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (128.231.64.1, UDP_-_EDNS0_4096_D_K)
  • 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.
  • d8zrpl2v50.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