medarbejder.akf-holding.dk

Updated: 2022-08-19 10:14:02 UTC (672 days ago) Go to most recent »

DNSSEC options (hide)

|?| RR types:
|?| DNSSEC algorithms:
|?| DS digest algorithms:
|?| Denial of existence:
|?| Redundant edges:
|?| Ignore RFC 8624:
|?| Ignore RFC 9276:
|?| Trust anchors:
- Root zone KSK
|?| Additional trusted keys:

Notices

DNSSEC Authentication Chain

RRset status

Bogus (11)

medarbejder.akf-holding.dk/AAAA (NODATA)
medarbejder.akf-holding.dk/CAA (NODATA)
medarbejder.akf-holding.dk/CNAME (NODATA)
medarbejder.akf-holding.dk/MX (NODATA)
medarbejder.akf-holding.dk/NAPTR (NODATA)
medarbejder.akf-holding.dk/NSEC3PARAM (NODATA)
medarbejder.akf-holding.dk/PTR (NODATA)
medarbejder.akf-holding.dk/SOA (NODATA)
medarbejder.akf-holding.dk/SRV (NODATA)
medarbejder.akf-holding.dk/TLSA (NODATA)
medarbejder.akf-holding.dk/TXT (NODATA)

Secure (2)

akf-holding.dk/SOA
medarbejder.akf-holding.dk/A

DNSKEY/DS/NSEC status

Bogus (11)

NSEC proving non-existence of medarbejder.akf-holding.dk/AAAA
NSEC proving non-existence of medarbejder.akf-holding.dk/CAA
NSEC proving non-existence of medarbejder.akf-holding.dk/CNAME
NSEC proving non-existence of medarbejder.akf-holding.dk/MX
NSEC proving non-existence of medarbejder.akf-holding.dk/NAPTR
NSEC proving non-existence of medarbejder.akf-holding.dk/NSEC3PARAM
NSEC proving non-existence of medarbejder.akf-holding.dk/PTR
NSEC proving non-existence of medarbejder.akf-holding.dk/SOA
NSEC proving non-existence of medarbejder.akf-holding.dk/SRV
NSEC proving non-existence of medarbejder.akf-holding.dk/TLSA
NSEC proving non-existence of medarbejder.akf-holding.dk/TXT

Secure (12)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 20826)
akf-holding.dk/DNSKEY (alg 8, id 4730)
akf-holding.dk/DNSKEY (alg 8, id 53455)
akf-holding.dk/DNSKEY (alg 8, id 58839)
akf-holding.dk/DS (alg 8, id 4730)
akf-holding.dk/DS (alg 8, id 4730)
akf-holding.dk/DS (alg 8, id 53455)
akf-holding.dk/DS (alg 8, id 53455)
dk/DNSKEY (alg 13, id 29434)
dk/DNSKEY (alg 13, id 44778)
dk/DS (alg 13, id 29434)

Delegation status

Secure (2)

. to dk
dk to akf-holding.dk

Notices

Errors (15)

RRSIG NSEC proving non-existence of medarbejder.akf-holding.dk/AAAA alg 8, id 58839: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG NSEC proving non-existence of medarbejder.akf-holding.dk/CAA alg 8, id 58839: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG NSEC proving non-existence of medarbejder.akf-holding.dk/CNAME alg 8, id 58839: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG NSEC proving non-existence of medarbejder.akf-holding.dk/MX alg 8, id 58839: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG NSEC proving non-existence of medarbejder.akf-holding.dk/NAPTR alg 8, id 58839: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG NSEC proving non-existence of medarbejder.akf-holding.dk/NSEC3PARAM alg 8, id 58839: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG NSEC proving non-existence of medarbejder.akf-holding.dk/PTR alg 8, id 58839: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG NSEC proving non-existence of medarbejder.akf-holding.dk/SOA alg 8, id 58839: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG NSEC proving non-existence of medarbejder.akf-holding.dk/SRV alg 8, id 58839: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG NSEC proving non-existence of medarbejder.akf-holding.dk/TLSA alg 8, id 58839: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
RRSIG NSEC proving non-existence of medarbejder.akf-holding.dk/TXT alg 8, id 58839: The cryptographic signature of the RRSIG RR does not properly validate. See RFC 4035, Sec. 5.3.3.
akf-holding.dk/DS (alg 8, id 4730): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
akf-holding.dk/DS (alg 8, id 4730): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
akf-holding.dk/DS (alg 8, id 53455): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
akf-holding.dk/DS (alg 8, id 53455): DNSSEC specification prohibits signing with DS records that use digest algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.

Warnings (8)

akf-holding.dk/DS (alg 8, id 4730): 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.
akf-holding.dk/DS (alg 8, id 4730): 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.
akf-holding.dk/DS (alg 8, id 4730): In the spirit of RFC 4509, DS records with digest type 1 (SHA-1) might be ignored when DS records with digest type 4 (SHA-384) exist in the same RRset. See RFC 4509, Sec. 3.
akf-holding.dk/DS (alg 8, id 4730): In the spirit of RFC 4509, DS records with digest type 1 (SHA-1) might be ignored when DS records with digest type 4 (SHA-384) exist in the same RRset. See RFC 4509, Sec. 3.
akf-holding.dk/DS (alg 8, id 53455): 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.
akf-holding.dk/DS (alg 8, id 53455): 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.
akf-holding.dk/DS (alg 8, id 53455): In the spirit of RFC 4509, DS records with digest type 1 (SHA-1) might be ignored when DS records with digest type 4 (SHA-384) exist in the same RRset. See RFC 4509, Sec. 3.
akf-holding.dk/DS (alg 8, id 53455): In the spirit of RFC 4509, DS records with digest type 1 (SHA-1) might be ignored when DS records with digest type 4 (SHA-384) exist in the same RRset. See RFC 4509, Sec. 3.