View on GitHub

DNSViz: A DNS visualization tool

5x5.lv

Updated: 2021-10-22 08:31:22 UTC (1157 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

Secure (3)
  • lv/SOA
  • lv/SOA
  • lv/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 14748)
  • ./DNSKEY (alg 8, id 20326)
  • NSEC3 proving non-existence of 5x5.lv/DS
  • lv/DNSKEY (alg 8, id 31113)
  • lv/DNSKEY (alg 8, id 42018)
  • lv/DS (alg 8, id 42018)

Delegation statusDelegation status

Lame (1)
  • lv to 5x5.lv
Secure (1)
  • . to lv

NoticesNotices

Errors (17)
  • 5x5.lv zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (37.48.90.71, 128.199.44.161, 212.71.239.8)
  • 5x5.lv zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (37.48.90.71, 128.199.44.161, 212.71.239.8)
  • 5x5.lv/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (37.48.90.71, 128.199.44.161, 212.71.239.8, UDP_-_EDNS0_4096_D_KN)
  • 5x5.lv/AAAA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (37.48.90.71, 128.199.44.161, 212.71.239.8, UDP_-_EDNS0_4096_D_KN)
  • 5x5.lv/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (37.48.90.71, 128.199.44.161, 212.71.239.8, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • 5x5.lv/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (37.48.90.71, 128.199.44.161, 212.71.239.8, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • 5x5.lv/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (37.48.90.71, 128.199.44.161, 212.71.239.8, UDP_-_EDNS0_4096_D_KN)
  • 5x5.lv/NSEC3PARAM: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (37.48.90.71, 128.199.44.161, 212.71.239.8, UDP_-_EDNS0_4096_D_KN)
  • 5x5.lv/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (37.48.90.71, 128.199.44.161, 212.71.239.8, TCP_-_EDNS0_4096_D_N)
  • 5x5.lv/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (37.48.90.71, 128.199.44.161, 212.71.239.8, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • 5x5.lv/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (37.48.90.71, 128.199.44.161, 212.71.239.8, UDP_-_EDNS0_4096_D_KN)
  • NSEC3 proving non-existence of 5x5.lv/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 5x5.lv/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • 15ce0jogbt.5x5.lv/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • 5x5.lv/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • 5x5.lv/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • 5x5.lv/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
  • NSEC3 proving non-existence of 5x5.lv/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of 5x5.lv/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • 5x5.lv/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