View on GitHub

DNSViz: A DNS visualization tool

177.in-addr.arpa

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

RRset statusRRset status

Secure (3)
  • 177.in-addr.arpa/NS
  • 177.in-addr.arpa/SOA
  • 177.in-addr.arpa/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (16)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26116)
  • 177.in-addr.arpa/DNSKEY (alg 8, id 4560)
  • 177.in-addr.arpa/DNSKEY (alg 8, id 5551)
  • 177.in-addr.arpa/DS (alg 8, id 5551)
  • 177.in-addr.arpa/DS (alg 8, id 5551)
  • arpa/DNSKEY (alg 8, id 42581)
  • arpa/DNSKEY (alg 8, id 4825)
  • 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 49608)
  • 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

Secure (3)
  • . to arpa
  • arpa to in-addr.arpa
  • in-addr.arpa to 177.in-addr.arpa

NoticesNotices

Errors (13)
  • 177.in-addr.arpa zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (200.0.68.10, 2801:14:a000::10)
  • 177.in-addr.arpa zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:13c7:7002:3000::10, 2001:13c7:7002:3000::11)
  • 177.in-addr.arpa/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (200.0.68.10, 2801:14:a000::10, UDP_-_NOEDNS_)
  • 177.in-addr.arpa/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (200.0.68.10, 2801:14:a000::10, UDP_-_EDNS0_512_D_K)
  • 177.in-addr.arpa/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:13c7:7002:3000::10, 2001:13c7:7002:3000::11, UDP_-_NOEDNS_)
  • 177.in-addr.arpa/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (200.0.68.10, 2801:14:a000::10, TCP_-_EDNS0_4096_D)
  • 177.in-addr.arpa/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (200.0.68.10, 2801:14:a000::10, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • 177.in-addr.arpa/TXT: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (200.0.68.10, 2801:14:a000::10, UDP_-_NOEDNS_)
  • in-addr.arpa zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:13c7:7010::53)
  • 177.in-addr.arpa/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • 177.in-addr.arpa/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • 177.in-addr.arpa/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • ski4gdm3n1.177.in-addr.arpa/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (14)
  • 177.in-addr.arpa/DNSKEY (alg 8, id 4560): 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. (202.12.31.53, UDP_-_EDNS0_4096_D_K)
  • 177.in-addr.arpa/DNSKEY (alg 8, id 5551): 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. (202.12.31.53, UDP_-_EDNS0_4096_D_K)
  • 177.in-addr.arpa/DS (alg 8, id 5551): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • 177.in-addr.arpa/DS (alg 8, id 5551): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • 177.in-addr.arpa/DS (alg 8, id 5551): 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.
  • 177.in-addr.arpa/DS (alg 8, id 5551): 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.
  • 177.in-addr.arpa/NS: 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. (2001:dd8:12::53, UDP_-_EDNS0_4096_D_K)
  • 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.
  • 177.in-addr.arpa/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • 177.in-addr.arpa/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ski4gdm3n1.177.in-addr.arpa/A 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