View on GitHub

DNSViz: A DNS visualization tool

aalto.fi

Updated: 2021-02-12 17:00:56 UTC (1228 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (6)
  • aalto.fi/A
  • aalto.fi/AAAA
  • aalto.fi/MX
  • aalto.fi/NS
  • aalto.fi/SOA
  • aalto.fi/TXT
Secure (1)
  • fi/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 42351)
  • NSEC3 proving non-existence of aalto.fi/DS
  • fi/DNSKEY (alg 8, id 21309)
  • fi/DNSKEY (alg 8, id 24991)
  • fi/DNSKEY (alg 8, id 44855)
  • fi/DS (alg 8, id 44855)

Delegation statusDelegation status

Insecure (1)
  • fi to aalto.fi
Secure (1)
  • . to fi

NoticesNotices

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