4no1.net
Updated:
2022-04-11 08:53:44 UTC (957 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (4)
- 4no1.net/A
- 4no1.net/MX
- 4no1.net/NS
- 4no1.net/SOA
Secure (1)
- net/SOA
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 47671)
- ./DNSKEY (alg 8, id 9799)
- NSEC3 proving non-existence of 4no1.net/DS
- net/DNSKEY (alg 8, id 35886)
- net/DNSKEY (alg 8, id 45728)
- net/DNSKEY (alg 8, id 4604)
- net/DS (alg 8, id 35886)
Delegation status
Insecure (1)
- net to 4no1.net
Secure (1)
- . to net
Notices
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_KN)
- 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_KN, UDP_-_EDNS0_512_D_KN)
- 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_KN)
- 4no1.net/SOA: 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, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- 4no1.net/TXT has warnings; select the "Denial of existence" DNSSEC option to see them.
- 4no1.net/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- 4no1.net/NSEC3PARAM 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.
- d26av8l5mf.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.
