nsm.no
Updated:
2021-01-18 13:24:51 UTC (1406 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- nsm.no/A
- nsm.no/MX
- nsm.no/NS
- nsm.no/SOA
- nsm.no/TXT
Secure (1)
- no/SOA
DNSKEY/DS/NSEC status
Insecure (2)
- nsm.no/DNSKEY (alg 8, id 21110)
- nsm.no/DNSKEY (alg 8, id 42016)
Secure (6)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 42351)
- NSEC3 proving non-existence of nsm.no/DS
- no/DNSKEY (alg 8, id 29471)
- no/DNSKEY (alg 8, id 37518)
- no/DS (alg 8, id 29471)
Delegation status
Insecure (1)
- no to nsm.no
Secure (1)
- . to no
Notices
Errors (6)
- NSEC3 proving non-existence of nsm.no/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of nsm.no/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- hfa361n0dj.nsm.no/A has errors; select the "Denial of existence" DNSSEC option to see them.
- nsm.no/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- nsm.no/DS has errors; select the "Denial of existence" DNSSEC option to see them.
- nsm.no/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (6)
- NSEC3 proving non-existence of nsm.no/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of nsm.no/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- hfa361n0dj.nsm.no/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- nsm.no/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- nsm.no/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
- nsm.no/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
