pitt.edu
Updated:
2024-05-22 17:34:24 UTC (117 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (7)
- pitt.edu/A
- pitt.edu/MX
- pitt.edu/NS
- pitt.edu/NSEC3PARAM
- pitt.edu/SOA
- pitt.edu/SOA
- pitt.edu/TXT
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 5613)
- edu/DNSKEY (alg 13, id 35663)
- edu/DNSKEY (alg 13, id 41543)
- edu/DS (alg 13, id 35663)
- pitt.edu/DNSKEY (alg 7, id 10962)
- pitt.edu/DNSKEY (alg 7, id 594)
- pitt.edu/DS (alg 7, id 594)
Delegation status
Secure (2)
- . to edu
- edu to pitt.edu
Notices
Errors (10)
- pitt.edu zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2620:102:4002:400::10, 2620:102:401f:fe00::10)
- pitt.edu/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2620:102:4002:400::10, 2620:102:401f:fe00::10, UDP_-_NOEDNS_)
- pitt.edu/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2620:102:4002:400::10, 2620:102:401f:fe00::10, UDP_-_NOEDNS_)
- pitt.edu/NSEC3PARAM: DNSSEC was effectively downgraded because no response was received from the server over UDP (tried 11 times) with EDNS enabled. See RFC 6891, Sec. 7, RFC 2671, Sec. 5.3. (130.49.127.11, UDP_-_NOEDNS_)
- pitt.edu/NSEC3PARAM: No response was received from the server over UDP (tried 11 times) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (130.49.127.11, UDP_-_EDNS0_4096_D_KN)
- pitt.edu/NSEC3PARAM: The DNSSEC records necessary to validate the response could not be retrieved from the server. See RFC 4035, Sec. 3.1.1, RFC 4035, Sec. 3.1.3. (130.49.127.11, UDP_-_EDNS0_4096_D_KN)
- pitt.edu/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (130.49.127.11, TCP_-_EDNS0_4096_D_N)
- pitt.edu/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- pitt.edu/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- f2b7s3glv0.pitt.edu/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (22)
- RRSIG pitt.edu/A alg 7, id 10962: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG pitt.edu/DNSKEY alg 7, id 10962: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG pitt.edu/DNSKEY alg 7, id 10962: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG pitt.edu/DNSKEY alg 7, id 594: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG pitt.edu/DNSKEY alg 7, id 594: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG pitt.edu/MX alg 7, id 10962: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG pitt.edu/NS alg 7, id 10962: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG pitt.edu/NSEC3PARAM alg 7, id 10962: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG pitt.edu/SOA alg 7, id 10962: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG pitt.edu/SOA alg 7, id 10962: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG pitt.edu/TXT alg 7, id 10962: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- edu to pitt.edu: AAAA glue records exist for ns4.pitt.edu, but there are no corresponding authoritative AAAA records. See RFC 1034, Sec. 4.2.2.
- edu to pitt.edu: AAAA glue records exist for ns5.pitt.edu, but there are no corresponding authoritative AAAA records. See RFC 1034, Sec. 4.2.2.
- pitt.edu/DS (alg 7, id 594): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- pitt.edu/DS (alg 7, id 594): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- pitt.edu/NS: 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. (130.49.127.11, UDP_-_EDNS0_4096_D_KN)
- pitt.edu/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. (130.49.127.11, UDP_-_EDNS0_4096_D_KN)
- pitt.edu/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. (130.49.127.11, UDP_-_EDNS0_4096_D_KN)
- pitt.edu/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- pitt.edu/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- pitt.edu/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- f2b7s3glv0.pitt.edu/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
