huduser.gov
Updated:
2023-03-13 18:52:50 UTC (408 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- huduser.gov/A
- huduser.gov/MX
- huduser.gov/NS
- huduser.gov/SOA
- huduser.gov/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 951)
- gov/DNSKEY (alg 8, id 24250)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- huduser.gov/DNSKEY (alg 5, id 37309)
- huduser.gov/DNSKEY (alg 5, id 39465)
- huduser.gov/DNSKEY (alg 8, id 28312)
- huduser.gov/DNSKEY (alg 8, id 49629)
- huduser.gov/DS (alg 8, id 28312)
Delegation status
Secure (2)
- . to gov
- gov to huduser.gov
Notices
Warnings (18)
- RRSIG huduser.gov/A alg 5, id 39465: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
- RRSIG huduser.gov/DNSKEY alg 5, id 37309: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
- RRSIG huduser.gov/DNSKEY alg 5, id 37309: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
- RRSIG huduser.gov/DNSKEY alg 5, id 37309: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
- RRSIG huduser.gov/DNSKEY alg 5, id 37309: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
- RRSIG huduser.gov/DNSKEY alg 5, id 39465: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
- RRSIG huduser.gov/DNSKEY alg 5, id 39465: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
- RRSIG huduser.gov/DNSKEY alg 5, id 39465: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
- RRSIG huduser.gov/DNSKEY alg 5, id 39465: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
- RRSIG huduser.gov/MX alg 5, id 39465: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
- RRSIG huduser.gov/NS alg 5, id 39465: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
- RRSIG huduser.gov/SOA alg 5, id 39465: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
- RRSIG huduser.gov/TXT alg 5, id 39465: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
- huduser.gov/DNSKEY (alg 5, id 37309): 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. (2600:2000:2210::16, 2600:2000:2220::16, 2600:2000:2230::16, 2600:2000:2240::16, UDP_-_EDNS0_4096_D_KN)
- huduser.gov/DNSKEY (alg 5, id 39465): 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. (2600:2000:2210::16, 2600:2000:2220::16, 2600:2000:2230::16, 2600:2000:2240::16, UDP_-_EDNS0_4096_D_KN)
- huduser.gov/DNSKEY (alg 8, id 28312): 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. (2600:2000:2210::16, 2600:2000:2220::16, 2600:2000:2230::16, 2600:2000:2240::16, UDP_-_EDNS0_4096_D_KN)
- huduser.gov/DNSKEY (alg 8, id 49629): 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. (2600:2000:2210::16, 2600:2000:2220::16, 2600:2000:2230::16, 2600:2000:2240::16, UDP_-_EDNS0_4096_D_KN)
- huduser.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. (2600:2000:2210::16, 2600:2000:2220::16, 2600:2000:2230::16, 2600:2000:2240::16, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
