tsc.gov
Updated:
2023-11-10 22:26:46 UTC (159 days ago)
Update now
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 (16)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46780)
- gov/DNSKEY (alg 8, id 10104)
- gov/DNSKEY (alg 8, id 49735)
- gov/DNSKEY (alg 8, id 64280)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 64280)
- gov/DS (alg 8, id 7698)
- tsc.gov/DNSKEY (alg 8, id 10222)
- tsc.gov/DNSKEY (alg 8, id 19341)
- tsc.gov/DNSKEY (alg 8, id 5790)
- tsc.gov/DNSKEY (alg 8, id 6919)
- tsc.gov/DS (alg 8, id 10222)
- tsc.gov/DS (alg 8, id 10222)
- tsc.gov/DS (alg 8, id 6919)
- tsc.gov/DS (alg 8, id 6919)
Delegation status
Secure (2)
- . to gov
- gov to tsc.gov
Notices
Warnings (8)
- tsc.gov/DS (alg 8, id 10222): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
- tsc.gov/DS (alg 8, id 10222): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
- 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.
- 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.
- tsc.gov/DS (alg 8, id 6919): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
- tsc.gov/DS (alg 8, id 6919): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
- tsc.gov/DS (alg 8, id 6919): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.
- tsc.gov/DS (alg 8, id 6919): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset.
JavaScript is required to make the graph below interactive.
