webapi.pre-uat.sazka.cz
Updated:
2022-04-14 12:19:04 UTC (1367 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (1)
- webapi.pre-uat.sazka.cz/A
Secure (1)
- sazka.cz/SOA
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 47671)
- NSEC3 proving non-existence of pre-uat.sazka.cz/DS
- NSEC3 proving non-existence of pre-uat.sazka.cz/DS
- cz/DNSKEY (alg 13, id 20237)
- cz/DNSKEY (alg 13, id 40420)
- cz/DS (alg 13, id 20237)
- sazka.cz/DNSKEY (alg 8, id 12787)
- sazka.cz/DNSKEY (alg 8, id 42855)
- sazka.cz/DNSKEY (alg 8, id 59754)
- sazka.cz/DS (alg 8, id 12787)
Delegation status
Insecure (1)
- sazka.cz to pre-uat.sazka.cz
Secure (2)
- . to cz
- cz to sazka.cz
Notices
Errors (4)
- NSEC3 proving non-existence of pre-uat.sazka.cz/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 pre-uat.sazka.cz/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 pre-uat.sazka.cz/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 pre-uat.sazka.cz/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
Warnings (4)
- NSEC3 proving non-existence of pre-uat.sazka.cz/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of pre-uat.sazka.cz/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of pre-uat.sazka.cz/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of pre-uat.sazka.cz/DS: 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.
