View on GitHub

DNSViz: A DNS visualization tool

superenvios.pe

Updated: 2021-12-30 15:37:41 UTC (854 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 (5)
  • superenvios.pe/A
  • superenvios.pe/MX
  • superenvios.pe/NS
  • superenvios.pe/SOA
  • superenvios.pe/TXT
Secure (1)
  • pe/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (7)
  • ./DNSKEY (alg 8, id 14748)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 9799)
  • NSEC3 proving non-existence of superenvios.pe/DS
  • pe/DNSKEY (alg 8, id 37239)
  • pe/DNSKEY (alg 8, id 7981)
  • pe/DS (alg 8, id 7981)

Delegation statusDelegation status

Insecure (1)
  • pe to superenvios.pe
Secure (1)
  • . to pe

NoticesNotices

Errors (3)
  • pe zone: The server(s) were not responsive to queries over UDP. (200.1.176.4)
  • superenvios.pe zone: The following NS name(s) did not resolve to address(es): ns1.mail.superenvios.pe, ns2.mail.superenvios.pe
  • superenvios.pe zone: There was an error resolving the following NS name(s) to address(es): ns1.file.superenvios.pe
Warnings (3)
  • . to pe: A glue records exist for pch.rcp.pe, but there are no corresponding authoritative A records.
  • pe to superenvios.pe: The following NS name(s) required glue, but no glue was returned in the referral: ns1.file.superenvios.pe, ns1.mail.superenvios.pe, ns2.mail.superenvios.pe
  • pe to superenvios.pe: The following NS name(s) were found in the delegation NS RRset (i.e., in the pe zone), but not in the authoritative NS RRset: ns1.file.superenvios.pe, ns1.mail.superenvios.pe, ns2.mail.superenvios.pe

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