View on GitHub

DNSViz: A DNS visualization tool

_25._tcp.mx.tiviths.com.br

Updated: 2020-04-19 19:15:01 UTC (1678 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 (2)
  • _25._tcp.mx.tiviths.com.br/TLSA (NXDOMAIN)
  • _tcp.mx.tiviths.com.br/NS (NXDOMAIN)
Secure (2)
  • mx.tiviths.com.br/A
  • tiviths.com.br/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (13)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 48903)
  • NSEC3 proving non-existence of _25._tcp.mx.tiviths.com.br/TLSA
  • NSEC3 proving non-existence of _tcp.mx.tiviths.com.br/NS
  • br/DNSKEY (alg 13, id 19027)
  • br/DNSKEY (alg 13, id 2471)
  • br/DS (alg 13, id 2471)
  • com.br/DNSKEY (alg 13, id 2764)
  • com.br/DS (alg 13, id 2764)
  • tiviths.com.br/DNSKEY (alg 8, id 16504)
  • tiviths.com.br/DNSKEY (alg 8, id 53237)
  • tiviths.com.br/DS (alg 8, id 53237)
  • tiviths.com.br/DS (alg 8, id 53237)

Delegation statusDelegation status

Secure (3)
  • . to br
  • br to com.br
  • com.br to tiviths.com.br

NoticesNotices

Errors (5)
  • NSEC3 proving non-existence of _25._tcp.mx.tiviths.com.br/TLSA: 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 _25._tcp.mx.tiviths.com.br/TLSA: 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 _tcp.mx.tiviths.com.br/NS: 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 _tcp.mx.tiviths.com.br/NS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • tiviths.com.br/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (9)
  • NSEC3 proving non-existence of _25._tcp.mx.tiviths.com.br/TLSA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of _25._tcp.mx.tiviths.com.br/TLSA: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of _tcp.mx.tiviths.com.br/NS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of _tcp.mx.tiviths.com.br/NS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • tiviths.com.br/DS (alg 8, id 53237): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • tiviths.com.br/DS (alg 8, id 53237): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • tiviths.com.br/DS (alg 8, id 53237): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • tiviths.com.br/DS (alg 8, id 53237): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
  • tiviths.com.br/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