4no1.net
Updated:
2020-09-01 16:54:35 UTC (1544 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (5)
- 4no1.net/A
- 4no1.net/MX
- 4no1.net/NS
- 4no1.net/SOA
- 4no1.net/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 46594)
- 4no1.net/DS (alg 7, id 30894)
- net/DNSKEY (alg 8, id 35886)
- net/DNSKEY (alg 8, id 56519)
- net/DS (alg 8, id 35886)
Non_existent (1)
- 4no1.net/DNSKEY (alg 7, id 30894)
Delegation status
Bogus (1)
- net to 4no1.net
Secure (1)
- . to net
Notices
Errors (14)
- 4no1.net zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (35.156.85.88, 46.16.60.159, 46.16.60.166)
- 4no1.net/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (35.156.85.88, 46.16.60.159, 46.16.60.166, UDP_-_EDNS0_4096_D_K)
- 4no1.net/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (35.156.85.88, 46.16.60.159, 46.16.60.166, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- 4no1.net/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (35.156.85.88, 46.16.60.159, 46.16.60.166, UDP_-_EDNS0_4096_D_K)
- 4no1.net/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (35.156.85.88, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
- 4no1.net/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (46.16.60.159, 46.16.60.166, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
- 4no1.net/SOA: The TCP connection was refused (ECONNREFUSED). See RFC 1035, Sec. 4.2. (35.156.85.88, 46.16.60.159, 46.16.60.166, TCP_-_EDNS0_4096_D)
- net to 4no1.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. (35.156.85.88, 46.16.60.159, 46.16.60.166, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- net to 4no1.net: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no DS RR matched a DNSKEY with algorithm 7 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (35.156.85.88, 46.16.60.159, 46.16.60.166, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- 4no1.net/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- 4no1.net/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- 4no1.net/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
- szb76ngjfp.4no1.net/A has errors; select the "Denial of existence" DNSSEC option to see them.
- 4no1.net/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
- 4no1.net/A: The server responded with no OPT record, rather than with RCODE FORMERR. See RFC 6891, Sec. 7. (35.156.85.88, 46.16.60.159, 46.16.60.166, UDP_-_EDNS0_4096_D_K)
- 4no1.net/MX: The server responded with no OPT record, rather than with RCODE FORMERR. See RFC 6891, Sec. 7. (35.156.85.88, 46.16.60.159, 46.16.60.166, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_512_D_K)
- 4no1.net/NS: The server responded with no OPT record, rather than with RCODE FORMERR. See RFC 6891, Sec. 7. (35.156.85.88, 46.16.60.159, 46.16.60.166, UDP_-_EDNS0_4096_D_K)
- 4no1.net/SOA: The server responded with no OPT record, rather than with RCODE FORMERR. See RFC 6891, Sec. 7. (35.156.85.88, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
- 4no1.net/SOA: The server responded with no OPT record, rather than with RCODE FORMERR. See RFC 6891, Sec. 7. (46.16.60.159, 46.16.60.166, UDP_-_EDNS0_4096_D_K, UDP_-_EDNS0_4096_D_K_0x20)
- 4no1.net/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- 4no1.net/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- 4no1.net/TXT has warnings; select the "Denial of existence" DNSSEC option to see them.
- szb76ngjfp.4no1.net/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- 4no1.net/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
