View on GitHub

DNSViz: A DNS visualization tool

253.41.196.in-addr.arpa

Updated: 2024-05-27 09:59:03 UTC (179 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

Secure (3)
  • 253.41.196.in-addr.arpa/NS
  • 253.41.196.in-addr.arpa/NSEC3PARAM
  • 253.41.196.in-addr.arpa/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (23)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 5613)
  • 196.in-addr.arpa/DNSKEY (alg 8, id 15009)
  • 196.in-addr.arpa/DNSKEY (alg 8, id 48389)
  • 196.in-addr.arpa/DS (alg 8, id 48389)
  • 196.in-addr.arpa/DS (alg 8, id 54334)
  • 253.41.196.in-addr.arpa/DNSKEY (alg 8, id 26400)
  • 253.41.196.in-addr.arpa/DNSKEY (alg 8, id 43076)
  • 253.41.196.in-addr.arpa/DNSKEY (alg 8, id 48109)
  • 253.41.196.in-addr.arpa/DNSKEY (alg 8, id 50992)
  • 253.41.196.in-addr.arpa/DNSKEY (alg 8, id 52365)
  • 253.41.196.in-addr.arpa/DS (alg 8, id 43076)
  • 253.41.196.in-addr.arpa/DS (alg 8, id 43076)
  • 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 (3)
  • 196.in-addr.arpa/DNSKEY (alg 8, id 54334)
  • in-addr.arpa/DNSKEY (alg 8, id 53696)
  • in-addr.arpa/DNSKEY (alg 8, id 63982)

Delegation statusDelegation status

Secure (4)
  • . to arpa
  • 196.in-addr.arpa to 253.41.196.in-addr.arpa
  • arpa to in-addr.arpa
  • in-addr.arpa to 196.in-addr.arpa

NoticesNotices

Errors (16)
  • 196.in-addr.arpa to 253.41.196.in-addr.arpa: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (197.140.10.155, UDP_-_EDNS0_4096_D_KN)
  • 196.in-addr.arpa to 253.41.196.in-addr.arpa: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (197.140.10.155, UDP_-_EDNS0_4096_D_KN)
  • 253.41.196.in-addr.arpa zone: The following NS name(s) did not resolve to address(es): ns01icosnet
  • 253.41.196.in-addr.arpa/DNSKEY (alg 8, id 26400): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (197.140.10.155, UDP_-_EDNS0_4096_D_KN)
  • 253.41.196.in-addr.arpa/DNSKEY (alg 8, id 43076): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (197.140.10.155, UDP_-_EDNS0_4096_D_KN)
  • 253.41.196.in-addr.arpa/DNSKEY (alg 8, id 48109): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (197.140.10.155, UDP_-_EDNS0_4096_D_KN)
  • 253.41.196.in-addr.arpa/DNSKEY (alg 8, id 50992): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (197.140.10.155, UDP_-_EDNS0_4096_D_KN)
  • 253.41.196.in-addr.arpa/DNSKEY (alg 8, id 52365): No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (197.140.10.155, UDP_-_EDNS0_4096_D_KN)
  • 253.41.196.in-addr.arpa/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (197.140.10.155, UDP_-_EDNS0_4096_D_KN)
  • 253.41.196.in-addr.arpa/NSEC3PARAM: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (197.140.10.155, UDP_-_EDNS0_4096_D_KN)
  • 253.41.196.in-addr.arpa/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (197.140.10.155, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • 253.41.196.in-addr.arpa/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • 253.41.196.in-addr.arpa/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
  • 253.41.196.in-addr.arpa/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • mjwskoxhc8.253.41.196.in-addr.arpa/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • 253.41.196.in-addr.arpa/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (15)
  • 196.in-addr.arpa to 253.41.196.in-addr.arpa: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the 196.in-addr.arpa zone): ns01icosnet See RFC 1034, Sec. 4.2.2.
  • 253.41.196.in-addr.arpa/DNSKEY (alg 8, id 26400): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (197.140.11.1, UDP_-_EDNS0_4096_D_KN)
  • 253.41.196.in-addr.arpa/DNSKEY (alg 8, id 43076): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (197.140.11.1, UDP_-_EDNS0_4096_D_KN)
  • 253.41.196.in-addr.arpa/DNSKEY (alg 8, id 48109): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (197.140.11.1, UDP_-_EDNS0_4096_D_KN)
  • 253.41.196.in-addr.arpa/DNSKEY (alg 8, id 50992): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (197.140.11.1, UDP_-_EDNS0_4096_D_KN)
  • 253.41.196.in-addr.arpa/DNSKEY (alg 8, id 52365): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (197.140.11.1, UDP_-_EDNS0_4096_D_KN)
  • 253.41.196.in-addr.arpa/DS (alg 8, id 43076): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • 253.41.196.in-addr.arpa/DS (alg 8, id 43076): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • 253.41.196.in-addr.arpa/DS (alg 8, id 43076): 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.
  • 253.41.196.in-addr.arpa/DS (alg 8, id 43076): 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.
  • 253.41.196.in-addr.arpa/MX has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 253.41.196.in-addr.arpa/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 253.41.196.in-addr.arpa/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • mjwskoxhc8.253.41.196.in-addr.arpa/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 253.41.196.in-addr.arpa/TXT 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