View on GitHub

DNSViz: A DNS visualization tool

google.com.au

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

RRset statusRRset status

Insecure (8)
  • google.com.au/A
  • google.com.au/A
  • google.com.au/AAAA
  • google.com.au/AAAA
  • google.com.au/MX
  • google.com.au/NS
  • google.com.au/SOA
  • google.com.au/TXT
Secure (1)
  • com.au/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46594)
  • NSEC3 proving non-existence of google.com.au/DS
  • au/DNSKEY (alg 8, id 17859)
  • au/DNSKEY (alg 8, id 18875)
  • au/DS (alg 8, id 18875)
  • au/DS (alg 8, id 18875)
  • com.au/DNSKEY (alg 8, id 14185)
  • com.au/DNSKEY (alg 8, id 14968)
  • com.au/DS (alg 8, id 14185)
  • com.au/DS (alg 8, id 14185)

Delegation statusDelegation status

Insecure (1)
  • com.au to google.com.au
Secure (2)
  • . to au
  • au to com.au

NoticesNotices

Errors (7)
  • NSEC3 proving non-existence of google.com.au/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 google.com.au/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • au/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (65.22.197.1, UDP_-_NOEDNS_)
  • au/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (65.22.197.1, UDP_-_EDNS0_512_D_K)
  • com.au zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (65.22.197.1)
  • com.au/DNSKEY: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (65.22.197.1, TCP_-_EDNS0_4096_D_K)
  • google.com.au/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (11)
  • NSEC3 proving non-existence of google.com.au/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of google.com.au/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • au/DS (alg 8, id 18875): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • au/DS (alg 8, id 18875): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • au/DS (alg 8, id 18875): 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.
  • au/DS (alg 8, id 18875): 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.
  • com.au/DS (alg 8, id 14185): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • com.au/DS (alg 8, id 14185): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • com.au/DS (alg 8, id 14185): 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.
  • com.au/DS (alg 8, id 14185): 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.
  • google.com.au/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