discourse.urho3d.io
Updated:
2021-06-09 12:27:00 UTC (4 years ago)
Update now
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 (11)
- ./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 36216)
- 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)
Delegation status
Insecure (1)
- com to hosted-by-discourse.com
Secure (3)
- . to com
- . to io
- io to urho3d.io
Notices
Errors (1)
- com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:503:231d::2:30)
Warnings (3)
- 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.
JavaScript is required to make the graph below interactive.
