arcep.bj | DNSViz

arcep.bj

Updated: 2024-01-11 11:18:47 UTC (359 days ago) Update now

DNSSEC options (hide)

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

Notices

DNSSEC Authentication Chain

RRset status

Insecure (6)

arcep.bj/A
arcep.bj/AAAA
arcep.bj/MX
arcep.bj/NS
arcep.bj/SOA
arcep.bj/TXT

Secure (1)

bj/SOA

DNSKEY/DS/NSEC status

Secure (7)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 30903)
NSEC3 proving non-existence of arcep.bj/DS
bj/DNSKEY (alg 8, id 20785)
bj/DNSKEY (alg 8, id 26617)
bj/DNSKEY (alg 8, id 55510)
bj/DS (alg 8, id 26617)

Delegation status

Insecure (1)

bj to arcep.bj

Secure (1)

. to bj

Notices

Errors (3)

NSEC3 proving non-existence of arcep.bj/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 arcep.bj/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
arcep.bj/DS has errors; select the "Denial of existence" DNSSEC option to see them.

Warnings (3)

NSEC3 proving non-existence of arcep.bj/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of arcep.bj/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
arcep.bj/DS has warnings; select the "Denial of existence" DNSSEC option to see them.

DNSKEY legend

Full legend

	SEP bit set
	Revoke bit set
	Trust anchor

See also

DNSSEC Debugger by Verisign Labs.

Download: png | svg

Warning

JavaScript is required to make the graph below interactive.

DNSSEC authentication graph