utc.com
Updated:
2025-03-04 22:18:17 UTC (16 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (7)
- utc.com/A
- utc.com/CDNSKEY
- utc.com/CDS
- utc.com/MX
- utc.com/NS
- utc.com/SOA
- utc.com/TXT
Secure (2)
- com/SOA
- com/SOA
DNSKEY/DS/NSEC status
Insecure (2)
- utc.com/DNSKEY (alg 13, id 2371)
- utc.com/DNSKEY (alg 13, id 34505)
Secure (7)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26470)
- ./DNSKEY (alg 8, id 38696)
- NSEC3 proving non-existence of utc.com/DS
- com/DNSKEY (alg 13, id 19718)
- com/DNSKEY (alg 13, id 23202)
- com/DS (alg 13, id 19718)
Non_existent (2)
- utc.com/DNSKEY (alg 0, id 0)
- utc.com/DNSKEY (alg 0, id 768)
Delegation status
Insecure (1)
- com to utc.com
Secure (1)
- . to com
Notices
Errors (4)
- utc.com/CDNSKEY: The CDNSKEY RRset must be signed with a key that is represented in both the current DNSKEY and the current DS RRset. See RFC 7344, Sec. 4.1.
- utc.com/CDNSKEY: The contents of the CDNSKEY RRset are inconsistent with those of the CDS RRset. See RFC 7344, Sec. 4.
- utc.com/CDS: The CDS RRset must be signed with a key that is represented in both the current DNSKEY and the current DS RRset. See RFC 7344, Sec. 4.1.
- utc.com/CDS: The contents of the CDNSKEY RRset are inconsistent with those of the CDS RRset. See RFC 7344, Sec. 4.
Warnings (3)
- com to utc.com: Authoritative AAAA records exist for ns1.utc.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- com to utc.com: Authoritative AAAA records exist for ns2.utc.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- com to utc.com: The following NS name(s) were found in the delegation NS RRset (i.e., in the com zone), but not in the authoritative NS RRset: algin.ns.cloudflare.com, aria.ns.cloudflare.com See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
