fema.gov
Updated:
2020-10-29 13:43:09 UTC (1490 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 20326)
- ./DNSKEY (alg 8, id 26116)
- fema.gov/DNSKEY (alg 8, id 27658)
- fema.gov/DNSKEY (alg 8, id 48426)
- fema.gov/DNSKEY (alg 8, id 60907)
- fema.gov/DS (alg 8, id 60907)
- fema.gov/DS (alg 8, id 60907)
- gov/DNSKEY (alg 8, id 15489)
- 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 fema.gov
Notices
Errors (3)
- gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2620:74:28::2:30)
- eujlgqz6y2.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 (14)
- fema.gov/DS (alg 8, id 60907): 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 60907): 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 60907): 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 60907): 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): 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.
- gov/DS (alg 8, id 7698): 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. (2001:500:12::d0d, UDP_-_EDNS0_4096_D_K)
- gov/DS (alg 8, id 7698): 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. (2001:500:12::d0d, UDP_-_EDNS0_4096_D_K)
- gov/DS (alg 8, id 7698): 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. (2001:500:12::d0d, UDP_-_EDNS0_4096_D_K)
- gov/DS (alg 8, id 7698): 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. (2001:500:12::d0d, UDP_-_EDNS0_4096_D_K)
- eujlgqz6y2.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.
