jb3.dev
Updated:
2021-12-30 01:41:38 UTC (1059 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (8)
- jb3.dev/A
- jb3.dev/AAAA
- jb3.dev/MX
- jb3.dev/NS
- jb3.dev/NSEC3PARAM
- jb3.dev/NSEC3PARAM
- jb3.dev/SOA
- jb3.dev/TXT
Secure (1)
- dev/SOA
DNSKEY/DS/NSEC status
Insecure (2)
- jb3.dev/DNSKEY (alg 8, id 22249)
- jb3.dev/DNSKEY (alg 8, id 813)
Secure (7)
- ./DNSKEY (alg 8, id 14748)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 9799)
- NSEC3 proving non-existence of jb3.dev/DS
- dev/DNSKEY (alg 8, id 52363)
- dev/DNSKEY (alg 8, id 60074)
- dev/DS (alg 8, id 60074)
Delegation status
Insecure (1)
- dev to jb3.dev
Secure (1)
- . to dev
Notices
Errors (5)
- NSEC3 proving non-existence of jb3.dev/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of jb3.dev/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- jb3.dev/DS has errors; select the "Denial of existence" DNSSEC option to see them.
- uw6dtc74ij.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 (5)
- NSEC3 proving non-existence of jb3.dev/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of jb3.dev/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- jb3.dev/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
- uw6dtc74ij.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.
