tsp.gov
Updated:
2022-01-20 16:55:53 UTC (1040 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 9799)
- gov/DNSKEY (alg 8, id 6229)
- gov/DNSKEY (alg 8, id 7030)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- tsp.gov/DS (alg 8, id 14596)
- tsp.gov/DS (alg 8, id 2695)
- tsp.gov/DS (alg 8, id 47764)
- tsp.gov/DS (alg 8, id 51316)
Non_existent (4)
- tsp.gov/DNSKEY (alg 8, id 14596)
- tsp.gov/DNSKEY (alg 8, id 2695)
- tsp.gov/DNSKEY (alg 8, id 47764)
- tsp.gov/DNSKEY (alg 8, id 51316)
Delegation status
Bogus (1)
- gov to tsp.gov
Secure (1)
- . to gov
Notices
Errors (5)
- gov to tsp.gov: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11.
- tsp.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (149.101.82.185, 149.101.82.186, 149.101.182.185, 149.101.182.186)
- tsp.gov zone: There was an error resolving the following NS name(s) to address(es): ns-pa01.tsp.gov, ns-pa02.tsp.gov, ns-va01.tsp.gov, ns-va02.tsp.gov
- tsp.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.185, 149.101.82.186, 149.101.182.185, 149.101.182.186, UDP_-_NOEDNS_)
- tsp.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.185, 149.101.82.186, 149.101.182.185, 149.101.182.186, UDP_-_NOEDNS_)
Warnings (12)
- tsp.gov/DS (alg 8, id 14596): 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 14596): 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 14596): 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 14596): 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 47764): 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 47764): 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 47764): 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 47764): 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 51316): 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 51316): 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 51316): 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 51316): 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.
