View on GitHub

DNSViz: A DNS visualization tool

test.ep.cinebot.it

Updated: 2020-07-04 05:07:39 UTC (5 years 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 (2)
  • cinebot.it/SOA
  • test.ep.cinebot.it/A
Secure (1)
  • it/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 46594)
  • ./DNSKEY (alg 8, id 48903)
  • NSEC3 proving non-existence of cinebot.it/DS
  • it/DNSKEY (alg 10, id 18395)
  • it/DNSKEY (alg 10, id 41901)
  • it/DS (alg 10, id 41901)

Delegation statusDelegation status

Insecure (2)
  • cinebot.it to ep.cinebot.it
  • it to cinebot.it
Secure (1)
  • . to it

NoticesNotices

Errors (3)
  • NSEC3 proving non-existence of cinebot.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 cinebot.it/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • ep.cinebot.it/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (51.255.48.120, UDP_-_EDNS0_512_D_K, UDP_-_NOEDNS_)
Warnings (12)
  • NSEC3 proving non-existence of cinebot.it/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of cinebot.it/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of cinebot.it/DS alg 10, id 18395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG NSEC3 proving non-existence of cinebot.it/DS alg 10, id 18395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG it/DNSKEY alg 10, id 18395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG it/DNSKEY alg 10, id 18395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG it/DNSKEY alg 10, id 41901: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG it/DNSKEY alg 10, id 41901: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • RRSIG it/SOA alg 10, id 18395: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
  • test.ep.cinebot.it/A: The response had an invalid RCODE (SERVFAIL) until EDNS was disabled. See RFC 6891, Sec. 6.2.6. (51.255.48.120, UDP_-_EDNS0_4096_D_K)
  • test.ep.cinebot.it/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • ep.cinebot.it/CNAME 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