View on GitHub

DNSViz: A DNS visualization tool

180.96.34.in-addr.arpa

Updated: 2024-04-25 04:42:20 UTC (12 months 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 (3)
  • 180.96.34.in-addr.arpa/NS
  • 180.96.34.in-addr.arpa/NSEC3PARAM
  • 180.96.34.in-addr.arpa/SOA
Secure (1)
  • 34.in-addr.arpa/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (3)
  • 180.96.34.in-addr.arpa/DNSKEY (alg 8, id 29265)
  • 180.96.34.in-addr.arpa/DNSKEY (alg 8, id 60422)
  • NSEC3 proving non-existence of 180.96.34.in-addr.arpa/DS
Secure (18)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 5613)
  • 34.in-addr.arpa/DNSKEY (alg 8, id 11366)
  • 34.in-addr.arpa/DNSKEY (alg 8, id 2274)
  • 34.in-addr.arpa/DNSKEY (alg 8, id 34368)
  • 34.in-addr.arpa/DNSKEY (alg 8, id 35137)
  • 34.in-addr.arpa/DS (alg 8, id 11366)
  • NSEC proving non-existence of 96.34.in-addr.arpa/DS
  • arpa/DNSKEY (alg 8, id 42581)
  • arpa/DNSKEY (alg 8, id 43060)
  • arpa/DS (alg 8, id 42581)
  • in-addr.arpa/DNSKEY (alg 8, id 37980)
  • in-addr.arpa/DNSKEY (alg 8, id 47054)
  • in-addr.arpa/DNSKEY (alg 8, id 54956)
  • in-addr.arpa/DS (alg 8, id 47054)
  • in-addr.arpa/DS (alg 8, id 53696)
  • in-addr.arpa/DS (alg 8, id 54956)
  • in-addr.arpa/DS (alg 8, id 63982)
Non_existent (2)
  • in-addr.arpa/DNSKEY (alg 8, id 53696)
  • in-addr.arpa/DNSKEY (alg 8, id 63982)

Delegation statusDelegation status

Lame (1)
  • 34.in-addr.arpa to 96.34.in-addr.arpa
Insecure (1)
  • 96.34.in-addr.arpa to 180.96.34.in-addr.arpa
Secure (3)
  • . to arpa
  • arpa to in-addr.arpa
  • in-addr.arpa to 34.in-addr.arpa

NoticesNotices

Errors (13)
  • 96.34.in-addr.arpa to 180.96.34.in-addr.arpa: An SOA RR with owner name (180.96.34.in-addr.arpa) not matching the zone name (96.34.in-addr.arpa) was returned with the NODATA response. See RFC 1034, Sec. 4.3.4, RFC 2308, Sec. 2.2. (216.239.32.102, 216.239.34.102, 216.239.36.102, 216.239.38.102, 2001:4860:4802:32::66, 2001:4860:4802:34::66, 2001:4860:4802:36::66, 2001:4860:4802:38::66, UDP_-_EDNS0_4096_D_KN)
  • 96.34.in-addr.arpa zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (216.239.32.102, 216.239.34.102, 216.239.36.102, 216.239.38.102, 2001:4860:4802:32::66, 2001:4860:4802:34::66, 2001:4860:4802:36::66, 2001:4860:4802:38::66)
  • 96.34.in-addr.arpa/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (216.239.32.102, 216.239.34.102, 216.239.36.102, 216.239.38.102, 2001:4860:4802:32::66, 2001:4860:4802:34::66, 2001:4860:4802:36::66, 2001:4860:4802:38::66, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • NSEC3 proving non-existence of 180.96.34.in-addr.arpa/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 180.96.34.in-addr.arpa/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 180.96.34.in-addr.arpa/DS: The SOA bit was set in the bitmap of the NSEC3 RR corresponding to the delegated name (180.96.34.in-addr.arpa). See RFC 5155, Sec. 8.9.
  • NSEC3 proving non-existence of 180.96.34.in-addr.arpa/DS: The SOA bit was set in the bitmap of the NSEC3 RR corresponding to the delegated name (180.96.34.in-addr.arpa). See RFC 5155, Sec. 8.9.
  • RRSIG NSEC3 proving non-existence of 180.96.34.in-addr.arpa/DS alg 8, id 29265: The Signer's Name field of the RRSIG RR (180.96.34.in-addr.arpa) does not match the name of the zone containing the RRset (96.34.in-addr.arpa). See RFC 4035, Sec. 5.3.1.
  • 180.96.34.in-addr.arpa/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • 180.96.34.in-addr.arpa/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
  • boqsmwe37n.180.96.34.in-addr.arpa/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • 180.96.34.in-addr.arpa/DS has errors; select the "Denial of existence" DNSSEC option to see them.
  • 180.96.34.in-addr.arpa/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (7)
  • NSEC3 proving non-existence of 180.96.34.in-addr.arpa/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of 180.96.34.in-addr.arpa/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • 180.96.34.in-addr.arpa/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 180.96.34.in-addr.arpa/TXT has warnings; select the "Denial of existence" DNSSEC option to see them.
  • boqsmwe37n.180.96.34.in-addr.arpa/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 180.96.34.in-addr.arpa/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 180.96.34.in-addr.arpa/CNAME 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