fha.gov
Updated:
2020-03-30 17:15:24 UTC (1700 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- fha.gov/A
- fha.gov/AAAA
- fha.gov/NS
- fha.gov/SOA
- fha.gov/TXT
DNSKEY/DS/NSEC status
Secure (13)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 33853)
- ./DNSKEY (alg 8, id 48903)
- fha.gov/DNSKEY (alg 7, id 14570)
- fha.gov/DNSKEY (alg 7, id 3440)
- fha.gov/DNSKEY (alg 7, id 4989)
- fha.gov/DNSKEY (alg 7, id 56699)
- fha.gov/DS (alg 7, id 4989)
- fha.gov/DS (alg 7, id 4989)
- gov/DNSKEY (alg 8, id 36558)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Secure (2)
- . to gov
- gov to fha.gov
Notices
Errors (5)
- fha.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (2620:0:c91::67:250, 2620:0:c91::67:251, 2620:0:c92::167:45, 2620:0:c92::167:91)
- fha.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (2620:0:c91::67:250, 2620:0:c91::67:251, 2620:0:c92::167:45, 2620:0:c92::167:91, TCP_-_EDNS0_4096_D)
- fha.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- rvz4ehf95t.fha.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- fha.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (28)
- RRSIG fha.gov/A alg 7, id 3440: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG fha.gov/AAAA alg 7, id 3440: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG fha.gov/DNSKEY alg 7, id 3440: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG fha.gov/DNSKEY alg 7, id 3440: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG fha.gov/DNSKEY alg 7, id 3440: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG fha.gov/DNSKEY alg 7, id 3440: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG fha.gov/DNSKEY alg 7, id 4989: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG fha.gov/DNSKEY alg 7, id 4989: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG fha.gov/DNSKEY alg 7, id 4989: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG fha.gov/DNSKEY alg 7, id 4989: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG fha.gov/NS alg 7, id 3440: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG fha.gov/SOA alg 7, id 3440: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG fha.gov/TXT alg 7, id 3440: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- fha.gov/DS (alg 7, id 4989): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- fha.gov/DS (alg 7, id 4989): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- fha.gov/DS (alg 7, id 4989): 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.
- fha.gov/DS (alg 7, id 4989): 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.
- fha.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. (170.97.167.91, UDP_-_EDNS0_4096_D_K)
- fha.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. (170.97.167.91, UDP_-_EDNS0_4096_D_K)
- gov to fha.gov: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the gov zone): ns3.hud.gov, ns2.hud.gov, ns4.hud.gov, ns1.hud.gov See RFC 1034, Sec. 4.2.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): 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.
- fha.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- fha.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
- rvz4ehf95t.fha.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- fha.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
