boboworld.com
Updated:
2024-11-04 22:19:43 UTC (405 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- boboworld.com/A
- boboworld.com/MX
- boboworld.com/NS
- boboworld.com/SOA
- boboworld.com/TXT
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 61050)
- boboworld.com/DNSKEY (alg 13, id 4236)
- boboworld.com/DS (alg 13, id 4236)
- boboworld.com/DS (alg 13, id 4236)
- com/DNSKEY (alg 13, id 19718)
- com/DNSKEY (alg 13, id 29942)
- com/DS (alg 13, id 19718)
Delegation status
Secure (2)
- . to com
- com to boboworld.com
Notices
Errors (2)
- boboworld.com/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (162.159.26.131, UDP_-_EDNS0_4096_D_KN)
- boboworld.com/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (162.159.26.131, UDP_-_EDNS0_4096_D_KN)
Warnings (6)
- boboworld.com/DS (alg 13, id 4236): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- boboworld.com/DS (alg 13, id 4236): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- boboworld.com/DS (alg 13, id 4236): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- boboworld.com/DS (alg 13, id 4236): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- boboworld.com/DS (alg 13, id 4236): In the spirit of RFC 4509, DS records with digest type 1 (SHA-1) might be ignored when DS records with digest type 4 (SHA-384) exist in the same RRset. See RFC 4509, Sec. 3.
- boboworld.com/DS (alg 13, id 4236): In the spirit of RFC 4509, DS records with digest type 1 (SHA-1) might be ignored when DS records with digest type 4 (SHA-384) exist in the same RRset. See RFC 4509, Sec. 3.
JavaScript is required to make the graph below interactive.
