discourse.urho3d.io
Updated:
2021-05-26 04:48:19 UTC (4 years ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (2)
- urho3d.hosted-by-discourse.com/A
- urho3d.hosted-by-discourse.com/AAAA
Secure (3)
- com/SOA
- com/SOA
- discourse.urho3d.io/CNAME
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 14631)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of hosted-by-discourse.com/DS
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 54714)
- com/DS (alg 8, id 30909)
- io/DNSKEY (alg 8, id 43695)
- io/DNSKEY (alg 8, id 57355)
- io/DS (alg 8, id 57355)
- urho3d.io/DNSKEY (alg 13, id 42295)
- urho3d.io/DS (alg 13, id 42295)
- urho3d.io/DS (alg 8, id 937)
Non_existent (1)
- urho3d.io/DNSKEY (alg 8, id 937)
Delegation status
Insecure (1)
- com to hosted-by-discourse.com
Secure (3)
- . to com
- . to io
- io to urho3d.io
Notices
Errors (4)
- discourse.urho3d.io/CNAME: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (156.154.132.200, 156.154.133.200, 2610:a1:1024::200, 2610:a1:1025::200, UDP_-_EDNS0_4096_D_KN)
- io to urho3d.io: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (156.154.132.200, 156.154.133.200, 2610:a1:1024::200, 2610:a1:1025::200, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- urho3d.io/DNSKEY (alg 13, id 42295): The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (156.154.132.200, 156.154.133.200, 2610:a1:1024::200, 2610:a1:1025::200, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- urho3d.io/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
- com to hosted-by-discourse.com: Authoritative AAAA records exist for ns-104.awsdns-13.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- urho3d.io/DS (alg 13, id 42295): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- urho3d.io/DS (alg 13, id 42295): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- urho3d.io/DS (alg 8, id 937): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- urho3d.io/DS (alg 8, id 937): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
JavaScript is required to make the graph below interactive.
