s3lph.ch
Updated:
2021-11-10 11:14:44 UTC (1159 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (7)
- s3lph.ch/A
- s3lph.ch/AAAA
- s3lph.ch/MX
- s3lph.ch/NS
- s3lph.ch/NSEC3PARAM
- s3lph.ch/SOA
- s3lph.ch/TXT
Secure (2)
- ch/SOA
- ch/SOA
DNSKEY/DS/NSEC status
Insecure (2)
- s3lph.ch/DNSKEY (alg 14, id 19881)
- s3lph.ch/DNSKEY (alg 14, id 46451)
Secure (7)
- ./DNSKEY (alg 8, id 14748)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of s3lph.ch/DS
- ch/DNSKEY (alg 13, id 1053)
- ch/DNSKEY (alg 13, id 2883)
- ch/DNSKEY (alg 13, id 6720)
- ch/DS (alg 13, id 1053)
Delegation status
Insecure (1)
- ch to s3lph.ch
Secure (1)
- . to ch
Notices
Errors (15)
- ch/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (74.116.178.40, UDP_-_EDNS0_512_D_KN)
- s3lph.ch zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (78.47.46.234, 2a01:4f8:c0c:1f2c::2)
- s3lph.ch zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (78.47.46.234, 2a01:4f8:c0c:1f2c::2)
- s3lph.ch/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (78.47.46.234, 2a01:4f8:c0c:1f2c::2, UDP_-_EDNS0_4096_D_KN)
- s3lph.ch/AAAA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (78.47.46.234, 2a01:4f8:c0c:1f2c::2, UDP_-_EDNS0_4096_D_KN)
- s3lph.ch/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (78.47.46.234, 2a01:4f8:c0c:1f2c::2, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- s3lph.ch/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (78.47.46.234, 2a01:4f8:c0c:1f2c::2, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- s3lph.ch/NS: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (78.47.46.234, 2a01:4f8:c0c:1f2c::2, UDP_-_EDNS0_4096_D_KN)
- s3lph.ch/NSEC3PARAM: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (78.47.46.234, 2a01:4f8:c0c:1f2c::2, UDP_-_EDNS0_4096_D_KN)
- s3lph.ch/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (78.47.46.234, 2a01:4f8:c0c:1f2c::2, TCP_-_EDNS0_4096_D_N)
- s3lph.ch/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (78.47.46.234, 2a01:4f8:c0c:1f2c::2, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- s3lph.ch/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (78.47.46.234, 2a01:4f8:c0c:1f2c::2, UDP_-_EDNS0_4096_D_KN)
- yakxo1gmvd.s3lph.ch/A has errors; select the "Denial of existence" DNSSEC option to see them.
- s3lph.ch/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- s3lph.ch/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- . to ch: The following NS name(s) were found in the delegation NS RRset (i.e., in the . zone), but not in the authoritative NS RRset: c.nic.ch, g.nic.ch See RFC 1034, Sec. 4.2.2.
- ch to s3lph.ch: The following NS name(s) were found in the delegation NS RRset (i.e., in the ch zone), but not in the authoritative NS RRset: ns1.s3lph.me See RFC 1034, Sec. 4.2.2.
- yakxo1gmvd.s3lph.ch/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- s3lph.ch/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
