fl-lbadv-jan19.testing.prod.toratest.com
Updated:
2023-01-20 18:28:52 UTC (713 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (1)
- fl-lbadv-jan19.testing.prod.toratest.com/A
Secure (1)
- toratest.com/SOA
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 951)
- NSEC3 proving non-existence of testing.prod.toratest.com/DS
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 36739)
- com/DS (alg 8, id 30909)
- toratest.com/DNSKEY (alg 8, id 23574)
- toratest.com/DNSKEY (alg 8, id 55214)
- toratest.com/DS (alg 8, id 55214)
Delegation status
Insecure (1)
- toratest.com to testing.prod.toratest.com
Secure (2)
- . to com
- com to toratest.com
Notices
Errors (2)
- NSEC3 proving non-existence of testing.prod.toratest.com/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 testing.prod.toratest.com/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
Warnings (3)
- NSEC3 proving non-existence of testing.prod.toratest.com/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of testing.prod.toratest.com/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- toratest.com to testing.prod.toratest.com: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the toratest.com zone): dns3.p01.nsone.net, dns3.p16.nsone.net, dns4.p01.nsone.net, dns1.p16.nsone.net, dns1.p01.nsone.net, dns2.p01.nsone.net, dns2.p16.nsone.net, dns4.p16.nsone.net See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
