tsptest.gov

Updated: 2022-01-19 19:30:50 UTC (1040 days ago) Go to most recent »

DNSSEC options (hide)

|?| RR types:
|?| DNSSEC algorithms:
|?| DS digest algorithms:
|?| Denial of existence:
|?| Redundant edges:
|?| Ignore RFC 8624:
|?| Ignore RFC 9276:
|?| Multi-signer:
|?| Trust anchors:
- Root zone KSK
|?| Additional trusted keys:

Notices

DNSSEC Authentication Chain

RRset status

Bogus (5)

tsptest.gov/MX
tsptest.gov/NS
tsptest.gov/NSEC3PARAM
tsptest.gov/SOA
tsptest.gov/TXT

DNSKEY/DS/NSEC status

Bogus (4)

tsptest.gov/DNSKEY (alg 7, id 15053)
tsptest.gov/DNSKEY (alg 7, id 25821)
tsptest.gov/DNSKEY (alg 8, id 26104)
tsptest.gov/DNSKEY (alg 8, id 50415)

Secure (8)

./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)
tsptest.gov/DS (alg 7, id 38208)
tsptest.gov/DS (alg 8, id 7834)

Non_existent (2)

tsptest.gov/DNSKEY (alg 7, id 38208)
tsptest.gov/DNSKEY (alg 8, id 7834)

Delegation status

Bogus (1)

gov to tsptest.gov

Secure (1)

. to gov

Notices

Errors (11)

gov to tsptest.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. (149.101.82.185, UDP_-_EDNS0_4096_D_KN)
gov to tsptest.gov: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no DS RR matched a DNSKEY with algorithm 7 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (149.101.82.185, UDP_-_EDNS0_4096_D_KN)
gov to tsptest.gov: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (149.101.82.185, UDP_-_EDNS0_4096_D_KN)
tsptest.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)
tsptest.gov/DNSKEY: 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)
tsptest.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_)
tsptest.gov/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
tsptest.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
tsptest.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
i312us6bqf.tsptest.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.
tsptest.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.

Warnings (26)

RRSIG tsptest.gov/DNSKEY alg 7, id 15053: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG tsptest.gov/DNSKEY alg 7, id 15053: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG tsptest.gov/DNSKEY alg 7, id 15053: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG tsptest.gov/DNSKEY alg 7, id 15053: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG tsptest.gov/DNSKEY alg 7, id 25821: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG tsptest.gov/DNSKEY alg 7, id 25821: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG tsptest.gov/DNSKEY alg 7, id 25821: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG tsptest.gov/DNSKEY alg 7, id 25821: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG tsptest.gov/MX alg 7, id 15053: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG tsptest.gov/NS alg 7, id 15053: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG tsptest.gov/NSEC3PARAM alg 7, id 15053: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG tsptest.gov/SOA alg 7, id 15053: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG tsptest.gov/SOA alg 7, id 15053: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG tsptest.gov/TXT alg 7, id 15053: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
tsptest.gov/DS (alg 7, id 38208): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
tsptest.gov/DS (alg 7, id 38208): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
tsptest.gov/DS (alg 7, id 38208): 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.
tsptest.gov/DS (alg 7, id 38208): 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.
tsptest.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.82.185, UDP_-_EDNS0_4096_D_KN_0x20)
tsptest.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.185, UDP_-_EDNS0_4096_D_KN)
tsptest.gov/TXT: 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.185, UDP_-_EDNS0_4096_D_KN)
tsptest.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
tsptest.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
tsptest.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
i312us6bqf.tsptest.gov/A has warnings; select the "Denial of existence" DNSSEC option to see them.
tsptest.gov/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.