View on GitHub

DNSViz: A DNS visualization tool

teletalk.net.br

Updated: 2021-03-24 13:07:02 UTC (1339 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 (4)
  • teletalk.net.br/MX
  • teletalk.net.br/NS
  • teletalk.net.br/SOA
  • teletalk.net.br/TXT
Secure (1)
  • net.br/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Insecure (2)
  • teletalk.net.br/DNSKEY (alg 5, id 37243)
  • teletalk.net.br/DNSKEY (alg 5, id 48975)
Secure (9)
  • ./DNSKEY (alg 8, id 14631)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 42351)
  • NSEC3 proving non-existence of teletalk.net.br/DS
  • br/DNSKEY (alg 13, id 2471)
  • br/DNSKEY (alg 13, id 429)
  • br/DS (alg 13, id 2471)
  • net.br/DNSKEY (alg 13, id 42128)
  • net.br/DS (alg 13, id 42128)

Delegation statusDelegation status

Insecure (1)
  • net.br to teletalk.net.br
Secure (2)
  • . to br
  • br to net.br

NoticesNotices

Errors (3)
  • NSEC3 proving non-existence of teletalk.net.br/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 teletalk.net.br/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • teletalk.net.br/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (16)
  • NSEC3 proving non-existence of teletalk.net.br/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of teletalk.net.br/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • RRSIG teletalk.net.br/DNSKEY alg 5, id 37243: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG teletalk.net.br/DNSKEY alg 5, id 37243: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG teletalk.net.br/DNSKEY alg 5, id 48975: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG teletalk.net.br/DNSKEY alg 5, id 48975: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG teletalk.net.br/MX alg 5, id 48975: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG teletalk.net.br/NS alg 5, id 48975: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG teletalk.net.br/SOA alg 5, id 48975: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG teletalk.net.br/TXT alg 5, id 48975: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • teletalk.net.br/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • teletalk.net.br/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • teletalk.net.br/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • teletalk.net.br/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
  • li5xc2b7zm.teletalk.net.br/A has warnings; select the "Denial of existence" DNSSEC option to see them.
  • teletalk.net.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