View on GitHub

DNSViz: A DNS visualization tool

transparencia.itacaja.to.gov.br

Updated: 2022-05-03 03:20:02 UTC (733 days ago) Update now
« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Insecure (2)
  • transparencia.itacaja.to.gov.br/CNAME
  • vps-aws.dattasystem.com.br/A
Secure (2)
  • com.br/SOA
  • to.gov.br/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (15)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 47671)
  • NSEC proving non-existence of itacaja.to.gov.br/DS
  • NSEC3 proving non-existence of dattasystem.com.br/DS
  • br/DNSKEY (alg 13, id 24560)
  • br/DNSKEY (alg 13, id 2471)
  • br/DNSKEY (alg 13, id 6416)
  • br/DS (alg 13, id 2471)
  • com.br/DNSKEY (alg 13, id 18076)
  • com.br/DS (alg 13, id 18076)
  • gov.br/DNSKEY (alg 13, id 18076)
  • gov.br/DS (alg 13, id 18076)
  • to.gov.br/DNSKEY (alg 5, id 2524)
  • to.gov.br/DNSKEY (alg 5, id 58636)
  • to.gov.br/DS (alg 5, id 2524)

Delegation statusDelegation status

Insecure (2)
  • com.br to dattasystem.com.br
  • to.gov.br to itacaja.to.gov.br
Secure (4)
  • . to br
  • br to com.br
  • br to gov.br
  • gov.br to to.gov.br

NoticesNotices

Errors (5)
  • dattasystem.com.br/DNSKEY: No response was received from the server over UDP (tried 4 times). (191.252.128.163, UDP_-_EDNS0_512_D_KN)
  • dattasystem.com.br/DNSKEY: No response was received from the server over UDP (tried 5 times). (191.252.128.162, UDP_-_EDNS0_512_D_KN)
  • itacaja.to.gov.br/DNSKEY: No response was received from the server over UDP (tried 5 times). (191.252.128.163, UDP_-_EDNS0_512_D_KN)
  • itacaja.to.gov.br/DNSKEY: No response was received from the server over UDP (tried 6 times). (191.252.128.162, UDP_-_EDNS0_512_D_KN)
  • itacaja.to.gov.br/DNSKEY: The UDP connection was refused (ECONNREFUSED). (191.252.128.162, UDP_-_NOEDNS_)
Warnings (22)
  • RRSIG NSEC proving non-existence of itacaja.to.gov.br/DS alg 5, id 2524: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
  • RRSIG NSEC proving non-existence of itacaja.to.gov.br/DS alg 5, id 2524: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
  • RRSIG NSEC proving non-existence of itacaja.to.gov.br/DS alg 5, id 58636: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
  • RRSIG NSEC proving non-existence of itacaja.to.gov.br/DS alg 5, id 58636: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
  • RRSIG to.gov.br/DNSKEY alg 5, id 2524: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
  • RRSIG to.gov.br/DNSKEY alg 5, id 2524: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
  • RRSIG to.gov.br/DNSKEY alg 5, id 2524: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
  • RRSIG to.gov.br/DNSKEY alg 5, id 2524: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
  • RRSIG to.gov.br/DNSKEY alg 5, id 58636: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
  • RRSIG to.gov.br/DNSKEY alg 5, id 58636: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
  • RRSIG to.gov.br/DNSKEY alg 5, id 58636: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
  • RRSIG to.gov.br/DNSKEY alg 5, id 58636: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
  • RRSIG to.gov.br/SOA alg 5, id 2524: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
  • RRSIG to.gov.br/SOA alg 5, id 2524: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
  • RRSIG to.gov.br/SOA alg 5, id 58636: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
  • RRSIG to.gov.br/SOA alg 5, id 58636: DNSSEC specification recommends not signing with DNSSEC algorithm 5 (RSASHA1).
  • com.br to dattasystem.com.br: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the com.br zone): dns3.dattasystem.com.br, dns4.dattasystem.com.br
  • gov.br to to.gov.br: The glue address(es) for ns.to.gov.br (187.29.146.1) differed from its authoritative address(es) (128.201.16.20, 131.72.217.1, 131.72.217.20, 187.29.146.1, 187.29.146.20).
  • to.gov.br to itacaja.to.gov.br: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the to.gov.br zone): ns1.itacaja.to.gov.br, ns2.itacaja.to.gov.br
  • to.gov.br to itacaja.to.gov.br: The following NS name(s) were found in the delegation NS RRset (i.e., in the to.gov.br zone), but not in the authoritative NS RRset: dns1.dattasystem.com.br, dns2.dattasystem.com.br, dns3.dattasystem.com.br, dns4.dattasystem.com.br
  • to.gov.br/DS (alg 5, id 2524): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).
  • to.gov.br/DS (alg 5, id 2524): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1).

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