View on GitHub

DNSViz: A DNS visualization tool

1.1.1.1.in-addr.arpa

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

RRset statusRRset status

Insecure (1)
  • 1.1.1.1.in-addr.arpa/PTR
Secure (1)
  • 1.in-addr.arpa/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (16)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 9799)
  • 1.in-addr.arpa/DNSKEY (alg 13, id 23004)
  • 1.in-addr.arpa/DNSKEY (alg 13, id 38172)
  • 1.in-addr.arpa/DS (alg 13, id 23004)
  • NSEC3 proving non-existence of 1.1.1.in-addr.arpa/DS
  • arpa/DNSKEY (alg 8, id 31455)
  • arpa/DNSKEY (alg 8, id 42581)
  • arpa/DS (alg 8, id 42581)
  • arpa/DS (alg 8, id 42581)
  • in-addr.arpa/DNSKEY (alg 8, id 47054)
  • in-addr.arpa/DNSKEY (alg 8, id 5314)
  • 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 63982)
Non_existent (2)
  • in-addr.arpa/DNSKEY (alg 8, id 53696)
  • in-addr.arpa/DNSKEY (alg 8, id 63982)

Delegation statusDelegation status

Insecure (1)
  • 1.in-addr.arpa to 1.1.1.in-addr.arpa
Secure (3)
  • . to arpa
  • arpa to in-addr.arpa
  • in-addr.arpa to 1.in-addr.arpa

NoticesNotices

Errors (2)
  • NSEC3 proving non-existence of 1.1.1.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 1.1.1.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.
Warnings (8)
  • 1.in-addr.arpa to 1.1.1.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 1.in-addr.arpa zone): mira.ns.cloudflare.com, alec.ns.cloudflare.com See RFC 1034, Sec. 4.2.2.
  • 1.in-addr.arpa to 1.1.1.in-addr.arpa: The following NS name(s) were found in the delegation NS RRset (i.e., in the 1.in-addr.arpa zone), but not in the authoritative NS RRset: ns3.cloudflare.com, ns7.cloudflare.com See RFC 1034, Sec. 4.2.2.
  • NSEC3 proving non-existence of 1.1.1.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 1.1.1.in-addr.arpa/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • arpa/DS (alg 8, id 42581): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • arpa/DS (alg 8, id 42581): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • arpa/DS (alg 8, id 42581): 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.
  • arpa/DS (alg 8, id 42581): 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.

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