View on GitHub

DNSViz: A DNS visualization tool

just-pthai-it.info

« 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)
  • ./SOA
  • just-pthai-it.info/A
  • just-pthai-it.info/A (NXDOMAIN)
  • just-pthai-it.info/SOA
  • just-pthai-it.info/SOA (NXDOMAIN)
Secure (1)
  • info/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 30903)
  • ./DNSKEY (alg 8, id 5613)
  • NSEC3 proving non-existence of just-pthai-it.info/DS
  • info/DNSKEY (alg 8, id 36546)
  • info/DNSKEY (alg 8, id 42411)
  • info/DNSKEY (alg 8, id 5104)
  • info/DS (alg 8, id 5104)

Delegation statusDelegation status

Insecure (1)
  • info to just-pthai-it.info
Secure (1)
  • . to info

NoticesNotices

Errors (16)
  • ./SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (103.90.226.137, 103.200.22.7, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • NSEC3 proving non-existence of just-pthai-it.info/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 just-pthai-it.info/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • just-pthai-it.info zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (103.90.226.137, 103.200.22.7)
  • just-pthai-it.info/A (NXDOMAIN): An SOA RR with owner name (.) not matching the zone name (just-pthai-it.info) was returned with the NXDOMAIN response. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.1. (103.90.226.137, 103.200.22.7, UDP_-_EDNS0_4096_D_KN)
  • just-pthai-it.info/SOA (NXDOMAIN): An SOA RR with owner name (.) not matching the zone name (just-pthai-it.info) was returned with the NXDOMAIN response. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.1. (103.90.226.137, 103.200.22.7, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • just-pthai-it.info/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (103.90.226.137, 103.200.22.7, TCP_-_EDNS0_4096_D_N)
  • just-pthai-it.info/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • just-pthai-it.info/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • just-pthai-it.info/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • just-pthai-it.info/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • just-pthai-it.info/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
  • just-pthai-it.info/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • 7enc83yr5o.just-pthai-it.info/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • just-pthai-it.info/NS has errors; select the "Denial of existence" DNSSEC option to see them.
  • just-pthai-it.info/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
  • NSEC3 proving non-existence of just-pthai-it.info/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of just-pthai-it.info/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • info to just-pthai-it.info: The following NS name(s) were found in the delegation NS RRset (i.e., in the info zone), but not in the authoritative NS RRset: ns1.vietnix.net, ns2.vietnix.net, nsbak.vietnix.net See RFC 1034, Sec. 4.2.2.
  • just-pthai-it.info/DS 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