аэросъемкауфа.рф
Updated:
2022-02-15 05:51:25 UTC (3 years ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (3)
- аэросъемкауфа.рф/A
- аэросъемкауфа.рф/NS
- аэросъемкауфа.рф/SOA
Secure (1)
- рф/SOA
DNSKEY/DS/NSEC status
Secure (7)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 9799)
- NSEC3 proving non-existence of аэросъемкауфа.рф/DS
- рф/DNSKEY (alg 8, id 16254)
- рф/DNSKEY (alg 8, id 49960)
- рф/DNSKEY (alg 8, id 54618)
- рф/DS (alg 8, id 49960)
Delegation status
Insecure (1)
- рф to аэросъемкауфа.рф
Secure (1)
- . to рф
Notices
Errors (4)
- NSEC3 proving non-existence of аэросъемкауфа.рф/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 аэросъемкауфа.рф/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- рф zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:678:14:0:193:232:156:17)
- xn--80aaaszlmpkyl0e9a.xn--p1ai/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (3)
- NSEC3 proving non-existence of аэросъемкауфа.рф/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of аэросъемкауфа.рф/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- xn--80aaaszlmpkyl0e9a.xn--p1ai/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
