hrsa.gov
Updated:
2023-07-07 19:49:40 UTC (506 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (7)
- hrsa.gov/A
- hrsa.gov/AAAA
- hrsa.gov/MX
- hrsa.gov/NS
- hrsa.gov/SOA
- hrsa.gov/SOA
- hrsa.gov/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./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 10345)
- hrsa.gov/DNSKEY (alg 8, id 45939)
- hrsa.gov/DS (alg 8, id 10345)
- hrsa.gov/DS (alg 8, id 10345)
Delegation status
Secure (2)
- . to gov
- gov to hrsa.gov
Notices
Errors (3)
- hrsa.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (2607:f220:404:101::80e7:80fb)
- 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/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (2607:f220:404:101::80e7:80fb, TCP_-_EDNS0_4096_D_N)
Warnings (13)
- 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.
- 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. (2607:f220:410:405::a263:f9ef, 2607:f220:41c:400::250, UDP_-_EDNS0_4096_D_KN)
- hrsa.gov/DS (alg 8, id 10345): 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 10345): 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 10345): 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 10345): 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 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 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 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, 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)
JavaScript is required to make the graph below interactive.
