View on GitHub

DNSViz: A DNS visualization tool

uab.cat

Updated: 2023-05-01 09:56:50 UTC (447 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)
  • uab.cat/A
  • uab.cat/MX
  • uab.cat/NS
  • uab.cat/SOA
  • uab.cat/TXT
Secure (1)
  • cat/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 uab.cat/DS
  • cat/DNSKEY (alg 10, id 38453)
  • cat/DNSKEY (alg 10, id 58737)
  • cat/DS (alg 10, id 58737)

Delegation statusDelegation status

Insecure (1)
  • cat to uab.cat
Secure (1)
  • . to cat

NoticesNotices

Errors (18)
  • cat zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:620:0:ff::2f, 2001:678:e:110::53)
  • uab.cat zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (2001:40b0:1:1122:ce5c:a000:0:5)
  • uab.cat zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (2001:40b0:1:1122:ce5c:a000:0:5)
  • uab.cat zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (84.88.0.5)
  • uab.cat/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (84.88.0.5, UDP_-_NOEDNS_)
  • uab.cat/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (2001:40b0:1:1122:ce5c:a000:0:5, UDP_-_NOEDNS_)
  • uab.cat/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (2001:40b0:1:1122:ce5c:a000:0:5, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • uab.cat/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (2001:40b0:1:1122:ce5c:a000:0:5, UDP_-_EDNS0_512_D_KN, UDP_-_NOEDNS_)
  • uab.cat/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (84.88.0.5, UDP_-_NOEDNS_)
  • uab.cat/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (2001:40b0:1:1122:ce5c:a000:0:5, UDP_-_NOEDNS_)
  • uab.cat/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (2001:40b0:1:1122:ce5c:a000:0:5, TCP_-_NOEDNS_)
  • uab.cat/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (2001:40b0:1:1122:ce5c:a000:0:5, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • uab.cat/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (2001:40b0:1:1122:ce5c:a000:0:5, UDP_-_NOEDNS_)
  • cpiem2yj58.uab.cat/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • uab.cat/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
  • uab.cat/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • uab.cat/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • uab.cat/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
  • RRSIG NSEC3 proving non-existence of uab.cat/DS alg 10, id 38453: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG cat/DNSKEY alg 10, id 58737: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG cat/DNSKEY alg 10, id 58737: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG cat/SOA alg 10, id 38453: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • uab.cat/DS 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