View on GitHub

DNSViz: A DNS visualization tool

my.hyundaicard.com

« 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 (2)
  • custom.bnc.lt/A
  • my.hyundaicard.com/CNAME
Secure (2)
  • com/SOA
  • lt/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./DNSKEY (alg 8, id 20038)
  • ./DNSKEY (alg 8, id 20326)
  • NSEC3 proving non-existence of bnc.lt/DS
  • NSEC3 proving non-existence of hyundaicard.com/DS
  • com/DNSKEY (alg 13, id 19718)
  • com/DNSKEY (alg 13, id 59354)
  • com/DS (alg 13, id 19718)
  • lt/DNSKEY (alg 8, id 51241)
  • lt/DNSKEY (alg 8, id 60305)
  • lt/DS (alg 8, id 60305)

Delegation statusDelegation status

Insecure (2)
  • com to hyundaicard.com
  • lt to bnc.lt
Secure (2)
  • . to com
  • . to lt

NoticesNotices

Errors (2)
  • NSEC3 proving non-existence of bnc.lt/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 bnc.lt/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
Warnings (3)
  • NSEC3 proving non-existence of bnc.lt/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of bnc.lt/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • com to hyundaicard.com: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the com zone): hns1.hyundaicard.co.kr, hns2.hyundaicard.co.kr See RFC 1034, Sec. 4.2.2.

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