ripe.net
Updated:
2023-11-01 11:43:45 UTC (389 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- ripe.net/A
- ripe.net/AAAA
- ripe.net/MX
- ripe.net/NS
- ripe.net/SOA
- ripe.net/TXT
DNSKEY/DS/NSEC status
Secure (7)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46780)
- net/DNSKEY (alg 8, id 35886)
- net/DNSKEY (alg 8, id 51464)
- net/DS (alg 8, id 35886)
- ripe.net/DNSKEY (alg 13, id 10186)
- ripe.net/DS (alg 13, id 10186)
Delegation status
Secure (2)
- . to net
- net to ripe.net
Notices
Errors (4)
- ripe.net/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2620:38:2000::53, UDP_-_NOEDNS_)
- ripe.net/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (2620:38:2000::53, UDP_-_EDNS0_512_D_KN)
- l0sjtwvyia.ripe.net/A has errors; select the "Denial of existence" DNSSEC option to see them.
- ripe.net/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (5)
- ripe.net/SOA: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (2620:38:2000::53, UDP_-_EDNS0_4096_D_KN)
- ripe.net/SOA: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2620:38:2000::53, UDP_-_EDNS0_4096_D_KN_0x20)
- ripe.net/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
- ripe.net/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- l0sjtwvyia.ripe.net/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
