155.136.188.41.in-addr.arpa
Updated:
2020-03-13 06:07:51 UTC (1715 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (2)
- 136.188.41.in-addr.arpa/SOA
- 155.136.188.41.in-addr.arpa/PTR (NXDOMAIN)
Secure (1)
- 41.in-addr.arpa/SOA
DNSKEY/DS/NSEC status
Secure (19)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 33853)
- 41.in-addr.arpa/DNSKEY (alg 8, id 36123)
- 41.in-addr.arpa/DNSKEY (alg 8, id 52720)
- 41.in-addr.arpa/DNSKEY (alg 8, id 926)
- 41.in-addr.arpa/DS (alg 8, id 557)
- 41.in-addr.arpa/DS (alg 8, id 926)
- 41.in-addr.arpa/DS (alg 8, id 926)
- NSEC proving non-existence of 136.188.41.in-addr.arpa/DS
- arpa/DNSKEY (alg 8, id 42581)
- arpa/DNSKEY (alg 8, id 44490)
- arpa/DS (alg 8, id 42581)
- arpa/DS (alg 8, id 42581)
- in-addr.arpa/DNSKEY (alg 8, id 25669)
- in-addr.arpa/DNSKEY (alg 8, id 47054)
- 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)
- 41.in-addr.arpa/DNSKEY (alg 8, id 557)
- in-addr.arpa/DNSKEY (alg 8, id 53696)
- in-addr.arpa/DNSKEY (alg 8, id 63982)
Delegation status
Insecure (1)
- 41.in-addr.arpa to 136.188.41.in-addr.arpa
Secure (3)
- . to arpa
- arpa to in-addr.arpa
- in-addr.arpa to 41.in-addr.arpa
Notices
Errors (1)
- arpa zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (192.5.5.241, 2001:500:2::c)
Warnings (14)
- 41.in-addr.arpa to 136.188.41.in-addr.arpa: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the 41.in-addr.arpa zone): ns1.simbanet.co.tz See RFC 1034, Sec. 4.2.2.
- 41.in-addr.arpa to 136.188.41.in-addr.arpa: The following NS name(s) were found in the delegation NS RRset (i.e., in the 41.in-addr.arpa zone), but not in the authoritative NS RRset: dn1.simbanet.net See RFC 1034, Sec. 4.2.2.
- 41.in-addr.arpa/DS (alg 8, id 557): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- 41.in-addr.arpa/DS (alg 8, id 557): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- 41.in-addr.arpa/DS (alg 8, id 557): 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.
- 41.in-addr.arpa/DS (alg 8, id 557): 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.
- 41.in-addr.arpa/DS (alg 8, id 926): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- 41.in-addr.arpa/DS (alg 8, id 926): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- 41.in-addr.arpa/DS (alg 8, id 926): 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.
- 41.in-addr.arpa/DS (alg 8, id 926): 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.
