tsp.gov
Updated:
2022-04-18 12:33:21 UTC (950 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- tsp.gov/A
- tsp.gov/MX
- tsp.gov/NS
- tsp.gov/NSEC3PARAM
- tsp.gov/SOA
- tsp.gov/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 47671)
- gov/DNSKEY (alg 8, id 2706)
- gov/DNSKEY (alg 8, id 7030)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- tsp.gov/DNSKEY (alg 8, id 42759)
- tsp.gov/DNSKEY (alg 8, id 51931)
- tsp.gov/DS (alg 8, id 51931)
- tsp.gov/DS (alg 8, id 51931)
Delegation status
Secure (2)
- . to gov
- gov to tsp.gov
Notices
Errors (3)
- ypzrlc0q3u.tsp.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- tsp.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- tsp.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
- tsp.gov/DS (alg 8, id 51931): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- tsp.gov/DS (alg 8, id 51931): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- tsp.gov/DS (alg 8, id 51931): 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.
- tsp.gov/DS (alg 8, id 51931): 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.
- ypzrlc0q3u.tsp.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- tsp.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- tsp.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
