View on GitHub

DNSViz: A DNS visualization tool

vlada.hr

Updated: 2020-07-27 23:23:26 UTC (1608 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)
  • vlada.hr/A
  • vlada.hr/MX
  • vlada.hr/NS
  • vlada.hr/SOA
  • vlada.hr/TXT
Secure (1)
  • hr/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46594)
  • NSEC3 proving non-existence of vlada.hr/DS
  • hr/DNSKEY (alg 8, id 10758)
  • hr/DNSKEY (alg 8, id 63025)
  • hr/DS (alg 8, id 63025)
  • hr/DS (alg 8, id 63025)

Delegation statusDelegation status

Insecure (1)
  • hr to vlada.hr
Secure (1)
  • . to hr

NoticesNotices

Errors (16)
  • NSEC3 proving non-existence of vlada.hr/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 vlada.hr/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • vlada.hr zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (195.20.153.67)
  • vlada.hr zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (195.20.153.67)
  • vlada.hr/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (195.20.153.67, UDP_-_EDNS0_4096_D_K)
  • vlada.hr/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (195.20.153.67, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • vlada.hr/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (195.20.153.67, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • vlada.hr/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (195.20.153.67, UDP_-_EDNS0_4096_D_K)
  • vlada.hr/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (195.20.153.67, TCP_-_EDNS0_4096_D)
  • vlada.hr/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (195.20.153.67, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • vlada.hr/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (195.20.153.67, UDP_-_EDNS0_4096_D_K)
  • vlada.hr/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • vlada.hr/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • vlada.hr/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • vlada.hr/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • umx3tla9vk.vlada.hr/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
  • NSEC3 proving non-existence of vlada.hr/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of vlada.hr/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • hr/DS (alg 8, id 63025): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • hr/DS (alg 8, id 63025): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • hr/DS (alg 8, id 63025): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • hr/DS (alg 8, id 63025): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • vlada.hr/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