View on GitHub

DNSViz: A DNS visualization tool

utc.com

Updated: 2023-11-26 01:03:19 UTC (363 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (5)
  • utc.com/A
  • utc.com/MX
  • utc.com/NS
  • utc.com/SOA
  • utc.com/TXT
Secure (2)
  • com/SOA
  • com/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (2)
  • utc.com/DNSKEY (alg 13, id 2371)
  • utc.com/DNSKEY (alg 13, id 34505)
Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46780)
  • NSEC3 proving non-existence of utc.com/DS
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 63246)
  • com/DS (alg 8, id 30909)

Delegation statusDelegation status

Insecure (1)
  • com to utc.com
Secure (1)
  • . to com

NoticesNotices

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.

DNSKEY legend

Full legend
SEP bit setSEP bit set
Revoke bit setRevoke bit set
Trust anchorTrust anchor
Download: png | svg
Warning JavaScript is required to make the graph below interactive.
DNSSEC authentication graph