View on GitHub

DNSViz: A DNS visualization tool

sylnt.us

Updated: 2021-06-14 03:47:28 UTC (1095 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Secure (5)
  • sylnt.us/A
  • sylnt.us/AAAA
  • sylnt.us/NS
  • sylnt.us/SOA
  • sylnt.us/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (10)
  • ./DNSKEY (alg 8, id 14631)
  • ./DNSKEY (alg 8, id 20326)
  • sylnt.us/DNSKEY (alg 8, id 11227)
  • sylnt.us/DNSKEY (alg 8, id 5595)
  • sylnt.us/DS (alg 8, id 11227)
  • sylnt.us/DS (alg 8, id 5595)
  • us/DNSKEY (alg 8, id 21364)
  • us/DNSKEY (alg 8, id 53985)
  • us/DS (alg 8, id 21364)
  • us/DS (alg 8, id 21364)

Delegation statusDelegation status

Secure (2)
  • . to us
  • us to sylnt.us

NoticesNotices

Errors (15)
  • sylnt.us zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (45.33.35.220)
  • sylnt.us zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (45.33.35.220)
  • sylnt.us/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (45.33.35.220, UDP_-_EDNS0_4096_D_KN)
  • sylnt.us/AAAA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (45.33.35.220, UDP_-_EDNS0_4096_D_KN)
  • sylnt.us/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (45.33.35.220, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • sylnt.us/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (45.33.35.220, UDP_-_EDNS0_4096_D_KN)
  • sylnt.us/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (45.33.35.220, TCP_-_EDNS0_4096_D_N)
  • sylnt.us/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (45.33.35.220, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • sylnt.us/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (45.33.35.220, UDP_-_EDNS0_4096_D_KN)
  • us/DS (alg 8, id 21364): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • us/DS (alg 8, id 21364): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • sylnt.us/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • wri96opgt3.sylnt.us/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • sylnt.us/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • sylnt.us/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
  • us to sylnt.us: The following NS name(s) were found in the delegation NS RRset (i.e., in the us zone), but not in the authoritative NS RRset: remote.demmers.org See RFC 1034, Sec. 4.2.2.
  • us/DS (alg 8, id 21364): 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.
  • us/DS (alg 8, id 21364): 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