rockfranky.dynvpn.de
Updated:
2022-12-05 17:46:54 UTC (747 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (1)
- de/SOA
DNSKEY/DS/NSEC status
Secure (7)
- ./DNSKEY (alg 8, id 18733)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of dynvpn.de/DS
- de/DNSKEY (alg 8, id 26755)
- de/DNSKEY (alg 8, id 31116)
- de/DNSKEY (alg 8, id 44298)
- de/DS (alg 8, id 26755)
Delegation status
Insecure (1)
- de to dynvpn.de
Secure (1)
- . to de
Notices
Errors (4)
- NSEC3 proving non-existence of dynvpn.de/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of dynvpn.de/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- rockfranky.dynvpn.de/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (83.246.76.144, 83.246.77.45, UDP_-_NOEDNS_)
- rockfranky.dynvpn.de/AAAA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (83.246.76.144, 83.246.77.45, UDP_-_NOEDNS_)
Warnings (2)
- NSEC3 proving non-existence of dynvpn.de/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of dynvpn.de/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
JavaScript is required to make the graph below interactive.
