uscp.gov
Updated:
2021-04-14 13:47:17 UTC (1318 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (4)
- uscp.gov/MX
- uscp.gov/NS
- uscp.gov/SOA
- uscp.gov/TXT
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)
- uscp.gov/DNSKEY (alg 8, id 1081)
- uscp.gov/DNSKEY (alg 8, id 40044)
- uscp.gov/DS (alg 8, id 1081)
- uscp.gov/DS (alg 8, id 1081)
Delegation status
Secure (2)
- . to gov
- gov to uscp.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)
- uscp.gov/DS (alg 8, id 1081): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- uscp.gov/DS (alg 8, id 1081): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- uscp.gov/DS (alg 8, id 1081): 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.
- uscp.gov/DS (alg 8, id 1081): 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.
