View on GitHub

DNSViz: A DNS visualization tool

www.verisign.com

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

RRset statusRRset status

Insecure (3)
  • www.verisign.com/A
  • www.verisign.com/AAAA
  • www.verisign.com/AAAA
Secure (1)
  • verisign.com/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 33853)
  • ./DNSKEY (alg 8, id 48903)
  • NSEC3 proving non-existence of www.verisign.com/DS
  • com/DNSKEY (alg 8, id 30909)
  • com/DNSKEY (alg 8, id 56311)
  • com/DS (alg 8, id 30909)
  • verisign.com/DNSKEY (alg 8, id 13548)
  • verisign.com/DNSKEY (alg 8, id 55204)
  • verisign.com/DS (alg 8, id 55204)

Delegation statusDelegation status

Insecure (1)
  • verisign.com to www.verisign.com
Secure (2)
  • . to com
  • com to verisign.com

NoticesNotices

Errors (13)
  • NSEC3 proving non-existence of www.verisign.com/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 www.verisign.com/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • www.verisign.com zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (2620:74:13::16, 2620:74:14::16)
  • www.verisign.com/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2620:74:13::16, 2620:74:14::16, UDP_-_NOEDNS_)
  • www.verisign.com/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2620:74:13::16, 2620:74:14::16, UDP_-_EDNS0_512_D_K)
  • www.verisign.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • www.verisign.com/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • www.verisign.com/SOA has errors; select the "Denial of existence" DNSSEC option to see them.
  • www.verisign.com/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
  • www.verisign.com/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • www.verisign.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • 0w9der42zy.www.verisign.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • www.verisign.com/NS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
  • NSEC3 proving non-existence of www.verisign.com/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of www.verisign.com/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • verisign.com to www.verisign.com: The following NS name(s) were found in the delegation NS RRset (i.e., in the verisign.com zone), but not in the authoritative NS RRset: gslb.shared-fo.brn1.verisign.com, gslb.shared-fo.ilg1.verisign.com See RFC 1034, Sec. 4.2.2.
  • www.verisign.com/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