View on GitHub

DNSViz: A DNS visualization tool

magicescape.es

« Previous analysis | Next analysis »
DNSSEC options (hide)
  1. |?|
  2. |?|
  3. |?|
  4. |?|
  5. |?|
  6. |?|
  7. |?|
  8. |?|
  9. |?|
  10. |?|
Notices
DNSSEC Authentication Chain

RRset statusRRset status

Bogus (4)
  • magicescape.es/A
  • magicescape.es/MX
  • magicescape.es/NS
  • magicescape.es/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (8)
  • ./DNSKEY (alg 8, id 20326)
  • ./DNSKEY (alg 8, id 48903)
  • es/DNSKEY (alg 8, id 40876)
  • es/DNSKEY (alg 8, id 50252)
  • es/DS (alg 8, id 29450)
  • es/DS (alg 8, id 50252)
  • es/DS (alg 8, id 50252)
  • magicescape.es/DS (alg 7, id 23928)
Non_existent (2)
  • es/DNSKEY (alg 8, id 29450)
  • magicescape.es/DNSKEY (alg 7, id 23928)

Delegation statusDelegation status

Bogus (1)
  • es to magicescape.es
Secure (1)
  • . to es

NoticesNotices

Errors (11)
  • es to magicescape.es: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (216.239.36.100, 216.239.38.100, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • es to magicescape.es: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no DS RR matched a DNSKEY with algorithm 7 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (216.239.36.100, 216.239.38.100, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • magicescape.es/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (216.239.36.100, 216.239.38.100, UDP_-_EDNS0_4096_D_K)
  • magicescape.es/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (216.239.36.100, 216.239.38.100, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
  • magicescape.es/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (216.239.36.100, 216.239.38.100, UDP_-_EDNS0_4096_D_K)
  • magicescape.es/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (216.239.36.100, 216.239.38.100, TCP_-_EDNS0_4096_D, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
  • magicescape.es/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
  • magicescape.es/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
  • nmzlq7cjk8.magicescape.es/A has errors; select the "Denial of existence" DNSSEC option to see them.
  • magicescape.es/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
  • magicescape.es/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
  • es/DS (alg 8, id 50252): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • es/DS (alg 8, id 50252): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • es/DS (alg 8, id 50252): 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.
  • es/DS (alg 8, id 50252): 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.

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