se.net
Updated:
2023-08-09 13:12:46 UTC (459 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- se.net/A
- se.net/MX
- se.net/NS
- se.net/NSEC3PARAM
- se.net/SOA
- se.net/TXT
DNSKEY/DS/NSEC status
Secure (9)
- ./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/DS (alg 7, id 16074)
- se.net/DS (alg 7, id 34383)
Non_existent (1)
- se.net/DNSKEY (alg 7, id 34383)
Delegation status
Secure (2)
- . to net
- net to se.net
Notices
Warnings (18)
- RRSIG se.net/A alg 7, id 12965: 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 16074: 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 16074: 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 12965: 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 12965: 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 12965: 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 12965: 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 12965: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- 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. (212.18.248.10, 2001:67c:13cc::1:24, UDP_-_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. (212.18.248.10, 2001:67c:13cc::1:24, UDP_-_EDNS0_4096_D_KN)
- se.net/MX: 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, 2001:67c:13cc::1:24, 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. (2001:67c:13cc::1:24, 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, 2001:67c:13cc::1:24, 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, 2001:67c:13cc::1:24, UDP_-_EDNS0_4096_D_KN)
- se.net/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- h2yqpa8l7e.se.net/A 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.
JavaScript is required to make the graph below interactive.
