11.140.197.in-addr.arpa
Updated:
2022-05-30 09:19:48 UTC (910 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (3)
- 11.140.197.in-addr.arpa/NS
- 11.140.197.in-addr.arpa/NSEC3PARAM
- 11.140.197.in-addr.arpa/SOA
DNSKEY/DS/NSEC status
Bogus (4)
- 11.140.197.in-addr.arpa/DNSKEY (alg 8, id 17040)
- 11.140.197.in-addr.arpa/DNSKEY (alg 8, id 62056)
- 11.140.197.in-addr.arpa/DNSKEY (alg 8, id 64799)
- 11.140.197.in-addr.arpa/DNSKEY (alg 8, id 65020)
Secure (20)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 47671)
- 11.140.197.in-addr.arpa/DS (alg 8, id 64799)
- 11.140.197.in-addr.arpa/DS (alg 8, id 64799)
- 197.in-addr.arpa/DNSKEY (alg 8, id 42701)
- 197.in-addr.arpa/DNSKEY (alg 8, id 52528)
- 197.in-addr.arpa/DNSKEY (alg 8, id 9156)
- 197.in-addr.arpa/DS (alg 8, id 35764)
- 197.in-addr.arpa/DS (alg 8, id 42701)
- 197.in-addr.arpa/DS (alg 8, id 42701)
- arpa/DNSKEY (alg 8, id 42581)
- arpa/DNSKEY (alg 8, id 64000)
- arpa/DS (alg 8, id 42581)
- arpa/DS (alg 8, id 42581)
- in-addr.arpa/DNSKEY (alg 8, id 47054)
- in-addr.arpa/DNSKEY (alg 8, id 4873)
- in-addr.arpa/DNSKEY (alg 8, id 54956)
- in-addr.arpa/DS (alg 8, id 47054)
- in-addr.arpa/DS (alg 8, id 53696)
- in-addr.arpa/DS (alg 8, id 63982)
Non_existent (3)
- 197.in-addr.arpa/DNSKEY (alg 8, id 35764)
- in-addr.arpa/DNSKEY (alg 8, id 53696)
- in-addr.arpa/DNSKEY (alg 8, id 63982)
Delegation status
Bogus (1)
- 197.in-addr.arpa to 11.140.197.in-addr.arpa
Secure (3)
- . to arpa
- arpa to in-addr.arpa
- in-addr.arpa to 197.in-addr.arpa
Notices
Errors (14)
- 11.140.197.in-addr.arpa/DNSKEY (alg 8, id 17040): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (197.140.10.155, 197.140.11.1, UDP_-_EDNS0_4096_D_KN)
- 11.140.197.in-addr.arpa/DNSKEY (alg 8, id 62056): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (197.140.10.155, 197.140.11.1, UDP_-_EDNS0_4096_D_KN)
- 11.140.197.in-addr.arpa/DNSKEY (alg 8, id 64799): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (197.140.10.155, 197.140.11.1, UDP_-_EDNS0_4096_D_KN)
- 11.140.197.in-addr.arpa/DNSKEY (alg 8, id 65020): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (197.140.10.155, 197.140.11.1, UDP_-_EDNS0_4096_D_KN)
- 11.140.197.in-addr.arpa/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (197.140.10.155, 197.140.11.1, UDP_-_EDNS0_4096_D_KN)
- 11.140.197.in-addr.arpa/NSEC3PARAM: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (197.140.10.155, 197.140.11.1, UDP_-_EDNS0_4096_D_KN)
- 11.140.197.in-addr.arpa/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (197.140.10.155, 197.140.11.1, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- 197.in-addr.arpa to 11.140.197.in-addr.arpa: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (197.140.10.155, 197.140.11.1, UDP_-_EDNS0_4096_D_KN)
- 197.in-addr.arpa to 11.140.197.in-addr.arpa: 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. (197.140.10.155, 197.140.11.1, UDP_-_EDNS0_4096_D_KN)
- 11.140.197.in-addr.arpa/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
- 11.140.197.in-addr.arpa/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- 11.140.197.in-addr.arpa/MX has errors; select the "Denial of existence" DNSSEC option to see them.
- 11.140.197.in-addr.arpa/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- r4p65cbzk2.11.140.197.in-addr.arpa/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (12)
- 11.140.197.in-addr.arpa/DS (alg 8, id 64799): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- 11.140.197.in-addr.arpa/DS (alg 8, id 64799): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- 11.140.197.in-addr.arpa/DS (alg 8, id 64799): 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.
- 11.140.197.in-addr.arpa/DS (alg 8, id 64799): 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.
- 197.in-addr.arpa/DS (alg 8, id 42701): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- 197.in-addr.arpa/DS (alg 8, id 42701): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- 197.in-addr.arpa/DS (alg 8, id 42701): 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.
- 197.in-addr.arpa/DS (alg 8, id 42701): 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.
- arpa/DS (alg 8, id 42581): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- arpa/DS (alg 8, id 42581): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- arpa/DS (alg 8, id 42581): 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.
- arpa/DS (alg 8, id 42581): 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.
JavaScript is required to make the graph below interactive.
