inuvem.org
Updated:
2022-11-07 16:49:34 UTC (748 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (7)
- inuvem.org/A
- inuvem.org/AAAA
- inuvem.org/MX
- inuvem.org/NS
- inuvem.org/NSEC3PARAM
- inuvem.org/SOA
- inuvem.org/TXT
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 18733)
- ./DNSKEY (alg 8, id 20326)
- inuvem.org/DNSKEY (alg 13, id 37733)
- inuvem.org/DS (alg 13, id 37733)
- inuvem.org/DS (alg 13, id 37733)
- org/DNSKEY (alg 8, id 26974)
- org/DNSKEY (alg 8, id 29166)
- org/DNSKEY (alg 8, id 41406)
- org/DS (alg 8, id 26974)
Delegation status
Secure (2)
- . to org
- org to inuvem.org
Notices
Errors (4)
- ./DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (193.0.14.129, 2001:500:200::b, UDP_-_EDNS0_512_D_KN)
- org zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:500:c::1)
- r0esmcq9kd.inuvem.org/A has errors; select the "Denial of existence" DNSSEC option to see them.
- inuvem.org/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (12)
- ./DNSKEY (alg 8, id 18733): 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. (2001:500:200::b, UDP_-_EDNS0_4096_D_KN)
- ./DNSKEY (alg 8, id 20326): 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. (2001:500:200::b, UDP_-_EDNS0_4096_D_KN)
- inuvem.org/DS (alg 13, id 37733): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- inuvem.org/DS (alg 13, id 37733): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- inuvem.org/DS (alg 13, id 37733): 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.
- inuvem.org/DS (alg 13, id 37733): 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.
- inuvem.org/DS (alg 13, id 37733): In the spirit of RFC 4509, DS records with digest type 1 (SHA-1) might be ignored when DS records with digest type 4 (SHA-384) exist in the same RRset. See RFC 4509, Sec. 3.
- inuvem.org/DS (alg 13, id 37733): In the spirit of RFC 4509, DS records with digest type 1 (SHA-1) might be ignored when DS records with digest type 4 (SHA-384) exist in the same RRset. See RFC 4509, Sec. 3.
- org to inuvem.org: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the org zone): ns2.stackdns.com, ns1.stackdns.com, ns4.stackdns.com, ns3.stackdns.com See RFC 1034, Sec. 4.2.2.
- org to inuvem.org: The following NS name(s) were found in the delegation NS RRset (i.e., in the org zone), but not in the authoritative NS RRset: ns1.ibrave.host, ns2.ibrave.host, ns3.ibrave.host, ns4.ibrave.host See RFC 1034, Sec. 4.2.2.
- r0esmcq9kd.inuvem.org/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- inuvem.org/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
