republicanleader.gov
Updated:
2021-04-14 10:11:51 UTC (1318 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (3)
- republicanleader.gov/A
- republicanleader.gov/NS
- republicanleader.gov/SOA
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 14631)
- ./DNSKEY (alg 8, id 20326)
- gov/DNSKEY (alg 8, id 27306)
- gov/DNSKEY (alg 8, id 48498)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- republicanleader.gov/DNSKEY (alg 13, id 5202)
- republicanleader.gov/DNSKEY (alg 13, id 52541)
- republicanleader.gov/DS (alg 13, id 52541)
- republicanleader.gov/DS (alg 13, id 52541)
Delegation status
Secure (2)
- . to gov
- gov to republicanleader.gov
Notices
Errors (1)
- gov/DS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:7fe::53, UDP_-_NOEDNS_)
Warnings (4)
- republicanleader.gov/DS (alg 13, id 52541): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- republicanleader.gov/DS (alg 13, id 52541): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- republicanleader.gov/DS (alg 13, id 52541): 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.
- republicanleader.gov/DS (alg 13, id 52541): 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.
