150.167.77.40.in-addr.arpa
Updated:
2020-09-15 12:39:19 UTC (1558 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (4)
- 150.167.77.40.in-addr.arpa/PTR
- 150.167.77.40.in-addr.arpa/PTR (NXDOMAIN)
- 167.77.40.in-addr.arpa/SOA
- 77.40.in-addr.arpa/SOA
Secure (1)
- 40.in-addr.arpa/SOA
DNSKEY/DS/NSEC status
Secure (17)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46594)
- 40.in-addr.arpa/DNSKEY (alg 5, id 16656)
- 40.in-addr.arpa/DNSKEY (alg 5, id 25739)
- 40.in-addr.arpa/DNSKEY (alg 5, id 35055)
- 40.in-addr.arpa/DS (alg 5, id 16656)
- NSEC proving non-existence of 77.40.in-addr.arpa/DS
- arpa/DNSKEY (alg 8, id 42581)
- arpa/DNSKEY (alg 8, id 57156)
- 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 49608)
- 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 (2)
- in-addr.arpa/DNSKEY (alg 8, id 53696)
- in-addr.arpa/DNSKEY (alg 8, id 63982)
Delegation status
Insecure (2)
- 40.in-addr.arpa to 77.40.in-addr.arpa
- 77.40.in-addr.arpa to 167.77.40.in-addr.arpa
Secure (3)
- . to arpa
- arpa to in-addr.arpa
- in-addr.arpa to 40.in-addr.arpa
Notices
Warnings (14)
- 40.in-addr.arpa/DS (alg 5, id 16656): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- 40.in-addr.arpa/DS (alg 5, id 16656): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- RRSIG 40.in-addr.arpa/DNSKEY alg 5, id 16656: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG 40.in-addr.arpa/DNSKEY alg 5, id 16656: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG 40.in-addr.arpa/DNSKEY alg 5, id 16656: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG 40.in-addr.arpa/DNSKEY alg 5, id 35055: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG 40.in-addr.arpa/DNSKEY alg 5, id 35055: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG 40.in-addr.arpa/DNSKEY alg 5, id 35055: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG 40.in-addr.arpa/SOA alg 5, id 35055: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG NSEC proving non-existence of 77.40.in-addr.arpa/DS alg 5, id 35055: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- 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.
