dnssec-or-not.net
Updated:
2020-10-22 03:02:22 UTC (1504 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (2)
- net/SOA
- net/SOA
DNSKEY/DS/NSEC status
Secure (7)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 26116)
- NSEC3 proving non-existence of dnssec-or-not.net/DS
- dnssec-or-not.net/DS (alg 8, id 53635)
- net/DNSKEY (alg 8, id 15314)
- net/DNSKEY (alg 8, id 35886)
- net/DS (alg 8, id 35886)
Non_existent (1)
- dnssec-or-not.net/DNSKEY (alg 8, id 53635)
Delegation status
Bogus (1)
- net to dnssec-or-not.net
Secure (1)
- . to net
Notices
Errors (16)
- dnssec-or-not.net zone: The server(s) responded over TCP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (104.237.131.42, 173.230.152.222, 2600:3c01::f03c:91ff:fe6e:85aa)
- dnssec-or-not.net zone: The server(s) responded over UDP with a malformed response or with an invalid RCODE. See RFC 1035, Sec. 4.1.1. (104.237.131.42, 173.230.152.222, 2600:3c01::f03c:91ff:fe6e:85aa)
- dnssec-or-not.net zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2600:3c00::f03c:91ff:fe89:51a)
- dnssec-or-not.net/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2600:3c00::f03c:91ff:fe89:51a, UDP_-_NOEDNS_)
- dnssec-or-not.net/A: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (104.237.131.42, 173.230.152.222, 2600:3c01::f03c:91ff:fe6e:85aa, UDP_-_EDNS0_4096_D_K)
- dnssec-or-not.net/AAAA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (104.237.131.42, 173.230.152.222, 2600:3c01::f03c:91ff:fe6e:85aa, UDP_-_EDNS0_4096_D_K)
- dnssec-or-not.net/DNSKEY: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (104.237.131.42, 173.230.152.222, 2600:3c01::f03c:91ff:fe6e:85aa, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- dnssec-or-not.net/MX: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (104.237.131.42, 173.230.152.222, 2600:3c01::f03c:91ff:fe6e:85aa, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- dnssec-or-not.net/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (104.237.131.42, 173.230.152.222, 2600:3c01::f03c:91ff:fe6e:85aa, TCP_-_EDNS0_4096_D)
- dnssec-or-not.net/SOA: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (104.237.131.42, 173.230.152.222, 2600:3c01::f03c:91ff:fe6e:85aa, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
- dnssec-or-not.net/TXT: The response had an invalid RCODE (REFUSED). See RFC 1035, Sec. 4.1.1. (104.237.131.42, 173.230.152.222, 2600:3c01::f03c:91ff:fe6e:85aa, UDP_-_EDNS0_4096_D_K)
- net to dnssec-or-not.net: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11.
- dnssec-or-not.net/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- 4jolv01b9p.dnssec-or-not.net/A has errors; select the "Denial of existence" DNSSEC option to see them.
- dnssec-or-not.net/NS has errors; select the "Denial of existence" DNSSEC option to see them.
- dnssec-or-not.net/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (1)
- net to dnssec-or-not.net: The following NS name(s) were found in the delegation NS RRset (i.e., in the net zone), but not in the authoritative NS RRset: ns.packet-pushers.com, ns2.packet-pushers.com See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
