uminho.pt
Updated:
2024-10-10 13:50:32 UTC (42 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (4)
- uminho.pt/MX
- uminho.pt/NS
- uminho.pt/SOA
- uminho.pt/TXT
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 20038)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 61050)
- pt/DNSKEY (alg 13, id 30640)
- pt/DNSKEY (alg 13, id 40155)
- pt/DS (alg 13, id 40155)
- uminho.pt/DNSKEY (alg 5, id 36028)
- uminho.pt/DNSKEY (alg 5, id 51330)
- uminho.pt/DS (alg 5, id 36028)
Delegation status
Secure (2)
- . to pt
- pt to uminho.pt
Notices
Errors (1)
- ./DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (192.33.4.12, UDP_-_EDNS0_512_D_KN)
Warnings (19)
- ./DNSKEY (alg 8, id 20038): 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. (192.33.4.12, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 20326): 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. (192.33.4.12, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 61050): 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. (192.33.4.12, UDP_-_EDNS0_4096_D_KN)
- RRSIG uminho.pt/DNSKEY alg 5, id 36028: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG uminho.pt/DNSKEY alg 5, id 36028: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG uminho.pt/DNSKEY alg 5, id 51330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG uminho.pt/DNSKEY alg 5, id 51330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG uminho.pt/MX alg 5, id 51330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG uminho.pt/NS alg 5, id 51330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG uminho.pt/SOA alg 5, id 51330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG uminho.pt/TXT alg 5, id 51330: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- sf4bc.qz5g4.uminho.pt/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- uminho.pt/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- uminho.pt/CDNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- uminho.pt/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
- uminho.pt/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- uminho.pt/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- uminho.pt/CDS has warnings; select the "Denial of existence" DNSSEC option to see them.
- uminho.pt/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
