nickersonm.com
Updated:
2022-03-06 14:41:57 UTC (1021 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Bogus (5)
- nickersonm.com/A
- nickersonm.com/MX
- nickersonm.com/NS
- nickersonm.com/SOA
- nickersonm.com/TXT
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 9799)
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 38535)
- com/DS (alg 8, id 30909)
- nickersonm.com/DS (alg 5, id 34756)
Non_existent (1)
- nickersonm.com/DNSKEY (alg 5, id 34756)
Delegation status
Bogus (1)
- com to nickersonm.com
Secure (1)
- . to com
Notices
Errors (12)
- com to nickersonm.com: 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. (108.162.192.147, 108.162.193.143, 172.64.32.147, 172.64.33.143, 173.245.58.147, 173.245.59.143, 2606:4700:50::adf5:3a93, 2606:4700:58::adf5:3b8f, 2803:f800:50::6ca2:c093, 2803:f800:50::6ca2:c18f, 2a06:98c1:50::ac40:2093, 2a06:98c1:50::ac40:218f, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- com to nickersonm.com: The DS RRset for the zone included algorithm 5 (RSASHA1), but no DS RR matched a DNSKEY with algorithm 5 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (108.162.192.147, 108.162.193.143, 172.64.32.147, 172.64.33.143, 173.245.58.147, 173.245.59.143, 2606:4700:50::adf5:3a93, 2606:4700:58::adf5:3b8f, 2803:f800:50::6ca2:c093, 2803:f800:50::6ca2:c18f, 2a06:98c1:50::ac40:2093, 2a06:98c1:50::ac40:218f, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- nickersonm.com/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (108.162.192.147, 108.162.193.143, 172.64.32.147, 172.64.33.143, 173.245.58.147, 173.245.59.143, 2606:4700:50::adf5:3a93, 2606:4700:58::adf5:3b8f, 2803:f800:50::6ca2:c093, 2803:f800:50::6ca2:c18f, 2a06:98c1:50::ac40:2093, 2a06:98c1:50::ac40:218f, UDP_-_EDNS0_4096_D_KN)
- nickersonm.com/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (108.162.192.147, 108.162.193.143, 172.64.32.147, 172.64.33.143, 173.245.58.147, 173.245.59.143, 2606:4700:50::adf5:3a93, 2606:4700:58::adf5:3b8f, 2803:f800:50::6ca2:c093, 2803:f800:50::6ca2:c18f, 2a06:98c1:50::ac40:2093, 2a06:98c1:50::ac40:218f, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- nickersonm.com/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (108.162.192.147, 108.162.193.143, 172.64.32.147, 172.64.33.143, 173.245.58.147, 173.245.59.143, 2606:4700:50::adf5:3a93, 2606:4700:58::adf5:3b8f, 2803:f800:50::6ca2:c093, 2803:f800:50::6ca2:c18f, 2a06:98c1:50::ac40:2093, 2a06:98c1:50::ac40:218f, UDP_-_EDNS0_4096_D_KN)
- nickersonm.com/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (108.162.192.147, 108.162.193.143, 172.64.32.147, 172.64.33.143, 173.245.58.147, 173.245.59.143, 2606:4700:50::adf5:3a93, 2606:4700:58::adf5:3b8f, 2803:f800:50::6ca2:c093, 2803:f800:50::6ca2:c18f, 2a06:98c1:50::ac40:2093, 2a06:98c1:50::ac40:218f, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- nickersonm.com/TXT: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (108.162.192.147, 108.162.193.143, 172.64.32.147, 172.64.33.143, 173.245.58.147, 173.245.59.143, 2606:4700:50::adf5:3a93, 2606:4700:58::adf5:3b8f, 2803:f800:50::6ca2:c093, 2803:f800:50::6ca2:c18f, 2a06:98c1:50::ac40:2093, 2a06:98c1:50::ac40:218f, UDP_-_EDNS0_4096_D_KN)
- bf0k29i7ou.nickersonm.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
- nickersonm.com/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
- nickersonm.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- nickersonm.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- nickersonm.com/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- nickersonm.com/DS (alg 5, id 34756): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- nickersonm.com/DS (alg 5, id 34756): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- nickersonm.com/DS (alg 5, id 34756): 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.
- nickersonm.com/DS (alg 5, id 34756): 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.
JavaScript is required to make the graph below interactive.
