View on GitHub

DNSViz: A DNS visualization tool

rezosup.net

Updated: 2024-02-16 22:10:29 UTC (280 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

Secure (6)
  • rezosup.net/A
  • rezosup.net/AAAA
  • rezosup.net/MX
  • rezosup.net/NS
  • rezosup.net/SOA
  • rezosup.net/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 30903)
  • net/DNSKEY (alg 13, id 34730)
  • net/DNSKEY (alg 13, id 37331)
  • net/DS (alg 13, id 37331)
  • rezosup.net/DNSKEY (alg 14, id 13243)
  • rezosup.net/DNSKEY (alg 14, id 31341)
  • rezosup.net/DS (alg 14, id 31341)

Delegation statusDelegation status

Secure (2)
  • . to net
  • net to rezosup.net

NoticesNotices

Errors (4)
  • rezosup.net zone: The following NS name(s) did not resolve to address(es): ns1.rezel.net
  • rezosup.net zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (212.129.30.44, 2001:bc8:226f:f02::1)
  • rezosup.net/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (212.129.30.44, 2001:bc8:226f:f02::1, UDP_-_NOEDNS_)
  • rezosup.net/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (212.129.30.44, 2001:bc8:226f:f02::1, UDP_-_NOEDNS_)

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