View on GitHub

DNSViz: A DNS visualization tool

anatel.gov.br

Updated: 2024-01-09 15:07:07 UTC (318 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

Secure (5)
  • anatel.gov.br/A
  • anatel.gov.br/AAAA
  • anatel.gov.br/MX
  • anatel.gov.br/NS
  • anatel.gov.br/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (14)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 30903)
  • ./DNSKEY (alg 8, id 46780)
  • anatel.gov.br/DNSKEY (alg 5, id 32418)
  • anatel.gov.br/DNSKEY (alg 5, id 42127)
  • anatel.gov.br/DS (alg 5, id 42127)
  • anatel.gov.br/DS (alg 5, id 42127)
  • br/DNSKEY (alg 13, id 16486)
  • br/DNSKEY (alg 13, id 38298)
  • br/DS (alg 13, id 38298)
  • gov.br/DNSKEY (alg 13, id 4011)
  • gov.br/DNSKEY (alg 13, id 52091)
  • gov.br/DS (alg 13, id 4011)
  • gov.br/DS (alg 13, id 52091)

Delegation statusDelegation status

Secure (3)
  • . to br
  • br to gov.br
  • gov.br to anatel.gov.br

NoticesNotices

Errors (16)
  • anatel.gov.br zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (2801:80:c90:c1da:da0::67, 2801:80:c90:c1da:da0::68)
  • anatel.gov.br zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (200.0.81.67, 200.0.81.68)
  • anatel.gov.br zone: There was an error resolving the following NS name(s) to address(es): anatelns1.anatel.gov.br, anatelns2.anatel.gov.br
  • anatel.gov.br/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (200.0.81.67, 200.0.81.68, UDP_-_NOEDNS_)
  • anatel.gov.br/AAAA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2801:80:c90:c1da:da0::67, UDP_-_NOEDNS_)
  • anatel.gov.br/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2801:80:c90:c1da:da0::68, UDP_-_NOEDNS_)
  • anatel.gov.br/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2801:80:c90:c1da:da0::67, 2801:80:c90:c1da:da0::68, UDP_-_EDNS0_512_D_KN)
  • anatel.gov.br/MX: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2801:80:c90:c1da:da0::67, 2801:80:c90:c1da:da0::68, UDP_-_NOEDNS_)
  • anatel.gov.br/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2801:80:c90:c1da:da0::67, UDP_-_EDNS0_512_D_KN)
  • anatel.gov.br/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (200.0.81.67, 200.0.81.68, UDP_-_NOEDNS_)
  • anatel.gov.br/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (2801:80:c90:c1da:da0::67, 2801:80:c90:c1da:da0::68, TCP_-_EDNS0_4096_D_N)
  • anatel.gov.br/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2801:80:c90:c1da:da0::67, 2801:80:c90:c1da:da0::68, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
  • anatel.gov.br/TXT: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2801:80:c90:c1da:da0::67, 2801:80:c90:c1da:da0::68, UDP_-_NOEDNS_)
  • eql7mvikth.anatel.gov.br/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • anatel.gov.br/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • anatel.gov.br/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (15)
  • RRSIG anatel.gov.br/A alg 5, id 32418: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG anatel.gov.br/AAAA alg 5, id 32418: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG anatel.gov.br/DNSKEY alg 5, id 32418: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG anatel.gov.br/DNSKEY alg 5, id 32418: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG anatel.gov.br/DNSKEY alg 5, id 42127: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG anatel.gov.br/DNSKEY alg 5, id 42127: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG anatel.gov.br/MX alg 5, id 32418: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG anatel.gov.br/NS alg 5, id 32418: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • RRSIG anatel.gov.br/SOA alg 5, id 32418: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
  • anatel.gov.br/DS (alg 5, id 42127): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • anatel.gov.br/DS (alg 5, id 42127): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • anatel.gov.br/DS (alg 5, id 42127): 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.
  • anatel.gov.br/DS (alg 5, id 42127): 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.
  • anatel.gov.br/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • anatel.gov.br/NSEC3PARAM 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