NSEC3 proving non-existence of incometax.gov.in/DS
gov.in/DNSKEY (alg 8, id 62943)
gov.in/DNSKEY (alg 8, id 6814)
gov.in/DS (alg 8, id 6814)
gov.in/DS (alg 8, id 6814)
in/DNSKEY (alg 8, id 54739)
in/DNSKEY (alg 8, id 65169)
in/DS (alg 8, id 54739)
in/DS (alg 8, id 54739)
Non_existent (1)
incometax.gov.in/DNSKEY (alg 5, id 11712)
Delegation status
Insecure (1)
gov.in to incometax.gov.in
Secure (2)
. to in
in to gov.in
Notices
Errors (6)
NSEC3 proving non-existence of incometax.gov.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 incometax.gov.in/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
incometax.gov.in/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (59.160.103.171, 125.16.225.122, UDP_-_NOEDNS_)
incometax.gov.in/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (59.160.103.171, 125.16.225.122, UDP_-_EDNS0_512_D_KN)
ns01.incometax.gov.in/AAAA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (59.160.103.171, 125.16.225.122, UDP_-_NOEDNS_)
incometax.gov.in/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (12)
NSEC3 proving non-existence of incometax.gov.in/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of incometax.gov.in/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
RRSIG ns01.incometax.gov.in/A alg 5, id 11712: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
RRSIG ns01.incometax.gov.in/A alg 5, id 11712: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
gov.in/DS (alg 8, id 6814): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
gov.in/DS (alg 8, id 6814): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
gov.in/DS (alg 8, id 6814): 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.
gov.in/DS (alg 8, id 6814): 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): 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.