tsp.gov
Updated:
2022-01-07 13:51:34 UTC (1054 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (4)
- tsp.gov/A
- tsp.gov/NS
- tsp.gov/NSEC3PARAM
- tsp.gov/SOA
DNSKEY/DS/NSEC status
Secure (14)
- ./DNSKEY (alg 8, id 14748)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 9799)
- gov/DNSKEY (alg 8, id 6229)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- tsp.gov/DNSKEY (alg 8, id 20238)
- tsp.gov/DNSKEY (alg 8, id 2695)
- tsp.gov/DNSKEY (alg 8, id 47764)
- tsp.gov/DNSKEY (alg 8, id 60081)
- tsp.gov/DS (alg 8, id 2695)
- tsp.gov/DS (alg 8, id 2695)
- tsp.gov/DS (alg 8, id 47764)
- tsp.gov/DS (alg 8, id 47764)
Delegation status
Secure (2)
- . to gov
- gov to tsp.gov
Notices
Errors (12)
- tsp.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (149.101.82.185)
- tsp.gov zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (149.101.82.186, 149.101.182.185, 149.101.182.186)
- tsp.gov/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.186, 149.101.182.185, 149.101.182.186, UDP_-_NOEDNS_)
- tsp.gov/AAAA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.185, UDP_-_NOEDNS_)
- tsp.gov/MX: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.185, UDP_-_NOEDNS_)
- tsp.gov/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (149.101.82.185, UDP_-_EDNS0_512_D_KN)
- tsp.gov/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.186, 149.101.182.185, 149.101.182.186, UDP_-_NOEDNS_)
- tsp.gov/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (149.101.82.185, TCP_-_EDNS0_4096_D_N)
- tsp.gov/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.185, UDP_-_NOEDNS_)
- tsp.gov/TXT: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.185, UDP_-_NOEDNS_)
- lp1witoh89.tsp.gov/A 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 (9)
- tsp.gov/DS (alg 8, id 2695): 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 2695): 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 2695): 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 2695): 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/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
