tsc.gov
Updated:
2023-09-05 12:21:31 UTC (443 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- tsc.gov/A
- tsc.gov/MX
- tsc.gov/NS
- tsc.gov/NSEC3PARAM
- tsc.gov/SOA
- tsc.gov/TXT
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 11019)
- ./DNSKEY (alg 8, id 20326)
- gov/DNSKEY (alg 8, id 40921)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- tsc.gov/DNSKEY (alg 8, id 10222)
- tsc.gov/DNSKEY (alg 8, id 12018)
- tsc.gov/DS (alg 8, id 10222)
- tsc.gov/DS (alg 8, id 10222)
Delegation status
Secure (2)
- . to gov
- gov to tsc.gov
Notices
Errors (3)
- tsc.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- 6jnd9z2yqu.tsc.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- tsc.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
- tsc.gov/DS (alg 8, id 10222): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- tsc.gov/DS (alg 8, id 10222): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- tsc.gov/DS (alg 8, id 10222): 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.
- tsc.gov/DS (alg 8, id 10222): 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.
- tsc.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- 6jnd9z2yqu.tsc.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- tsc.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
