View on GitHub

DNSViz: A DNS visualization tool

ualr.edu

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

RRset statusRRset status

Secure (6)
  • ualr.edu/A
  • ualr.edu/MX
  • ualr.edu/NS
  • ualr.edu/NSEC3PARAM
  • ualr.edu/SOA
  • ualr.edu/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (9)
  • ./DNSKEY (alg 8, id 11019)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46780)
  • edu/DNSKEY (alg 13, id 35663)
  • edu/DNSKEY (alg 13, id 8957)
  • edu/DS (alg 13, id 35663)
  • ualr.edu/DNSKEY (alg 7, id 1589)
  • ualr.edu/DNSKEY (alg 7, id 52161)
  • ualr.edu/DS (alg 7, id 52161)

Delegation statusDelegation status

Secure (2)
  • . to edu
  • edu to ualr.edu

NoticesNotices

Errors (9)
  • ualr.edu zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (2620:e8:0:5::32)
  • ualr.edu/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2620:e8:0:5::32, UDP_-_EDNS0_4096_D_KN)
  • ualr.edu/MX: No response was received from the server over TCP (tried 8 times). See RFC 1035, Sec. 4.2. (2620:e8:0:5::32, TCP_-_EDNS0_4096_D_N)
  • ualr.edu/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (2620:e8:0:5::32, TCP_-_EDNS0_4096_D_N)
  • ualr.edu/TXT: No response was received from the server over TCP (tried 4 times). See RFC 1035, Sec. 4.2. (2620:e8:0:5::32, TCP_-_EDNS0_4096_D_N)
  • ualr.edu/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • ualr.edu/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • ualr.edu/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • s9bqv2fp8x.ualr.edu/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (23)
  • RRSIG ualr.edu/A alg 7, id 1589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ualr.edu/DNSKEY alg 7, id 1589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ualr.edu/DNSKEY alg 7, id 1589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ualr.edu/DNSKEY alg 7, id 52161: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ualr.edu/DNSKEY alg 7, id 52161: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ualr.edu/MX alg 7, id 1589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ualr.edu/NS alg 7, id 1589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ualr.edu/NSEC3PARAM alg 7, id 1589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ualr.edu/SOA alg 7, id 1589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG ualr.edu/TXT alg 7, id 1589: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • edu to ualr.edu: Authoritative AAAA records exist for ns.ualr.edu, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • edu to ualr.edu: Authoritative AAAA records exist for ns2.ualr.edu, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • edu to ualr.edu: Authoritative AAAA records exist for ns3.ualr.edu, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
  • edu to ualr.edu: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the edu zone): ns6.ualr.edu, ns5.ualr.edu, ns7.net.ualr.edu See RFC 1034, Sec. 4.2.2.
  • ualr.edu/A: No response was received from the server over UDP (tried 7 times) until the NSID EDNS option was removed (however, this server appeared to respond legitimately to other queries with the NSID EDNS option present). See RFC 6891, Sec. 6.1.2. (2620:e8:0:5::32, UDP_-_EDNS0_4096_D_KN)
  • ualr.edu/DS (alg 7, id 52161): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ualr.edu/DS (alg 7, id 52161): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • ualr.edu/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. (2620:e8:0:5::32, UDP_-_EDNS0_4096_D_KN)
  • ualr.edu/SOA: 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. (2620:e8:0:5::32, UDP_-_EDNS0_4096_D_KN)
  • ualr.edu/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ualr.edu/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ualr.edu/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • s9bqv2fp8x.ualr.edu/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