View on GitHub

DNSViz: A DNS visualization tool

lamar.edu

Updated: 2023-03-30 16:28:07 UTC (601 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 (5)
  • lamar.edu/A
  • lamar.edu/MX
  • lamar.edu/NS
  • lamar.edu/SOA
  • lamar.edu/TXT
Secure (1)
  • edu/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • ./DNSKEY (alg 8, id 951)
  • NSEC3 proving non-existence of lamar.edu/DS
  • edu/DNSKEY (alg 8, id 28065)
  • edu/DNSKEY (alg 8, id 34085)
  • edu/DS (alg 8, id 28065)

Delegation statusDelegation status

Insecure (1)
  • edu to lamar.edu
Secure (1)
  • . to edu

NoticesNotices

Errors (17)
  • lamar.edu zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (140.158.64.6)
  • lamar.edu zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (140.158.64.6)
  • lamar.edu zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (147.26.255.7)
  • lamar.edu/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (147.26.255.7, UDP_-_NOEDNS_)
  • lamar.edu/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (140.158.64.6, UDP_-_NOEDNS_)
  • lamar.edu/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (140.158.64.6, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • lamar.edu/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (140.158.64.6, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • lamar.edu/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (147.26.255.7, UDP_-_NOEDNS_)
  • lamar.edu/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (140.158.64.6, UDP_-_NOEDNS_)
  • lamar.edu/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (140.158.64.6, TCP_-_NOEDNS_)
  • lamar.edu/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (140.158.64.6, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • lamar.edu/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (140.158.64.6, UDP_-_NOEDNS_)
  • lamar.edu/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • bd2s0tnu7g.lamar.edu/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • lamar.edu/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • lamar.edu/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • lamar.edu/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (1)
  • edu to lamar.edu: The following NS name(s) were found in the delegation NS RRset (i.e., in the edu zone), but not in the authoritative NS RRset: dr-dns1.lamar.edu 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