emergency-federal-register.gov
Updated:
2023-03-10 17:47:45 UTC (623 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (4)
- emergency-federal-register.gov/A
- emergency-federal-register.gov/NS
- emergency-federal-register.gov/SOA
- emergency-federal-register.gov/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 951)
- emergency-federal-register.gov/DNSKEY (alg 8, id 16154)
- emergency-federal-register.gov/DNSKEY (alg 8, id 49545)
- emergency-federal-register.gov/DNSKEY (alg 8, id 8439)
- emergency-federal-register.gov/DS (alg 8, id 16154)
- emergency-federal-register.gov/DS (alg 8, id 16154)
- gov/DNSKEY (alg 8, id 24250)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Secure (2)
- . to gov
- gov to emergency-federal-register.gov
Notices
Warnings (4)
- emergency-federal-register.gov/DS (alg 8, id 16154): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- emergency-federal-register.gov/DS (alg 8, id 16154): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- emergency-federal-register.gov/DS (alg 8, id 16154): 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.
- emergency-federal-register.gov/DS (alg 8, id 16154): 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.
JavaScript is required to make the graph below interactive.
