View on GitHub

DNSViz: A DNS visualization tool

3lineofcode.in

Updated: 2023-04-13 15:59:32 UTC (979 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

Insecure (4)
  • 3lineofcode.in/A
  • 3lineofcode.in/NS
  • 3lineofcode.in/SOA
  • 3lineofcode.in/TXT
Secure (1)
  • in/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (6)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • NSEC3 proving non-existence of 3lineofcode.in/DS
  • in/DNSKEY (alg 8, id 54739)
  • in/DNSKEY (alg 8, id 65169)
  • in/DS (alg 8, id 54739)

Delegation statusDelegation status

Insecure (1)
  • in to 3lineofcode.in
Secure (1)
  • . to in

NoticesNotices

Errors (14)
  • 3lineofcode.in zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (97.74.108.19, 173.201.76.19, 2603:5:21c1::13, 2603:5:22c1::13)
  • 3lineofcode.in zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (97.74.108.19, 173.201.76.19, 2603:5:21c1::13, 2603:5:22c1::13)
  • 3lineofcode.in/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (97.74.108.19, 173.201.76.19, 2603:5:21c1::13, 2603:5:22c1::13, UDP_-_EDNS0_4096_D_KN)
  • 3lineofcode.in/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (97.74.108.19, 173.201.76.19, 2603:5:21c1::13, 2603:5:22c1::13, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • 3lineofcode.in/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (97.74.108.19, 173.201.76.19, 2603:5:21c1::13, 2603:5:22c1::13, UDP_-_EDNS0_4096_D_KN)
  • 3lineofcode.in/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (97.74.108.19, 173.201.76.19, 2603:5:21c1::13, 2603:5:22c1::13, TCP_-_EDNS0_4096_D_N)
  • 3lineofcode.in/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (97.74.108.19, 173.201.76.19, 2603:5:21c1::13, 2603:5:22c1::13, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • 3lineofcode.in/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (97.74.108.19, 173.201.76.19, 2603:5:21c1::13, 2603:5:22c1::13, UDP_-_EDNS0_4096_D_KN)
  • 3lineofcode.in/MX has errors; select the "Denial of existence" DNSSEC option to see them.
  • 3lineofcode.in/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • kx65y70quz.3lineofcode.in/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • 3lineofcode.in/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • 3lineofcode.in/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • 3lineofcode.in/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (1)
  • in to 3lineofcode.in: The following NS name(s) were found in the delegation NS RRset (i.e., in the in zone), but not in the authoritative NS RRset: ns37.domaincontrol.com, ns38.domaincontrol.com See RFC 1034, Sec. 4.2.2.

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