RRSIG upf.edu/A alg 5, id 25467: The Signature Expiration field of the RRSIG RR (2023-09-02 07:26:05+00:00) is 3 hours, 1 minute in the past. See RFC 4035, Sec. 5.3.1.
RRSIG upf.edu/DNSKEY alg 5, id 22876: The Signature Expiration field of the RRSIG RR (2023-09-02 07:26:05+00:00) is 3 hours, 1 minute in the past. See RFC 4035, Sec. 5.3.1.
RRSIG upf.edu/DNSKEY alg 5, id 22876: The Signature Expiration field of the RRSIG RR (2023-09-02 07:26:05+00:00) is 3 hours, 1 minute in the past. See RFC 4035, Sec. 5.3.1.
RRSIG upf.edu/DNSKEY alg 5, id 22876: The Signature Expiration field of the RRSIG RR (2023-09-02 07:26:05+00:00) is 3 hours, 1 minute in the past. See RFC 4035, Sec. 5.3.1.
RRSIG upf.edu/DNSKEY alg 5, id 25467: The Signature Expiration field of the RRSIG RR (2023-09-02 07:26:05+00:00) is 3 hours, 1 minute in the past. See RFC 4035, Sec. 5.3.1.
RRSIG upf.edu/DNSKEY alg 5, id 25467: The Signature Expiration field of the RRSIG RR (2023-09-02 07:26:05+00:00) is 3 hours, 1 minute in the past. See RFC 4035, Sec. 5.3.1.
RRSIG upf.edu/DNSKEY alg 5, id 25467: The Signature Expiration field of the RRSIG RR (2023-09-02 07:26:05+00:00) is 3 hours, 1 minute in the past. See RFC 4035, Sec. 5.3.1.
RRSIG upf.edu/MX alg 5, id 25467: The Signature Expiration field of the RRSIG RR (2023-09-02 07:26:05+00:00) is 3 hours, 1 minute in the past. See RFC 4035, Sec. 5.3.1.
RRSIG upf.edu/NS alg 5, id 25467: The Signature Expiration field of the RRSIG RR (2023-09-02 07:26:05+00:00) is 3 hours, 1 minute in the past. See RFC 4035, Sec. 5.3.1.
RRSIG upf.edu/SOA alg 5, id 25467: The Signature Expiration field of the RRSIG RR (2023-09-02 07:26:05+00:00) is 3 hours, 1 minute in the past. See RFC 4035, Sec. 5.3.1.
RRSIG upf.edu/TXT alg 5, id 25467: The Signature Expiration field of the RRSIG RR (2023-09-02 07:26:05+00:00) is 3 hours, 1 minute in the past. See RFC 4035, Sec. 5.3.1.
edu to upf.edu: 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. (84.89.128.13, 84.89.128.14, 84.89.155.14, 84.89.155.15, TCP_-_EDNS0_4096_D_KN)
upf.edu zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (84.89.128.17)
upf.edu/DNSKEY: No response was received from the server over UDP (tried 16 times). See RFC 1035, Sec. 4.2. (84.89.128.17, UDP_-_EDNS0_4096_D_KN)
upf.edu/SOA: No response was received from the server over TCP (tried 4 times). See RFC 1035, Sec. 4.2. (84.89.128.17, TCP_-_EDNS0_4096_D_N)
upf.edu/TXT: There was an error communicating with the server over TCP (UNKNOWN). See RFC 1035, Sec. 4.2. (84.89.128.17, TCP_-_EDNS0_4096_D_KN)
upf.edu/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
upf.edu/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
upf.edu/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
f6ze4oj8sh.upf.edu/A has errors; select the "Denial of existence" DNSSEC option to see them.
upf.edu/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (28)
RRSIG upf.edu/A alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG upf.edu/A alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG upf.edu/DNSKEY alg 5, id 22876: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG upf.edu/DNSKEY alg 5, id 22876: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG upf.edu/DNSKEY alg 5, id 22876: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG upf.edu/DNSKEY alg 5, id 22876: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG upf.edu/DNSKEY alg 5, id 22876: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG upf.edu/DNSKEY alg 5, id 22876: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG upf.edu/DNSKEY alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG upf.edu/DNSKEY alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG upf.edu/DNSKEY alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG upf.edu/DNSKEY alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG upf.edu/DNSKEY alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG upf.edu/DNSKEY alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG upf.edu/MX alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG upf.edu/MX alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG upf.edu/NS alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG upf.edu/NS alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG upf.edu/SOA alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG upf.edu/SOA alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG upf.edu/TXT alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG upf.edu/TXT alg 5, id 25467: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
edu to upf.edu: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the edu zone): ns1.upf.edu See RFC 1034, Sec. 4.2.2.
upf.edu/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
upf.edu/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
upf.edu/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
f6ze4oj8sh.upf.edu/A has warnings; select the "Denial of existence" DNSSEC option to see them.
upf.edu/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.