View on GitHub

DNSViz: A DNS visualization tool

ens.fr

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

RRset statusRRset status

Insecure (5)
  • ens.fr/A
  • ens.fr/MX
  • ens.fr/NS
  • ens.fr/SOA
  • ens.fr/TXT
Secure (2)
  • fr/SOA
  • fr/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 26116)
  • ./DNSKEY (alg 8, id 46594)
  • NSEC3 proving non-existence of ens.fr/DS
  • fr/DNSKEY (alg 8, id 2134)
  • fr/DNSKEY (alg 8, id 35095)
  • fr/DS (alg 8, id 35095)

Delegation statusDelegation status

Insecure (1)
  • fr to ens.fr
Secure (1)
  • . to fr

NoticesNotices

Errors (4)
  • ./DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (192.112.36.4, UDP_-_EDNS0_512_D_K)
  • NSEC3 proving non-existence of ens.fr/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of ens.fr/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • ens.fr/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
  • NSEC3 proving non-existence of ens.fr/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of ens.fr/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • ens.fr/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