View on GitHub

DNSViz: A DNS visualization tool

www.city.kazuno.akita.jp

Updated: 2022-03-08 03:33:32 UTC (1019 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 (1)
  • www.city.kazuno.akita.jp/CNAME
Secure (2)
  • jp/SOA
  • vximrpldomtv.stech-gisc.jp/A

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 9799)
  • NSEC3 proving non-existence of city.kazuno.akita.jp/DS
  • jp/DNSKEY (alg 8, id 18100)
  • jp/DNSKEY (alg 8, id 38121)
  • jp/DNSKEY (alg 8, id 48354)
  • jp/DS (alg 8, id 18100)
  • stech-gisc.jp/DNSKEY (alg 8, id 57574)
  • stech-gisc.jp/DNSKEY (alg 8, id 58476)
  • stech-gisc.jp/DS (alg 8, id 57574)

Delegation statusDelegation status

Insecure (1)
  • jp to city.kazuno.akita.jp
Secure (2)
  • . to jp
  • jp to stech-gisc.jp

NoticesNotices

Errors (2)
  • NSEC3 proving non-existence of city.kazuno.akita.jp/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 city.kazuno.akita.jp/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
Warnings (2)
  • NSEC3 proving non-existence of city.kazuno.akita.jp/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of city.kazuno.akita.jp/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.

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