View on GitHub

DNSViz: A DNS visualization tool

se.net

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

RRset statusRRset status

Secure (6)
  • se.net/A
  • se.net/MX
  • se.net/NS
  • se.net/NSEC3PARAM
  • se.net/SOA
  • se.net/TXT

DNSKEY/DS/NSEC statusDNSKEY/DS/NSEC status

Secure (12)
  • ./DNSKEY (alg 8, id 11019)
  • ./DNSKEY (alg 8, id 20326)
  • net/DNSKEY (alg 8, id 35886)
  • net/DNSKEY (alg 8, id 39455)
  • net/DS (alg 8, id 35886)
  • se.net/DNSKEY (alg 7, id 12965)
  • se.net/DNSKEY (alg 7, id 16074)
  • se.net/DNSKEY (alg 7, id 34383)
  • se.net/DNSKEY (alg 7, id 48984)
  • se.net/DNSKEY (alg 7, id 65504)
  • se.net/DS (alg 7, id 34383)
  • se.net/DS (alg 7, id 34383)

Delegation statusDelegation status

Secure (2)
  • . to net
  • net to se.net

NoticesNotices

Warnings (30)
  • RRSIG se.net/A alg 7, id 48984: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG se.net/DNSKEY alg 7, id 34383: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG se.net/DNSKEY alg 7, id 34383: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG se.net/DNSKEY alg 7, id 34383: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG se.net/DNSKEY alg 7, id 34383: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG se.net/DNSKEY alg 7, id 34383: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG se.net/MX alg 7, id 48984: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG se.net/NS alg 7, id 48984: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG se.net/NSEC3PARAM alg 7, id 48984: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG se.net/SOA alg 7, id 65504: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • RRSIG se.net/TXT alg 7, id 48984: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
  • se.net/A: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (212.18.248.10, UDP_-_EDNS0_4096_D_KN)
  • se.net/DNSKEY (alg 7, id 12965): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2a04:2b00:13ee::10, TCP_-_EDNS0_4096_D_KN)
  • se.net/DNSKEY (alg 7, id 16074): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2a04:2b00:13ee::10, TCP_-_EDNS0_4096_D_KN)
  • se.net/DNSKEY (alg 7, id 34383): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2a04:2b00:13ee::10, TCP_-_EDNS0_4096_D_KN)
  • se.net/DNSKEY (alg 7, id 48984): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2a04:2b00:13ee::10, TCP_-_EDNS0_4096_D_KN)
  • se.net/DNSKEY (alg 7, id 65504): The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2a04:2b00:13ee::10, TCP_-_EDNS0_4096_D_KN)
  • se.net/DNSKEY: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (212.18.248.10, 2a04:2b00:13ee::10, UDP_-_EDNS0_512_D_KN)
  • se.net/DS (alg 7, id 34383): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • se.net/DS (alg 7, id 34383): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
  • se.net/DS (alg 7, id 34383): 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.
  • se.net/DS (alg 7, id 34383): 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.
  • se.net/MX: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (2a04:2b00:13ee::10, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
  • se.net/NSEC3PARAM: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (212.18.248.10, 2a04:2b00:13ee::10, UDP_-_EDNS0_4096_D_KN)
  • se.net/SOA: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (212.18.248.10, 2a04:2b00:13ee::10, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
  • se.net/TXT: The server appears to support DNS cookies but did not return a COOKIE option. See RFC 7873, Sec. 5.2.3. (212.18.248.10, UDP_-_EDNS0_4096_D_KN)
  • se.net/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
  • se.net/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
  • se.net/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
  • gedc0wu6ma.se.net/A 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