View on GitHub

DNSViz: A DNS visualization tool

sns.it

Updated: 2022-10-09 10:08:48 UTC (613 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 (5)
  • sns.it/MX
  • sns.it/NS
  • sns.it/SOA
  • sns.it/SOA
  • sns.it/TXT
Secure (2)
  • it/SOA
  • it/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (8)
  • ./DNSKEY (alg 8, id 18733)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 20826)
  • NSEC3 proving non-existence of sns.it/DS
  • NSEC3 proving non-existence of sns.it/DS
  • it/DNSKEY (alg 10, id 18395)
  • it/DNSKEY (alg 10, id 41901)
  • it/DS (alg 10, id 41901)

Delegation statusDelegation status

Insecure (1)
  • it to sns.it
Secure (1)
  • . to it

NoticesNotices

Errors (5)
  • NSEC3 proving non-existence of sns.it/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 sns.it/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 sns.it/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 sns.it/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • sns.it/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (21)
  • NSEC3 proving non-existence of sns.it/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of sns.it/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of sns.it/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of sns.it/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of sns.it/DS alg 10, id 18395: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of sns.it/DS alg 10, id 18395: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of sns.it/DS alg 10, id 18395: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of sns.it/DS alg 10, id 18395: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG it/DNSKEY alg 10, id 18395: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG it/DNSKEY alg 10, id 18395: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG it/DNSKEY alg 10, id 18395: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG it/DNSKEY alg 10, id 18395: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG it/DNSKEY alg 10, id 41901: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG it/DNSKEY alg 10, id 41901: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG it/DNSKEY alg 10, id 41901: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG it/DNSKEY alg 10, id 41901: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG it/SOA alg 10, id 18395: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG it/SOA alg 10, id 18395: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • sns.it/SOA: The case of the query name (SnS.it) was not preserved in the Question section of the response. (40.90.4.8, UDP_-_EDNS0_4096_D_KN_0x20)
  • sns.it/SOA: The case of the query name (sns.it) was not preserved in the Question section of the response. (64.4.48.8, 2603:1061:0:700::8, UDP_-_EDNS0_4096_D_KN)
  • sns.it/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