View on GitHub

DNSViz: A DNS visualization tool

interior.gob.es

Updated: 2021-11-25 18:15:30 UTC (1028 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 (3)
  • interior.gob.es/NS
  • interior.gob.es/SOA
  • interior.gob.es/TXT
Secure (1)
  • gob.es/SOA

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (11)
  • ./DNSKEY (alg 8, id 14748)
  • ./DNSKEY (alg 8, id 20326)
  • NSEC3 proving non-existence of interior.gob.es/DS
  • es/DNSKEY (alg 8, id 24901)
  • es/DNSKEY (alg 8, id 50252)
  • es/DS (alg 8, id 50252)
  • es/DS (alg 8, id 50252)
  • gob.es/DNSKEY (alg 8, id 52186)
  • gob.es/DNSKEY (alg 8, id 58016)
  • gob.es/DS (alg 8, id 58016)
  • gob.es/DS (alg 8, id 58016)

Delegation statusDelegation status

Insecure (1)
  • gob.es to interior.gob.es
Secure (2)
  • . to es
  • es to gob.es

NoticesNotices

Errors (7)
  • NSEC3 proving non-existence of interior.gob.es/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 interior.gob.es/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
  • interior.gob.es zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (2a02:9000::1:3, 2a02:9000::1:4)
  • interior.gob.es/DS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:67c:21cc:2000::64:42, UDP_-_NOEDNS_)
  • interior.gob.es/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:67c:21cc:2000::64:42, UDP_-_NOEDNS_)
  • interior.gob.es/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (2a02:9000::1:3, 2a02:9000::1:4, TCP_-_EDNS0_4096_D_N)
  • interior.gob.es/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (11)
  • NSEC3 proving non-existence of interior.gob.es/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • NSEC3 proving non-existence of interior.gob.es/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
  • 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.
  • gob.es/DS (alg 8, id 58016): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gob.es/DS (alg 8, id 58016): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • gob.es/DS (alg 8, id 58016): 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.
  • gob.es/DS (alg 8, id 58016): 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.
  • interior.gob.es/DS 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