tsp.gov
Updated:
2021-11-10 02:22:14 UTC (1114 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (8)
- tsp.gov/A
- tsp.gov/MX
- tsp.gov/NS
- tsp.gov/NSEC3PARAM
- tsp.gov/NSEC3PARAM
- tsp.gov/NSEC3PARAM
- tsp.gov/SOA
- tsp.gov/TXT
DNSKEY/DS/NSEC status
Secure (13)
- ./DNSKEY (alg 8, id 14748)
- ./DNSKEY (alg 8, id 20326)
- gov/DNSKEY (alg 8, id 6229)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- tsp.gov/DNSKEY (alg 8, id 2695)
- tsp.gov/DNSKEY (alg 8, id 47764)
- tsp.gov/DNSKEY (alg 8, id 50418)
- tsp.gov/DNSKEY (alg 8, id 57156)
- 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 (6)
- tsp.gov zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (149.101.82.185, 149.101.182.185, 149.101.182.186)
- tsp.gov/NS: No response was received from the server over TCP (tried 7 times). See RFC 1035, Sec. 4.2. (149.101.82.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.182.185, 149.101.182.186, TCP_-_EDNS0_4096_D_N)
- 0n7x84qalj.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 until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (149.101.82.186, UDP_-_EDNS0_4096_D_KN)
- 0n7x84qalj.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.
