exploretsp.gov

Updated: 2022-01-19 19:31:47 UTC (1039 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 (4)

exploretsp.gov/A
exploretsp.gov/NS
exploretsp.gov/SOA
exploretsp.gov/TXT

DNSKEY/DS/NSEC status

Bogus (4)

exploretsp.gov/DNSKEY (alg 8, id 20676)
exploretsp.gov/DNSKEY (alg 8, id 35704)
exploretsp.gov/DNSKEY (alg 8, id 41992)
exploretsp.gov/DNSKEY (alg 8, id 62208)

Secure (8)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 9799)
exploretsp.gov/DS (alg 8, id 15307)
exploretsp.gov/DS (alg 8, id 5224)
gov/DNSKEY (alg 8, id 6229)
gov/DNSKEY (alg 8, id 7030)
gov/DNSKEY (alg 8, id 7698)
gov/DS (alg 8, id 7698)

Non_existent (2)

exploretsp.gov/DNSKEY (alg 8, id 15307)
exploretsp.gov/DNSKEY (alg 8, id 5224)

Delegation status

Bogus (1)

gov to exploretsp.gov

Secure (1)

. to gov

Notices

Errors (12)

exploretsp.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)
exploretsp.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_)
exploretsp.gov/MX: No response was received from the server over UDP (tried 14 times). See RFC 1035, Sec. 4.2. (149.101.82.185, UDP_-_EDNS0_4096_D_KN)
exploretsp.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_)
exploretsp.gov/NSEC3PARAM: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (149.101.82.185, UDP_-_NOEDNS_)
exploretsp.gov/SOA: No response was received from the server over TCP (tried 7 times). See RFC 1035, Sec. 4.2. (149.101.82.185, TCP_-_EDNS0_4096_D_KN_0x20)
exploretsp.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_)
gov to exploretsp.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, TCP_-_EDNS0_4096_D_KN)
gov to exploretsp.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, TCP_-_EDNS0_4096_D_KN)
exploretsp.gov/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
exploretsp.gov/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
jbiwn3pm5l.exploretsp.gov/A has errors; select the "Denial of existence" DNSSEC option to see them.

Warnings (7)

exploretsp.gov/A: 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)
exploretsp.gov/DNSKEY (alg 8, id 20676): 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)
exploretsp.gov/DNSKEY (alg 8, id 35704): 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)
exploretsp.gov/DNSKEY (alg 8, id 41992): 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)
exploretsp.gov/DNSKEY (alg 8, id 62208): 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)
exploretsp.gov/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
exploretsp.gov/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.