jb3.dev
Updated:
2021-12-01 19:19:43 UTC (1088 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (7)
- jb3.dev/A
- jb3.dev/MX
- jb3.dev/NS
- jb3.dev/NSEC3PARAM
- jb3.dev/NSEC3PARAM
- jb3.dev/SOA
- jb3.dev/TXT
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 14748)
- ./DNSKEY (alg 8, id 20326)
- dev/DNSKEY (alg 8, id 22764)
- dev/DNSKEY (alg 8, id 60074)
- dev/DS (alg 8, id 60074)
- jb3.dev/DNSKEY (alg 8, id 22249)
- jb3.dev/DNSKEY (alg 8, id 813)
- jb3.dev/DS (alg 8, id 22249)
- jb3.dev/DS (alg 8, id 22249)
Delegation status
Secure (2)
- . to dev
- dev to jb3.dev
Notices
Errors (3)
- jb3.dev/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- 45d8uenyw6.jb3.dev/A has errors; select the "Denial of existence" DNSSEC option to see them.
- jb3.dev/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
- jb3.dev/DS (alg 8, id 22249): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- jb3.dev/DS (alg 8, id 22249): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- jb3.dev/DS (alg 8, id 22249): 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.
- jb3.dev/DS (alg 8, id 22249): 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.
- jb3.dev/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- 45d8uenyw6.jb3.dev/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- jb3.dev/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
