911.gov
Updated:
2020-11-21 15:06:23 UTC (1461 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- 911.gov/A
- 911.gov/AAAA
- 911.gov/NS
- 911.gov/SOA
- 911.gov/TXT
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26116)
- 911.gov/DNSKEY (alg 8, id 15276)
- 911.gov/DNSKEY (alg 8, id 25968)
- 911.gov/DNSKEY (alg 8, id 4735)
- 911.gov/DS (alg 8, id 32836)
- 911.gov/DS (alg 8, id 4735)
- 911.gov/DS (alg 8, id 4735)
- gov/DNSKEY (alg 8, id 15489)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Non_existent (1)
- 911.gov/DNSKEY (alg 8, id 32836)
Delegation status
Secure (2)
- . to gov
- gov to 911.gov
Notices
Errors (3)
- 911.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- sjn57hgi1e.911.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- 911.gov/MX has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (18)
- 911.gov/DS (alg 8, id 32836): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- 911.gov/DS (alg 8, id 32836): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- 911.gov/DS (alg 8, id 32836): 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.
- 911.gov/DS (alg 8, id 32836): 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.
- 911.gov/DS (alg 8, id 4735): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- 911.gov/DS (alg 8, id 4735): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- 911.gov/DS (alg 8, id 4735): 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.
- 911.gov/DS (alg 8, id 4735): 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 to 911.gov: Authoritative AAAA records exist for edns1.dot.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- gov to 911.gov: Authoritative AAAA records exist for edns2.dot.gov, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- gov to 911.gov: Authoritative AAAA records exist for edns3.dot.gov, but there are no corresponding AAAA glue records. 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.
- 911.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- sjn57hgi1e.911.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- 911.gov/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
