zw3b.app
Updated:
2025-07-01 02:33:39 UTC (205 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (1)
- zxvib.yjwp2.zw3b.app/CNAME (NXDOMAIN)
Secure (13)
- _.zw3b.app/CNAME
- web.zw3b.app/A
- zw3b.app/A
- zw3b.app/AAAA
- zw3b.app/CDNSKEY (NODATA)
- zw3b.app/CDS (NODATA)
- zw3b.app/CNAME (NODATA)
- zw3b.app/MX
- zw3b.app/NS
- zw3b.app/NSEC3PARAM
- zw3b.app/NSEC3PARAM
- zw3b.app/SOA
- zw3b.app/TXT
DNSKEY/DS/NSEC status
Secure (19)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 38696)
- ./DNSKEY (alg 8, id 46441)
- ./DNSKEY (alg 8, id 53148)
- NSEC3 proving non-existence of zw3b.app/CDNSKEY
- NSEC3 proving non-existence of zw3b.app/CDNSKEY
- NSEC3 proving non-existence of zw3b.app/CDS
- NSEC3 proving non-existence of zw3b.app/CDS
- NSEC3 proving non-existence of zw3b.app/CNAME
- NSEC3 proving non-existence of zw3b.app/CNAME
- NSEC3 proving non-existence of zxvib.yjwp2.zw3b.app/CNAME
- NSEC3 proving non-existence of zxvib.yjwp2.zw3b.app/CNAME
- app/DNSKEY (alg 8, id 17620)
- app/DNSKEY (alg 8, id 23684)
- app/DS (alg 8, id 23684)
- zw3b.app/DNSKEY (alg 13, id 39028)
- zw3b.app/DNSKEY (alg 13, id 47132)
- zw3b.app/DS (alg 13, id 39028)
- zw3b.app/DS (alg 13, id 47132)
Delegation status
Secure (2)
- . to app
- app to zw3b.app
Notices
Errors (8)
- NSEC3 proving non-existence of zw3b.app/CDNSKEY: 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 zw3b.app/CDNSKEY: 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 zw3b.app/CDS: 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 zw3b.app/CDS: 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 zw3b.app/CNAME: 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 zw3b.app/CNAME: 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 zxvib.yjwp2.zw3b.app/CNAME: 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 zxvib.yjwp2.zw3b.app/CNAME: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
Warnings (8)
- NSEC3 proving non-existence of zw3b.app/CDNSKEY: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of zw3b.app/CDNSKEY: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of zw3b.app/CDS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of zw3b.app/CDS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of zw3b.app/CNAME: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of zw3b.app/CNAME: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of zxvib.yjwp2.zw3b.app/CNAME: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of zxvib.yjwp2.zw3b.app/CNAME: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
JavaScript is required to make the graph below interactive.
