boip.in
Updated:
2020-09-01 12:22:53 UTC (1597 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- boip.in/A
- boip.in/AAAA
- boip.in/MX
- boip.in/NS
- boip.in/SOA
- boip.in/TXT
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46594)
- boip.in/DNSKEY (alg 13, id 19299)
- boip.in/DNSKEY (alg 13, id 45741)
- boip.in/DS (alg 13, id 19299)
- in/DNSKEY (alg 8, id 54739)
- in/DNSKEY (alg 8, id 65169)
- in/DS (alg 8, id 54739)
- in/DS (alg 8, id 54739)
Delegation status
Secure (2)
- . to in
- in to boip.in
Notices
Errors (8)
- RRSIG boip.in/A alg 13, id 45741: The TTL of the RRset (2987) exceeds the value of the Original TTL field of the RRSIG RR covering it (2512). See RFC 4035, Sec. 2.2.
- RRSIG boip.in/A alg 13, id 45741: The TTL of the RRset (2987) exceeds the value of the Original TTL field of the RRSIG RR covering it (2512). See RFC 4035, Sec. 2.2.
- RRSIG boip.in/A alg 13, id 45741: The TTL of the RRset (2987) exceeds the value of the Original TTL field of the RRSIG RR covering it (2512). See RFC 4035, Sec. 2.2.
- RRSIG boip.in/AAAA alg 13, id 45741: The TTL of the RRset (3347) exceeds the value of the Original TTL field of the RRSIG RR covering it (773). See RFC 4035, Sec. 2.2.
- RRSIG boip.in/AAAA alg 13, id 45741: The TTL of the RRset (3347) exceeds the value of the Original TTL field of the RRSIG RR covering it (773). See RFC 4035, Sec. 2.2.
- RRSIG boip.in/AAAA alg 13, id 45741: The TTL of the RRset (3347) exceeds the value of the Original TTL field of the RRSIG RR covering it (773). See RFC 4035, Sec. 2.2.
- RRSIG boip.in/AAAA alg 13, id 45741: The TTL of the RRset (3347) exceeds the value of the Original TTL field of the RRSIG RR covering it (773). See RFC 4035, Sec. 2.2.
- boip.in/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- 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.
JavaScript is required to make the graph below interactive.
