api.met.no
Updated:
2024-11-12 17:53:46 UTC (12 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (1)
- api.met.no/A
DNSKEY/DS/NSEC status
Secure (8)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 61050)
- met.no/DNSKEY (alg 10, id 18984)
- met.no/DNSKEY (alg 10, id 488)
- met.no/DS (alg 10, id 18984)
- no/DNSKEY (alg 13, id 32037)
- no/DNSKEY (alg 13, id 38032)
- no/DS (alg 13, id 38032)
Delegation status
Secure (2)
- . to no
- no to met.no
Notices
Warnings (7)
- RRSIG api.met.no/A alg 10, id 488: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG met.no/DNSKEY alg 10, id 18984: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG met.no/DNSKEY alg 10, id 18984: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG met.no/DNSKEY alg 10, id 488: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG met.no/DNSKEY alg 10, id 488: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- api.met.no/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- met.no/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
