tsp.gov
Updated:
2021-09-16 15:41:32 UTC (1170 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (7)
- tsp.gov/A
- tsp.gov/MX
- tsp.gov/NS
- tsp.gov/NSEC3PARAM
- tsp.gov/NSEC3PARAM
- tsp.gov/SOA
- tsp.gov/TXT
DNSKEY/DS/NSEC status
Secure (14)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26838)
- gov/DNSKEY (alg 8, id 57735)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- tsp.gov/DNSKEY (alg 8, id 13239)
- tsp.gov/DNSKEY (alg 8, id 2695)
- tsp.gov/DNSKEY (alg 8, id 47764)
- tsp.gov/DNSKEY (alg 8, id 55821)
- tsp.gov/DNSKEY (alg 8, id 58215)
- 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 (10)
- 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, 149.101.82.186, 149.101.182.186, UDP_-_EDNS0_4096_D_KN, UDP_-_NOEDNS_)
- tsp.gov/MX: No response was received from the server over UDP (tried 15 times). See RFC 1035, Sec. 4.2. (149.101.182.185, UDP_-_EDNS0_4096_D_N)
- tsp.gov/NSEC3PARAM: 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.186, UDP_-_NOEDNS_)
- tsp.gov/SOA: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.182.186, TCP_-_EDNS0_4096_D_KN)
- 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, 149.101.82.186, 149.101.182.186, 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, 149.101.82.186, 149.101.182.186, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
- tsp.gov/TXT: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.185, 149.101.82.186, 149.101.182.186, TCP_-_EDNS0_4096_D_KN)
- 60wf7jnms2.tsp.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- tsp.gov/AAAA 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 (12)
- 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/SOA: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (149.101.182.185, UDP_-_EDNS0_4096_D_KN_0x20)
- 60wf7jnms2.tsp.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- tsp.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- tsp.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
