tsp.gov
Updated:
2022-01-27 12:47:38 UTC (1032 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- tsp.gov/A
- tsp.gov/MX
- tsp.gov/NS
- tsp.gov/SOA
- tsp.gov/TXT
Secure (1)
- gov/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 9799)
- NSEC3 proving non-existence of tsp.gov/DS
- gov/DNSKEY (alg 8, id 7030)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
Delegation status
Insecure (1)
- gov to tsp.gov
Secure (1)
- . to gov
Notices
Errors (14)
- NSEC3 proving non-existence of tsp.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of tsp.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- 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.82.186, 149.101.182.186)
- tsp.gov/DNSKEY: 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, UDP_-_NOEDNS_)
- tsp.gov/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (149.101.82.186, 149.101.182.185, UDP_-_EDNS0_512_D_KN)
- tsp.gov/MX: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.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, 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/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- tsp.gov/DS 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.
- tsp.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- z8jeq16vai.tsp.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
- tsp.gov/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (6)
- NSEC3 proving non-existence of tsp.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of tsp.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- tsp.gov/MX: 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.182.185, UDP_-_EDNS0_4096_D_KN)
- 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.182.185, UDP_-_EDNS0_4096_D_KN_0x20)
- tsp.gov/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
- tsp.gov/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
