jct.gov
Updated:
2021-06-29 09:37:58 UTC (1247 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- jct.gov/A
- jct.gov/MX
- jct.gov/NS
- jct.gov/SOA
- jct.gov/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 14631)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26838)
- gov/DNSKEY (alg 8, id 48498)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- jct.gov/DNSKEY (alg 13, id 1745)
- jct.gov/DNSKEY (alg 13, id 61960)
- jct.gov/DS (alg 13, id 61960)
- jct.gov/DS (alg 13, id 61960)
Delegation status
Secure (2)
- . to gov
- gov to jct.gov
Notices
Errors (3)
- jct.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:502:4612::91)
- jct.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:502:4612::91, UDP_-_NOEDNS_)
- jct.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:502:4612::91, UDP_-_NOEDNS_)
Warnings (4)
- jct.gov/DS (alg 13, id 61960): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- jct.gov/DS (alg 13, id 61960): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- jct.gov/DS (alg 13, id 61960): 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.
- jct.gov/DS (alg 13, id 61960): 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.
