View on GitHub

DNSViz: A DNS visualization tool

mofa.go.jp

DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (4)
  • mofa.go.jp/MX
  • mofa.go.jp/NS
  • mofa.go.jp/SOA
  • mofa.go.jp/TXT
Secure (1)
  • jp/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (3)
  • mofa.go.jp/DNSKEY (alg 8, id 24691)
  • mofa.go.jp/DNSKEY (alg 8, id 61899)
  • mofa.go.jp/DNSKEY (alg 8, id 7950)
Secure (7)
  • ./DNSKEY (alg 8, id 14631)
  • ./DNSKEY (alg 8, id 20326)
  • NSEC3 proving non-existence of mofa.go.jp/DS
  • jp/DNSKEY (alg 8, id 15171)
  • jp/DNSKEY (alg 8, id 36714)
  • jp/DNSKEY (alg 8, id 46369)
  • jp/DS (alg 8, id 46369)

Delegation statusDelegation status

Insecure (1)
  • jp to mofa.go.jp
Secure (1)
  • . to jp

NoticesNotices

Errors (9)
  • NSEC3 proving non-existence of mofa.go.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 mofa.go.jp/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • mofa.go.jp zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (95.131.158.22)
  • mofa.go.jp/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (95.131.158.22, UDP_-_NOEDNS_)
  • mofa.go.jp/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • mofa.go.jp/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • mofa.go.jp/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • a8p1iqzkd2.mofa.go.jp/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • mofa.go.jp/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
  • NSEC3 proving non-existence of mofa.go.jp/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of mofa.go.jp/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • mofa.go.jp/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • mofa.go.jp/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • mofa.go.jp/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • a8p1iqzkd2.mofa.go.jp/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • mofa.go.jp/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.

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