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 (7)
  • hrsa.gov/A
  • hrsa.gov/AAAA
  • hrsa.gov/MX
  • hrsa.gov/NS
  • hrsa.gov/NSEC3PARAM
  • hrsa.gov/SOA
  • hrsa.gov/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 11019)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • gov/DNSKEY (alg 8, id 50011)
  • gov/DNSKEY (alg 8, id 7698)
  • gov/DS (alg 8, id 7698)
  • hrsa.gov/DNSKEY (alg 8, id 15885)
  • hrsa.gov/DNSKEY (alg 8, id 45939)
  • hrsa.gov/DNSKEY (alg 8, id 47719)
  • hrsa.gov/DS (alg 8, id 47719)
  • hrsa.gov/DS (alg 8, id 47719)

Delegation statusDelegation status

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

NoticesNotices

Errors (6)
  • hrsa.gov/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2607:f220:404:101::80e7:80fb, UDP_-_EDNS0_512_D_KN)
  • hrsa.gov/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2607:f220:404:101::80e7:80fb, UDP_-_EDNS0_512_D_KN)
  • hrsa.gov/TXT: No response was received from the server over TCP (tried 5 times). See RFC 1035, Sec. 4.2. (2607:f220:404:101::80e7:80fb, TCP_-_EDNS0_4096_D_N)
  • hrsa.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • o65k9fzsdg.hrsa.gov/A 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.
Warnings (26)
  • gov to hrsa.gov: Authoritative AAAA records exist for ns.nih.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • gov to hrsa.gov: Authoritative AAAA records exist for ns2.nih.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • gov to hrsa.gov: Authoritative AAAA records exist for ns3.nih.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • gov/DS (alg 8, id 7698): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:200::b, UDP_-_EDNS0_4096_D_KN)
  • gov/DS (alg 8, id 7698): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2001:500:200::b, UDP_-_EDNS0_4096_D_KN)
  • hrsa.gov/A: 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. (2607:f220:410:405::a263:f9ef, 2607:f220:41c:400::250, UDP_-_EDNS0_4096_D_KN)
  • hrsa.gov/AAAA: 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.128.251, 2607:f220:410:405::a263:f9ef, 2607:f220:41c:400::250, UDP_-_EDNS0_4096_D_KN)
  • hrsa.gov/DNSKEY (alg 8, id 15885): 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. (2607:f220:404:101::80e7:80fb, 2607:f220:410:405::a263:f9ef, 2607:f220:41c:400::250, UDP_-_EDNS0_4096_D_KN)
  • hrsa.gov/DNSKEY (alg 8, id 45939): 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. (2607:f220:404:101::80e7:80fb, 2607:f220:410:405::a263:f9ef, 2607:f220:41c:400::250, UDP_-_EDNS0_4096_D_KN)
  • hrsa.gov/DNSKEY (alg 8, id 47719): 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. (2607:f220:404:101::80e7:80fb, 2607:f220:410:405::a263:f9ef, 2607:f220:41c:400::250, UDP_-_EDNS0_4096_D_KN)
  • hrsa.gov/DS (alg 8, id 47719): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • hrsa.gov/DS (alg 8, id 47719): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • hrsa.gov/DS (alg 8, id 47719): 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 8, id 47719): 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 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (2607:f220:404:101::80e7:80fb, UDP_-_EDNS0_4096_D_KN)
  • hrsa.gov/MX: 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. (2607:f220:410:405::a263:f9ef, 2607:f220:41c:400::250, UDP_-_EDNS0_4096_D_KN)
  • hrsa.gov/NS: No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (2607:f220:404:101::80e7:80fb, UDP_-_EDNS0_4096_D_KN)
  • hrsa.gov/NS: 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. (2607:f220:410:405::a263:f9ef, 2607:f220:41c:400::250, UDP_-_EDNS0_4096_D_KN)
  • hrsa.gov/NSEC3PARAM: No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (2607:f220:404:101::80e7:80fb, UDP_-_EDNS0_4096_D_KN)
  • hrsa.gov/NSEC3PARAM: 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. (2607:f220:410:405::a263:f9ef, 2607:f220:41c:400::250, UDP_-_EDNS0_4096_D_KN)
  • hrsa.gov/SOA: 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. (2607:f220:404:101::80e7:80fb, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • hrsa.gov/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. (2607:f220:410:405::a263:f9ef, 2607:f220:41c:400::250, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • hrsa.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. (2607:f220:410:405::a263:f9ef, 2607:f220:41c:400::250, UDP_-_EDNS0_4096_D_KN)
  • 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.
  • o65k9fzsdg.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