hrsa.gov
Updated:
2020-06-04 19:00:16 UTC (1431 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- hrsa.gov/A
- hrsa.gov/AAAA
- hrsa.gov/MX
- hrsa.gov/NS
- hrsa.gov/SOA
- hrsa.gov/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 48903)
- gov/DNSKEY (alg 8, id 40176)
- 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 status
Secure (2)
- . to gov
- gov to hrsa.gov
Notices
Errors (5)
- hrsa.gov zone: The server(s) were not responsive to queries over TCP. (165.112.4.230, 2607:f220:402:1801::a570:4e6)
- hrsa.gov zone: The server(s) were not responsive to queries over UDP. (2607:f220:418:4101::80e7:401)
- hrsa.gov/A: No response was received from the server over UDP (tried 13 times). (2607:f220:418:4101::80e7:401, UDP_-_EDNS0_4096_D)
- hrsa.gov/NS: No response was received from the server over UDP (tried 11 times). (2607:f220:418:4101::80e7:401, UDP_-_EDNS0_4096_D)
- hrsa.gov/SOA: No response was received from the server over TCP (tried 3 times). (165.112.4.230, 2607:f220:402:1801::a570:4e6, TCP_-_EDNS0_4096_D)
Warnings (24)
- RRSIG hrsa.gov/A alg 7, id 842: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1).
- RRSIG hrsa.gov/AAAA alg 7, id 842: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1).
- RRSIG hrsa.gov/DNSKEY alg 7, id 22563: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1).
- RRSIG hrsa.gov/DNSKEY alg 7, id 22563: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1).
- RRSIG hrsa.gov/DNSKEY alg 7, id 842: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1).
- RRSIG hrsa.gov/DNSKEY alg 7, id 842: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1).
- RRSIG hrsa.gov/MX alg 7, id 842: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1).
- RRSIG hrsa.gov/NS alg 7, id 842: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1).
- RRSIG hrsa.gov/SOA alg 7, id 842: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1).
- RRSIG hrsa.gov/TXT alg 7, id 842: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1).
- gov/DS (alg 8, id 7698): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
- gov/DS (alg 8, id 7698): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
- 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.
- 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.
- 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. (2607:f220:410:400::ef0, 2607:f220:41c:400::250, UDP_-_EDNS0_4096_D_K)
- 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. (2607:f220:410:400::ef0, 2607:f220:41c:400::250, UDP_-_EDNS0_4096_D_K)
- hrsa.gov/DS (alg 7, id 22563): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
- hrsa.gov/DS (alg 7, id 22563): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
- 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.
- 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.
- 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. (2607:f220:410:400::ef0, 2607:f220:41c:400::250, UDP_-_EDNS0_4096_D_K)
- 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. (2607:f220:410:400::ef0, 2607:f220:41c:400::250, UDP_-_EDNS0_4096_D_K)
- 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. (2607:f220:410:400::ef0, 2607:f220:41c:400::250, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_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. (2607:f220:410:400::ef0, 2607:f220:41c:400::250, UDP_-_EDNS0_4096_D_K)
JavaScript is required to make the graph below interactive.
