poalim.bank

Updated: 2021-02-22 18:40:04 UTC (1422 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:
|?| Multi-signer:
|?| Trust anchors:
- Root zone KSK
|?| Additional trusted keys:

Notices

DNSSEC Authentication Chain

RRset status

Secure (4)

poalim.bank/MX
poalim.bank/NS
poalim.bank/SOA
poalim.bank/TXT

DNSKEY/DS/NSEC status

Bogus (4)

poalim.bank/DNSKEY (alg 7, id 14445)
poalim.bank/DNSKEY (alg 7, id 29346)
poalim.bank/DNSKEY (alg 7, id 48752)
poalim.bank/DNSKEY (alg 7, id 62420)

Secure (11)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 42351)
bank/DNSKEY (alg 8, id 38070)
bank/DNSKEY (alg 8, id 46351)
bank/DS (alg 8, id 46351)
bank/DS (alg 8, id 46351)
poalim.bank/DNSKEY (alg 8, id 56658)
poalim.bank/DNSKEY (alg 8, id 6541)
poalim.bank/DS (alg 7, id 29346)
poalim.bank/DS (alg 7, id 59985)
poalim.bank/DS (alg 8, id 6541)

Non_existent (1)

poalim.bank/DNSKEY (alg 7, id 59985)

Delegation status

Secure (2)

. to bank
bank to poalim.bank

Notices

Errors (40)

bank to poalim.bank: No valid RRSIGs made by a key corresponding to a DS RR were found covering the DNSKEY RRset, resulting in no secure entry point (SEP) into the zone. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (82.166.142.61, UDP_-_EDNS0_4096_D_KN)
bank to poalim.bank: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no DS RR matched a DNSKEY with algorithm 7 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (82.80.214.212, UDP_-_EDNS0_4096_D_KN)
bank to poalim.bank: The DS RRset for the zone included algorithm 8 (RSASHA256), but no DS RR matched a DNSKEY with algorithm 8 that signs the zone's DNSKEY RRset. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (82.166.142.61, UDP_-_EDNS0_4096_D_KN)
poalim.bank/DNSKEY (alg 7, id 14445): The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (82.166.142.61, UDP_-_EDNS0_4096_D_KN)
poalim.bank/DNSKEY (alg 7, id 14445): The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (82.166.142.61, UDP_-_EDNS0_4096_D_KN)
poalim.bank/DNSKEY (alg 7, id 29346): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (82.80.214.212, UDP_-_EDNS0_4096_D_KN)
poalim.bank/DNSKEY (alg 7, id 29346): The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (82.166.142.61, UDP_-_EDNS0_4096_D_KN)
poalim.bank/DNSKEY (alg 7, id 29346): The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (82.166.142.61, UDP_-_EDNS0_4096_D_KN)
poalim.bank/DNSKEY (alg 7, id 48752): The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (82.166.142.61, UDP_-_EDNS0_4096_D_KN)
poalim.bank/DNSKEY (alg 7, id 48752): The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (82.166.142.61, UDP_-_EDNS0_4096_D_KN)
poalim.bank/DNSKEY (alg 7, id 62420): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (82.80.214.212, UDP_-_EDNS0_4096_D_KN)
poalim.bank/DNSKEY (alg 7, id 62420): The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (82.166.142.61, UDP_-_EDNS0_4096_D_KN)
poalim.bank/DNSKEY (alg 7, id 62420): The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (82.166.142.61, UDP_-_EDNS0_4096_D_KN)
poalim.bank/DNSKEY (alg 8, id 56658): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (82.166.142.61, UDP_-_EDNS0_4096_D_KN)
poalim.bank/DNSKEY (alg 8, id 56658): The DNSKEY RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (82.80.214.212, UDP_-_EDNS0_4096_D_KN)
poalim.bank/DNSKEY (alg 8, id 56658): The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (82.80.214.212, UDP_-_EDNS0_4096_D_KN)
poalim.bank/DNSKEY (alg 8, id 6541): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (82.166.142.61, UDP_-_EDNS0_4096_D_KN)
poalim.bank/DNSKEY (alg 8, id 6541): The DNSKEY RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (82.80.214.212, UDP_-_EDNS0_4096_D_KN)
poalim.bank/DNSKEY (alg 8, id 6541): The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (82.80.214.212, UDP_-_EDNS0_4096_D_KN)
poalim.bank/MX: The DNSKEY RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (82.80.214.212, UDP_-_EDNS0_4096_D_KN)
poalim.bank/MX: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (82.166.142.61, UDP_-_EDNS0_4096_D_KN)
poalim.bank/MX: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (82.80.214.212, UDP_-_EDNS0_4096_D_KN)
poalim.bank/MX: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (82.166.142.61, UDP_-_EDNS0_4096_D_KN)
poalim.bank/NS: The DNSKEY RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (82.80.214.212, UDP_-_EDNS0_4096_D_KN)
poalim.bank/NS: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (82.166.142.61, UDP_-_EDNS0_4096_D_KN)
poalim.bank/NS: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (82.80.214.212, UDP_-_EDNS0_4096_D_KN)
poalim.bank/NS: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (82.166.142.61, UDP_-_EDNS0_4096_D_KN)
poalim.bank/SOA: The DNSKEY RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (82.80.214.212, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
poalim.bank/SOA: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (82.166.142.61, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
poalim.bank/SOA: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (82.80.214.212, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
poalim.bank/SOA: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (82.166.142.61, TCP_-_EDNS0_4096_D_N, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
poalim.bank/TXT: The DNSKEY RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (82.80.214.212, UDP_-_EDNS0_4096_D_KN)
poalim.bank/TXT: The DNSKEY RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (82.166.142.61, UDP_-_EDNS0_4096_D_KN)
poalim.bank/TXT: The DS RRset for the zone included algorithm 7 (RSASHA1NSEC3SHA1), but no RRSIG with algorithm 7 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (82.80.214.212, UDP_-_EDNS0_4096_D_KN)
poalim.bank/TXT: The DS RRset for the zone included algorithm 8 (RSASHA256), but no RRSIG with algorithm 8 covering the RRset was returned in the response. See RFC 4035, Sec. 2.2, RFC 6840, Sec. 5.11. (82.166.142.61, UDP_-_EDNS0_4096_D_KN)
poalim.bank/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
poalim.bank/A has errors; select the "Denial of existence" DNSSEC option to see them.
xb3gv70fja.poalim.bank/A has errors; select the "Denial of existence" DNSSEC option to see them.
poalim.bank/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
poalim.bank/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.

Warnings (36)

RRSIG poalim.bank/DNSKEY alg 7, id 29346: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG poalim.bank/DNSKEY alg 7, id 29346: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG poalim.bank/DNSKEY alg 7, id 29346: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG poalim.bank/DNSKEY alg 7, id 29346: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG poalim.bank/DNSKEY alg 7, id 62420: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG poalim.bank/DNSKEY alg 7, id 62420: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG poalim.bank/DNSKEY alg 7, id 62420: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG poalim.bank/DNSKEY alg 7, id 62420: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG poalim.bank/MX alg 7, id 62420: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG poalim.bank/NS alg 7, id 62420: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG poalim.bank/SOA alg 7, id 62420: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG poalim.bank/SOA alg 7, id 62420: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG poalim.bank/SOA alg 7, id 62420: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG poalim.bank/SOA alg 7, id 62420: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG poalim.bank/TXT alg 7, id 62420: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG poalim.bank/TXT alg 7, id 62420: The value of the Signature Inception field of the RRSIG RR (2021-02-22 18:40:04+00:00) is within possible clock skew range (0 seconds) of the current time (2021-02-22 18:40:04+00:00). See RFC 4035, Sec. 5.3.1.
RRSIG poalim.bank/TXT alg 8, id 56658: The value of the Signature Inception field of the RRSIG RR (2021-02-22 18:40:04+00:00) is within possible clock skew range (0 seconds) of the current time (2021-02-22 18:40:04+00:00). See RFC 4035, Sec. 5.3.1.
bank/DS (alg 8, id 46351): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
bank/DS (alg 8, id 46351): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
bank/DS (alg 8, id 46351): 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.
bank/DS (alg 8, id 46351): 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.
poalim.bank/DNSKEY (alg 7, id 14445): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (82.80.214.212, UDP_-_EDNS0_4096_D_KN)
poalim.bank/DNSKEY (alg 7, id 48752): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (82.80.214.212, UDP_-_EDNS0_4096_D_KN)
poalim.bank/DS (alg 7, id 29346): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
poalim.bank/DS (alg 7, id 29346): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
poalim.bank/DS (alg 7, id 29346): 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.
poalim.bank/DS (alg 7, id 29346): 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.
poalim.bank/DS (alg 7, id 59985): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
poalim.bank/DS (alg 7, id 59985): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
poalim.bank/DS (alg 7, id 59985): 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.
poalim.bank/DS (alg 7, id 59985): 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.
poalim.bank/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
poalim.bank/A has warnings; select the "Denial of existence" DNSSEC option to see them.
xb3gv70fja.poalim.bank/A has warnings; select the "Denial of existence" DNSSEC option to see them.
poalim.bank/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
poalim.bank/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.