upf.edu
Updated:
2023-05-14 06:43:00 UTC (2 years ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (5)
- upf.edu/A
- upf.edu/MX
- upf.edu/NS
- upf.edu/SOA
- upf.edu/TXT
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 60955)
- edu/DNSKEY (alg 8, id 28065)
- edu/DNSKEY (alg 8, id 30503)
- edu/DS (alg 8, id 28065)
- upf.edu/DS (alg 5, id 22876)
Non_existent (2)
- upf.edu/DNSKEY (alg 5, id 22876)
- upf.edu/DNSKEY (alg 5, id 25467)
Delegation status
Bogus (1)
- edu to upf.edu
Secure (1)
- . to edu
Notices
Errors (17)
- 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.
- upf.edu zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (84.89.128.12, 84.89.128.13, 84.89.128.14, 84.89.128.17, 84.89.155.15)
- upf.edu/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (84.89.128.17, UDP_-_NOEDNS_)
- upf.edu/DNSKEY: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (84.89.155.15, TCP_-_EDNS0_4096_D_KN)
- upf.edu/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (84.89.128.12, 84.89.128.13, 84.89.128.14, 84.89.128.17, 84.89.155.14, UDP_-_EDNS0_4096_D_KN, UDP_-_NOEDNS_)
- upf.edu/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (84.89.155.14, 84.89.155.15, UDP_-_EDNS0_512_D_KN)
- upf.edu/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (84.89.155.15, UDP_-_EDNS0_512_D_KN)
- upf.edu/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (84.89.128.12, 84.89.128.13, 84.89.128.14, 84.89.128.17, 84.89.155.15, TCP_-_EDNS0_4096_D_N)
- upf.edu/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (84.89.155.14, UDP_-_NOEDNS__0x20)
- upf.edu/TXT: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (84.89.128.12, 84.89.128.13, 84.89.128.14, TCP_-_EDNS0_4096_D_KN)
- upf.edu/TXT: No response was received from the server over TCP (tried 2 times). See RFC 1035, Sec. 4.2. (84.89.155.15, TCP_-_NOEDNS_)
- upf.edu/TXT: No response was received from the server over TCP (tried 8 times). See RFC 1035, Sec. 4.2. (84.89.128.17, TCP_-_EDNS0_4096_D_KN)
- jmgb2dsrik.upf.edu/A has errors; select the "Denial of existence" DNSSEC option to see them.
- 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.
- upf.edu/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (15)
- 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/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.
- 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/NS: 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. (84.89.155.15, UDP_-_EDNS0_4096_D_KN)
- upf.edu/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. (84.89.128.17, 84.89.155.15, UDP_-_EDNS0_4096_D_KN)
- upf.edu/CNAME 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.
- upf.edu/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
