saitest.saicharan.in
Updated:
2021-01-05 06:40:22 UTC (1452 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (1)
- saicharan.in/SOA
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26116)
- ./DNSKEY (alg 8, id 42351)
- NSEC3 proving non-existence of saitest.saicharan.in/DS
- in/DNSKEY (alg 8, id 54739)
- in/DNSKEY (alg 8, id 65169)
- in/DS (alg 8, id 54739)
- in/DS (alg 8, id 54739)
- saicharan.in/DNSKEY (alg 8, id 3006)
- saicharan.in/DNSKEY (alg 8, id 55366)
- saicharan.in/DS (alg 8, id 55366)
Delegation status
Lame (1)
- saicharan.in to saitest.saicharan.in
Secure (2)
- . to in
- in to saicharan.in
Notices
Errors (16)
- NSEC3 proving non-existence of saitest.saicharan.in/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of saitest.saicharan.in/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- saitest.saicharan.in zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (50.35.24.39)
- saitest.saicharan.in zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (50.35.24.39)
- saitest.saicharan.in/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (50.35.24.39, UDP_-_NOEDNS_)
- saitest.saicharan.in/AAAA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (50.35.24.39, UDP_-_NOEDNS_)
- saitest.saicharan.in/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (50.35.24.39, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
- saitest.saicharan.in/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (50.35.24.39, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
- saitest.saicharan.in/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (50.35.24.39, UDP_-_NOEDNS_)
- saitest.saicharan.in/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (50.35.24.39, TCP_-_NOEDNS_)
- saitest.saicharan.in/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (50.35.24.39, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
- saitest.saicharan.in/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (50.35.24.39, UDP_-_NOEDNS_)
- saitest.saicharan.in/DS has errors; select the "Denial of existence" DNSSEC option to see them.
- 95l6qx4vyc.saitest.saicharan.in/A has errors; select the "Denial of existence" DNSSEC option to see them.
- saitest.saicharan.in/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- saitest.saicharan.in/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
- NSEC3 proving non-existence of saitest.saicharan.in/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of saitest.saicharan.in/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- in/DS (alg 8, id 54739): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- in/DS (alg 8, id 54739): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- in/DS (alg 8, id 54739): 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.
- in/DS (alg 8, id 54739): 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.
- saitest.saicharan.in/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
