www.ca.gov
Updated:
2022-07-02 10:16:19 UTC (904 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- akamaiedge.net/SOA
- e65017.dscb.akamaiedge.net/A
- e65017.dscb.akamaiedge.net/AAAA
- www.ca.gov.edgekey.net/CNAME
- www.ca.gov/CNAME
Secure (4)
- gov/SOA
- net/SOA
- net/SOA
- net/SOA
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 20826)
- ./DNSKEY (alg 8, id 47671)
- NSEC3 proving non-existence of akamaiedge.net/DS
- NSEC3 proving non-existence of ca.gov/DS
- NSEC3 proving non-existence of edgekey.net/DS
- gov/DNSKEY (alg 8, id 2706)
- gov/DNSKEY (alg 8, id 7698)
- gov/DS (alg 8, id 7698)
- net/DNSKEY (alg 8, id 35886)
- net/DNSKEY (alg 8, id 45728)
- net/DS (alg 8, id 35886)
Delegation status
Insecure (4)
- akamaiedge.net to dscb.akamaiedge.net
- gov to ca.gov
- net to akamaiedge.net
- net to edgekey.net
Secure (2)
- . to gov
- . to net
Notices
Errors (2)
- NSEC3 proving non-existence of ca.gov/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 ca.gov/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
Warnings (13)
- NSEC3 proving non-existence of ca.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of ca.gov/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- akamaiedge.net to dscb.akamaiedge.net: The glue address(es) for n2dscb.akamaiedge.net (23.216.148.77, 23.216.148.81) differed from its authoritative address(es) (23.216.148.81). See RFC 1034, Sec. 4.2.2.
- akamaiedge.net to dscb.akamaiedge.net: The glue address(es) for n3dscb.akamaiedge.net (23.216.148.77, 23.216.148.84) differed from its authoritative address(es) (23.216.148.77). See RFC 1034, Sec. 4.2.2.
- akamaiedge.net to dscb.akamaiedge.net: The glue address(es) for n4dscb.akamaiedge.net (23.216.148.78, 23.216.148.84) differed from its authoritative address(es) (23.216.148.84). See RFC 1034, Sec. 4.2.2.
- akamaiedge.net to dscb.akamaiedge.net: The glue address(es) for n5dscb.akamaiedge.net (23.62.45.15, 23.216.148.81) differed from its authoritative address(es) (23.62.45.15). See RFC 1034, Sec. 4.2.2.
- akamaiedge.net to dscb.akamaiedge.net: The glue address(es) for n6dscb.akamaiedge.net (23.62.45.18, 23.216.148.80) differed from its authoritative address(es) (23.216.148.80). See RFC 1034, Sec. 4.2.2.
- akamaiedge.net to dscb.akamaiedge.net: The glue address(es) for n7dscb.akamaiedge.net (23.67.78.18, 23.67.78.27) differed from its authoritative address(es) (23.67.78.18). See RFC 1034, Sec. 4.2.2.
- net to akamaiedge.net: Authoritative AAAA records exist for a11-192.akamaiedge.net, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- net to edgekey.net: Authoritative AAAA records exist for a13-65.akam.net, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- net to edgekey.net: Authoritative AAAA records exist for a5-65.akam.net, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- net to edgekey.net: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the net zone): a11-65.akam.net, ns1-2.akam.net, a9-65.akam.net, a3-65.akam.net See RFC 1034, Sec. 4.2.2.
- net to edgekey.net: The following NS name(s) were found in the delegation NS RRset (i.e., in the net zone), but not in the authoritative NS RRset: ns1-66.akam.net, ns4-66.akam.net, ns5-66.akam.net, ns7-65.akam.net See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
