View on GitHub

DNSViz: A DNS visualization tool

ormanns.net

Updated: 2023-12-21 23:40:31 UTC (126 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Secure (7)
  • ormanns.net/A
  • ormanns.net/AAAA
  • ormanns.net/MX
  • ormanns.net/NS
  • ormanns.net/NSEC3PARAM
  • ormanns.net/SOA
  • ormanns.net/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 30903)
  • ./DNSKEY (alg 8, id 46780)
  • net/DNSKEY (alg 13, id 37331)
  • net/DNSKEY (alg 13, id 44222)
  • net/DS (alg 13, id 37331)
  • ormanns.net/DNSKEY (alg 8, id 2269)
  • ormanns.net/DNSKEY (alg 8, id 32541)
  • ormanns.net/DNSKEY (alg 8, id 56842)
  • ormanns.net/DNSKEY (alg 8, id 61173)
  • ormanns.net/DS (alg 8, id 2269)
  • ormanns.net/DS (alg 8, id 56842)

Delegation statusDelegation status

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

NoticesNotices

Errors (14)
  • ormanns.net zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. (212.83.56.201)
  • ormanns.net zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. (212.83.56.201)
  • ormanns.net zone: The server(s) were not responsive to queries over UDP. (2a00:f48:1003:1::2e53:926f)
  • ormanns.net/A: No response was received from the server over UDP (tried 12 times). (2a00:f48:1003:1::2e53:926f, UDP_-_NOEDNS_)
  • ormanns.net/A: The response had an invalid RCODE (REFUSED). (212.83.56.201, UDP_-_EDNS0_4096_D_KN)
  • ormanns.net/AAAA: The response had an invalid RCODE (REFUSED). (212.83.56.201, UDP_-_EDNS0_4096_D_KN)
  • ormanns.net/DNSKEY: The response had an invalid RCODE (REFUSED). (212.83.56.201, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • ormanns.net/MX: The response had an invalid RCODE (REFUSED). (212.83.56.201, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • ormanns.net/NS: No response was received from the server over UDP (tried 12 times). (2a00:f48:1003:1::2e53:926f, UDP_-_NOEDNS_)
  • ormanns.net/NS: The response had an invalid RCODE (REFUSED). (212.83.56.201, UDP_-_EDNS0_4096_D_KN)
  • ormanns.net/NSEC3PARAM: The response had an invalid RCODE (REFUSED). (212.83.56.201, UDP_-_EDNS0_4096_D_KN)
  • ormanns.net/SOA: The response had an invalid RCODE (REFUSED). (212.83.56.201, TCP_-_EDNS0_4096_D_N)
  • ormanns.net/SOA: The response had an invalid RCODE (REFUSED). (212.83.56.201, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • ormanns.net/TXT: The response had an invalid RCODE (REFUSED). (212.83.56.201, UDP_-_EDNS0_4096_D_KN)
Warnings (1)
  • net to ormanns.net: The glue address(es) for ns3.ormanns.net (212.83.56.201) differed from its authoritative address(es) (62.113.204.214).

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