belgium.be
Updated:
2021-12-06 21:52:43 UTC (1133 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (6)
- belgium.be/A
- belgium.be/AAAA
- belgium.be/MX
- belgium.be/NS
- belgium.be/SOA
- belgium.be/TXT
Secure (1)
- be/SOA
DNSKEY/DS/NSEC status
Insecure (2)
- belgium.be/DNSKEY (alg 5, id 52051)
- belgium.be/DNSKEY (alg 5, id 7578)
Secure (10)
- ./DNSKEY (alg 8, id 14748)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of belgium.be/DS
- be/DNSKEY (alg 8, id 12664)
- be/DNSKEY (alg 8, id 52756)
- be/DNSKEY (alg 8, id 5955)
- be/DNSKEY (alg 8, id 64986)
- be/DNSKEY (alg 8, id 7359)
- be/DS (alg 8, id 12664)
- be/DS (alg 8, id 52756)
Delegation status
Insecure (1)
- be to belgium.be
Secure (1)
- . to be
Notices
Errors (3)
- NSEC3 proving non-existence of belgium.be/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 belgium.be/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- belgium.be/DS has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (18)
- NSEC3 proving non-existence of belgium.be/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of belgium.be/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- RRSIG belgium.be/A alg 5, id 7578: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG belgium.be/AAAA alg 5, id 7578: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG belgium.be/DNSKEY alg 5, id 52051: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG belgium.be/DNSKEY alg 5, id 52051: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG belgium.be/DNSKEY alg 5, id 7578: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG belgium.be/DNSKEY alg 5, id 7578: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG belgium.be/MX alg 5, id 7578: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG belgium.be/NS alg 5, id 7578: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG belgium.be/SOA alg 5, id 7578: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- RRSIG belgium.be/TXT alg 5, id 7578: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 5 (RSASHA1). See RFC 8624, Sec. 3.1.
- be to belgium.be: No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (120.29.253.8, UDP_-_EDNS0_4096_D_KN)
- belgium.be/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- belgium.be/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- belgium.be/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
- belgium.be/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
- w8g6zkvip1.belgium.be/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
