View on GitHub

DNSViz: A DNS visualization tool

fu-berlin.de

Updated: 2023-06-05 07:00:23 UTC (491 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)
  • fu-berlin.de/A
  • fu-berlin.de/MX
  • fu-berlin.de/NS
  • fu-berlin.de/SOA
  • fu-berlin.de/TXT
Secure (2)
  • de/SOA
  • de/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 60955)
  • NSEC3 proving non-existence of fu-berlin.de/DS
  • de/DNSKEY (alg 8, id 16614)
  • de/DNSKEY (alg 8, id 26755)
  • de/DNSKEY (alg 8, id 64125)
  • de/DS (alg 8, id 26755)

Delegation statusDelegation status

Insecure (1)
  • de to fu-berlin.de
Secure (1)
  • . to de

NoticesNotices

Errors (3)
  • NSEC3 proving non-existence of fu-berlin.de/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 fu-berlin.de/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • fu-berlin.de/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
  • NSEC3 proving non-existence of fu-berlin.de/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of fu-berlin.de/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • fu-berlin.de/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