fema.gov
Updated:
2021-04-02 22:43:51 UTC (1334 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (8)
- fema.gov/A
- fema.gov/A
- fema.gov/AAAA
- fema.gov/AAAA
- fema.gov/MX
- fema.gov/NS
- fema.gov/SOA
- fema.gov/TXT
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 14631)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 42351)
- fema.gov/DNSKEY (alg 8, id 20066)
- fema.gov/DNSKEY (alg 8, id 22753)
- fema.gov/DNSKEY (alg 8, id 63796)
- fema.gov/DS (alg 8, id 20066)
- fema.gov/DS (alg 8, id 20066)
- gov/DNSKEY (alg 8, id 27306)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Secure (2)
- . to gov
- gov to fema.gov
Notices
Errors (3)
- ./DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (192.112.36.4, UDP_-_EDNS0_512_D_KN)
- uctrhm91ej.fema.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- fema.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (6)
- fema.gov/DS (alg 8, id 20066): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- fema.gov/DS (alg 8, id 20066): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- fema.gov/DS (alg 8, id 20066): 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.
- fema.gov/DS (alg 8, id 20066): 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.
- uctrhm91ej.fema.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- fema.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
