egbert.net
Updated:
2020-05-13 17:31:18 UTC (1648 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- egbert.net/A
- egbert.net/MX
- egbert.net/NS
- egbert.net/SOA
- egbert.net/TXT
DNSKEY/DS/NSEC status
Secure (13)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 48903)
- egbert.net/DNSKEY (alg 8, id 11770)
- egbert.net/DNSKEY (alg 8, id 27955)
- egbert.net/DNSKEY (alg 8, id 3330)
- egbert.net/DNSKEY (alg 8, id 35199)
- egbert.net/DS (alg 8, id 11770)
- egbert.net/DS (alg 8, id 11770)
- egbert.net/DS (alg 8, id 27955)
- egbert.net/DS (alg 8, id 27955)
- net/DNSKEY (alg 8, id 35886)
- net/DNSKEY (alg 8, id 36059)
- net/DS (alg 8, id 35886)
Delegation status
Secure (2)
- . to net
- net to egbert.net
Notices
Errors (13)
- egbert.net zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (69.65.50.223, 2001:1850:1:5:800::6b)
- egbert.net zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (69.65.50.223, 2001:1850:1:5:800::6b)
- egbert.net/A: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (69.65.50.223, 2001:1850:1:5:800::6b, UDP_-_NOEDNS_)
- egbert.net/DNSKEY: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (69.65.50.223, 2001:1850:1:5:800::6b, UDP_-_EDNS0_512_D_K, UDP_-_NOEDNS_)
- egbert.net/MX: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (69.65.50.223, 2001:1850:1:5:800::6b, UDP_-_EDNS0_512_D_K, UDP_-_NOEDNS_)
- egbert.net/NS: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (69.65.50.223, 2001:1850:1:5:800::6b, UDP_-_NOEDNS_)
- egbert.net/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (69.65.50.223, 2001:1850:1:5:800::6b, TCP_-_NOEDNS_)
- egbert.net/SOA: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (69.65.50.223, 2001:1850:1:5:800::6b, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
- egbert.net/TXT: The response had an invalid RCODE (SERVFAIL). See RFC 1035, Sec. 4.1.1. (69.65.50.223, 2001:1850:1:5:800::6b, UDP_-_NOEDNS_)
- ql4jf5ksw3.egbert.net/A has errors; select the "Denial of existence" DNSSEC option to see them.
- egbert.net/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- egbert.net/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- egbert.net/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
- egbert.net/DS (alg 8, id 11770): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- egbert.net/DS (alg 8, id 11770): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- egbert.net/DS (alg 8, id 11770): 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.
- egbert.net/DS (alg 8, id 11770): 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.
- egbert.net/DS (alg 8, id 27955): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- egbert.net/DS (alg 8, id 27955): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- egbert.net/DS (alg 8, id 27955): 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.
- egbert.net/DS (alg 8, id 27955): 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.
JavaScript is required to make the graph below interactive.
